{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreic54yd6l6l2me3ena53kuepvj55yb6tn2p7clssme456lwyu3ohja",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mlvi7zchfnu2"
  },
  "path": "/t/android-chatgpt-app-error-after-before-tools-call/1380993#post_3",
  "publishedAt": "2026-05-15T13:42:53.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@LarisaHaster"
  ],
  "textContent": "In addition to @LarisaHaster's great response, can you try a minimal static component resource on the same app/tool first?\n\nNo JS bundle, no external assets, no OAuth, no redirects, no custom domain logic, just a tiny inline/static widget and see whether Android reaches `tools/call`.\n\nGiven your logs (`initialize`, `tools/list`, `resources/list`, `resources/read` all 200), the failure likely happens during widget render/bootstrap inside the Android client before the tool invocation path.\n\nAlso useful to inspect:\n\n  * exact `resources/read` payload + response headers\n  * tool descriptor `_meta` (especially `openai/outputTemplate`, `ui.resourceUri`, widget accessibility flags)\n  * CSP + widget domain config\n  * Android logcat / WebView console errors\n  * whether the widget depends on:\n    * browser-only APIs\n    * third-party cookies/storage\n    * redirects\n    * cross-origin assets\n    * service workers\n    * dynamic imports/module loading\n    * mixed-content HTTP assets\n\n\n\nIf the minimal component works, it points more toward CSP, asset loading, Android WebView compatibility, auth/session handling, or frontend JS crashing before the tool call.\n\nIf even the minimal widget fails before `tools/call`, that’s much stronger evidence of an Android ChatGPT client/App SDK regression rather than your server/tool handler.\n\nFeel free to open a support ticket to support@openai.com with request_IDs and any details that would be helpful as mentioned above.\n\n-Mark G.",
  "title": "Android ChatGPT app error after before tools/call"
}