Android ChatGPT app error after before tools/call

OpenAI_Support:

support@openai.com

Hi Mark,

Thanks for the guidance. We followed your suggested path and unfortunately still have not isolated the root cause.

The short version: the problem is not limited to the resume widget JS boot. We tested a minimal static widget resource and Android still showed the same generic error.

What we tested:

1. Minimal static component/resource on the same app/tool

   • We replaced the build_resume widget resource with a tiny inline/static HTML response.

   • No React.

   • No bundled app JS.

   • No external JS/CSS assets.

   • No OAuth.

   • No redirects.

   • No custom domain logic.

   • No notifyIntrinsicHeight.

   • No dynamic imports.

   • Visible body text only: Resume builder static probe loaded.

Android did reach resources/read.

Example logged sequence:

• initialize 200

• notifications/initialized 202

• tools/list 200

• resources/list 200

• resources/read 200 for ui://views/apps-sdk/build_resume.html?..

• response MIME: text/html+skybridge

• static HTML size: 1391 bytes

• response meta keys: openai/widgetCSP, openai/widgetDomain, openai/widgetDescription, openai/widgetPrefersBorder

• then Android still showed the generic error

So the static resource did not make the resume tool path reliable.

1. Separate control tool/widget We added a separate simple control tool/widget, a smiley-face probe. In some runs this worked: Android invoked the tool and rendered the widget. That suggests the tunnel/server and Android app connection can work in principle.

However, the resume tool continued to fail, especially once resume details were provided.

1. Tool/schema/descriptor reduction We tried reducing the resume tool surface in multiple ways:

   • simpler description

   • simpler schema

   • flat resumeDetails input instead of nested profile

   • renamed tool variants

   • plain tool without widget binding

   • empty resource list

   • cache-busted server/widget versions

   • fresh Android app connections

These did not consistently remove the generic Android error.

What should we do?