Install
Load the unpacked 1.2.7 source. The Chrome Web Store listing is live but older (measured 1.2.1) — this repo does not publish.
Get the extensionPrivacy
Read the full canonical privacy policy. The fix flow is local; bug reports are optional and user-triggered.
Read privacy policyWhat Error 1132 means here
In this browser tool, Zoom Error 1132 is treated as stale Zoom browser state: cookies on zoom.us / zoom.com and this tab’s Zoom site data. Clearing that state after FIX ZOOM and reloading the tab is the whole job.
This is not the Windows-profile path. The Windows app uses a helper account named user1. This extension does not create Windows accounts, does not touch user1, and does not launch Zoom Workplace.
What it does
1132 Fixer is the Chrome sibling of 1132 Fixer for Windows. One purpose: clear Zoom browser state related to error 1132, then reload the Zoom tab.
- On
zoom.us,zoom.com, or any of their subdomains, the popup shows ZOOM DETECTED and a single FIX ZOOM button. No options, no checkboxes, no log to read. - On any other site (or
chrome:///about:pages), the popup shows one line asking you to open a Zoom tab. No button is offered. The extension does not request access to non-Zoom hosts. - Every clear is user-triggered. The popup never deletes anything on open, install, startup, page-load, or a timer.
Source version is 1.2.7. Chrome, Edge, Brave, and Firefox packages exist from this tree; Firefox runtime is MANUAL_VALIDATION_REQUIRED. The live Chrome Web Store listing was measured 1.2.1.
What it does not do
- No Windows
user1/ isolated-profile repair. That is the Windows app only. - No unrelated-origin clearing. Other sites, the global HTTP cache, and service workers are left alone. Zoom site data is cleared only in the active Zoom tab, and only after FIX ZOOM.
- No data collection. No analytics. No telemetry pings of any kind.
- No remote code. Every script ships in the package — no
fetch, noXMLHttpRequest, noWebSocket, nosendBeacon, noeval, nonew Function. - No external fonts, stylesheets, images, or remote config.
- No reading of your cookie values. The extension only deletes; the UI surfaces a single count.
- No access to non-Zoom domains. Host permissions are scoped to Zoom’s two domains — Chrome will not let the extension touch anything else.
- The global HTTP cache is never wiped.
Permissions, in plain English
| Permission | Used for |
|---|---|
cookies |
Enumerate and delete cookies for zoom.us and zoom.com. |
activeTab |
Read the active tab’s URL when you open the popup; reload it after a successful clear. |
scripting |
One-shot inject into the active Zoom tab after FIX ZOOM, to clear that origin’s localStorage, sessionStorage, Cache API, and IndexedDB. The injected function refuses any other host. No content script is registered. |
Hosts: https://*.zoom.us/*, https://*.zoom.com/*, http://*.zoom.us/*, http://*.zoom.com/* |
Required by chrome.cookies to operate on Zoom domains, and by scripting to inject only into those hosts. Both schemes are listed so non-Secure Zoom cookies are visible too. No broader host access is requested. |
There is no browsingData permission and no <all_urls> host permission. scripting is the minimum extra permission the in-page Zoom-origin cleaner needs.
Where to go next
- Privacy: Full privacy policy
- Source: github.com/1132-Fixer/chrome
- Windows sibling: github.com/1132-Fixer/windows
- License: Code, documentation, and design tokens are MIT. The 1132 Fixer name, logo, icons, and brand artwork are not covered by the MIT licence, prospectively from the notice date — see TRADEMARKS, the per-file ASSET-LICENSE, and NOTICE.
- Independent project. Not affiliated with Zoom Video Communications, Inc.