Published Apps SDK widget updates / CSP behavior inconsistent after redeploy — anyone else seeing this?

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:

  • /backend-api/ecosystem/call_mcp 404

  • QuotaExceededError ... system-connectors exceeded the quota

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.