# Published Apps SDK widget updates / CSP behavior inconsistent after redeploy — anyone else seeing this? **URL:** \ **Category:** ChatGPT Apps SDK\ **Tags:** widget\ **Created:** [May 24, 2026, 3:55pm UTC](https://community.openai.com/t/published-apps-sdk-widget-updates-csp-behavior-inconsistent-after-redeploy-anyone-else-seeing-this/1381690 "2026-05-24T15:55:39Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Nadja\_Carabulea](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/nadja_carabulea/32/714857_2.png) [@Nadja\_Carabulea](https://community.openai.com/u/Nadja_Carabulea)\ **Post date:** [May 24, 2026, 3:55pm UTC](https://community.openai.com/t/published-apps-sdk-widget-updates-csp-behavior-inconsistent-after-redeploy-anyone-else-seeing-this/1381690/1 "2026-05-24T15:55:39Z")
\*\*EDIT (May 25, 2026): Resolved — see update below.\*\* We’re debugging a published ChatGPT app (“Priority Guardian”) and are trying to understand whether other developers are seeing similar behavior, especially for apps approved before the April 28 snapshot/cache changes. What we’re seeing: - `_meta.ui.csp.connectDomains` and legacy `openai/widgetCSP.connect_domains` appear ignored in the published runtime - iframe fetches to our declared backend domain are still CSP-blocked - after full disconnect/reconnect, our MCP logs show fresh `ReadResourceRequest` calls returning the newly deployed bundle (~364 KB) - BUT the iframe still appears to load the same `main-*.js` asset from `web-sandbox.oaiusercontent.com` - difficult to verify which bundle is actually executing - repeated ChatGPT internal runtime errors: We also noticed: - fullscreen/displayMode behavior became unstable recently (fullscreen flashes briefly then collapses) - onboarding becomes hard/impossible in condensed mode for new users Questions for other Apps SDK developers: 1. Are `connectDomains` / `connect_domains` currently working for published apps? 2. Have you seen stale widget/runtime behavior after redeploys? 3. Did apps approved before April 28 behave differently after the snapshot/cache loosening? 4. Has anyone found a reliable way to force widget propagation/cache invalidation without resubmission? 5. Has anyone seen the `system-connectors exceeded the quota` error correlated with widget/runtime instability? We already opened a formal support ticket with OpenAI. Mainly trying to determine whether this is isolated to our app or a broader published-runtime issue. ---
**Author:** ![Nadja\_Carabulea](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/nadja_carabulea/32/714857_2.png) [@Nadja\_Carabulea](https://community.openai.com/u/Nadja_Carabulea)\ **Post date:** [May 25, 2026, 11:24am UTC](https://community.openai.com/t/published-apps-sdk-widget-updates-csp-behavior-inconsistent-after-redeploy-anyone-else-seeing-this/1381690/2 "2026-05-25T11:24:59Z")
**Update — partial resolution** Thanks everyone who looked at this. Updating to save people time: **Resolved:** - The fullscreen flash-revert was a bug in my own widget code, not a platform issue. My desktop “fullscreen” was implemented as local React state only (no `requestDisplayMode` call), while my `openai:set_globals` handler unconditionally synced local `displayMode` from `window.openai.displayMode`. On desktop the host’s displayMode stays `'inline'`, and a `set_globals(inline)` burst fires ~5ms after the Expand click — the sync handler ran and reverted local fullscreen. Fix: persistent desktop-only intent flag that causes the sync handler to ignore `hostMode === 'inline'` while the user is in local fullscreen. Verified in production. - Bundle propagation actually works. My “stale runtime” symptoms were ChatGPT-side iframe caching that didn’t clear via disconnect/reconnect alone. Fully deleting and re-adding the app in dev mode invalidated the cache and the new bundle loaded immediately. After that, every server deploy propagated within minutes without resubmission. So the freeze model I was assuming (URI frozen → bytes frozen → resubmission required) was wrong — only the URI string is frozen at approval, the bytes behind it serve fresh on every deploy. **Still open / unconfirmed:** - Whether `_meta.ui.csp.connectDomains` and `openai/widgetCSP.connect_domains` are honored by the published runtime. I’ve worked around it by routing widget-\>backend through `callTool` instead of direct fetch, so I no longer need the declarations to work for my own app — but I haven’t confirmed they actually function for anyone. - The `/backend-api/ecosystem/call_mcp 404` and `system-connectors exceeded the quota` errors. Still showing in console. No correlation found with my widget behavior after the fullscreen fix shipped. Possibly host-internal, not app-side. If anyone has data on #1 or #2, still interested. Otherwise no further help needed on the original post. ---
**Author:** ![EricGT](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/ericgt/32/20571_2.png) [@EricGT](https://community.openai.com/u/EricGT)\ **Post date:** [May 25, 2026, 12:39pm UTC](https://community.openai.com/t/published-apps-sdk-widget-updates-csp-behavior-inconsistent-after-redeploy-anyone-else-seeing-this/1381690/3 "2026-05-25T12:39:36Z")
Have you tried using ChatGPT with Deep Research? [https://openai.com/index/introducing-deep-research/](https://openai.com/index/introducing-deep-research/) I used Deep Research to explore a related idea, and it surfaced several relevant documents—some I had not seen before, and others I had seen but should have reviewed more closely. ---
**Author:** ![system](https://us1.discourse-cdn.com/openai1/original/4X/8/7/c/87c2e81543bbb01aa9641aeef8fe14cab5e9590a.png) [@system](https://community.openai.com/u/system)\ **Post date:** [May 28, 2026, 12:40pm UTC](https://community.openai.com/t/published-apps-sdk-widget-updates-csp-behavior-inconsistent-after-redeploy-anyone-else-seeing-this/1381690/4 "2026-05-28T12:40:03Z")
Closed on May 28, 2026, 12:40pm UTC This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.