{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieytz3yomdiuxfyq6j5sq7vg3whaljlw23t4tyhurttq6s4zj6ebm",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mllrwv37xml2"
  },
  "path": "/t/for-our-gpt-signing-in-isnt-prompted-on-the-mobile-apps-it-works-fine-on-web/1380651#post_2",
  "publishedAt": "2026-05-11T16:29:34.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@tomking"
  ],
  "textContent": "Hey @tomking, that’s confusing, and you’re not the only one seeing web and mobile behave differently here.\n\nMost likely, mobile isn’t surfacing the GPT Action OAuth sign-in challenge properly. For Actions, auth should be configured as OAuth in the GPT editor so ChatGPT shows the “Sign in to [domain]” flow. I wouldn’t rely on `WWW-Authenticate` alone to trigger login.\n\nA few things to double-check:\n\n  * OAuth is configured in the GPT Action settings\n  * Both callback URLs are allowlisted:\n  * `chat.openai.com/aip/{GPT_ID}/oauth/callback`\n  * `chatgpt.com/aip/{GPT_ID}/oauth/callback`\n  * Token response includes the expected fields like `access_token`, `token_type`, and optionally `refresh_token` / `expires_in`\n\n\n\nIf all of that is set and mobile still only says “Stopped talking to api-url,” I’d treat it as a mobile client parity bug and open a support ticket with a repro.\n\n-Mark G.",
  "title": "For our GPT - signing in isn't prompted on the mobile apps (it works fine on Web)"
}