{"version":"2.1.269","anchor":"oauth-callback-errors-now-distinguish-state-mismatch-from-mi","canonical_anchor":"oauth-callback-errors-now-distinguish-state-mismatch-from-mi","heading":"OAuth callback errors now distinguish state-mismatch from missing-code","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/oauth-callback-errors-now-distinguish-state-mismatch-from-mi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### OAuth callback errors now distinguish state-mismatch from missing-code\n\nSign-in errors now tell apart a stale callback URL from one that's simply missing an authorization code\n\n**What**\n\nError messages shown during OAuth device or browser sign-in were rewritten to detect a specific case: when a pasted callback URL actually belongs to a different, unrelated sign-in attempt (called a state mismatch), rather than just lacking an authorization code. In that case, the message now tells the user to retry using the URL from the specific sign-in flow that's still open.\n\n**Why**\n\nThis gives a clearer, more actionable error message when a sign-in fails because the wrong callback URL was pasted, instead of a generic missing-code error that wouldn't point to the actual problem.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}