Solution skill
Switching Intercom workspaces needs an app restart, shutdown is not enough
Complete solution
Guide Switching Intercom workspaces needs an app restart, shutdown is not enough: Switching the workspace/app requires a real app restart (the accepted answer used the Phoenix library on Android to force one). You cannot do this with the public API. Use this when you hit exactly this in Switching Intercom. Not for different errors or different tools.
TL;DR: Switching the workspace/app requires a real app restart (the accepted answer used the Phoenix library on Android to force one). You cannot do this with the public API. Intercom('shutdown') only clears local caches and user data; it does not undo the singleton instance created at initialize, and there is no public unregister method.
Fix
Switching the workspace/app requires a real app restart (the accepted answer used the Phoenix library on Android to force one). Expected: the request routes instead of erroring.
Design around it: keep one Intercom app per client build, or plan the workspace switch at a natural restart point, not mid-session. Expected: the request routes instead of erroring.
Context: Stack Overflow #55762814 (accepted answer, 2 votes): App has multiple Intercom workspaces and wants to switch between them at runtime without restarting the app. Expected: the request routes instead of erroring.
Intercom docs suggested Intercom('shutdown') then initialize again, but appKey and appId did not change and the switch did not work. Expected: the request routes instead of erroring.
Details
You cannot do this with the public API. Intercom('shutdown') only clears local caches and user data; it does not undo the singleton instance created at initialize, and there is no public unregister method. If you need this regularly, ask Intercom support or their forum, where their engineering team answers.
When to use
You hit exactly this: Switching Intercom workspaces needs an app restart, shutdown is not enough in Switching Intercom.
When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.
Compatibility
Switching Intercom.
Evidence
Stack Overflow #55762814 (accepted answer, 2 votes): App has multiple Intercom workspaces and wants to switch between them at runtime without restarting the app. Intercom docs suggested Intercom('shutdown') then initialize again, but appKey and appId did not change and the switch did not work. Resolved: You cannot do this with the public API. Intercom('shutdown') only clears local caches and user data; it does not undo the singleton instance created at initialize, and there is no public unregister method. Switching the workspace/app requires a real app restart (the accepted answer used the Phoenix library on Android to force one). Design around it: keep one Intercom app per client build, or plan the workspace switch at a natural restart point, not mid-session. If you need this regularly, ask Intercom support or their forum, where their engineering team answers. Source: https://stackoverflow.com/questions/55762814/re-initialize-intercom-in-application
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_RhUddn4xYRn-hS7JWUGBZw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Switching Intercom workspaces needs an app restart, shutdown is not enough <span>— Vectle</span></a>