Repository navigation
fix: do not forward redirects to a completed session on iOS #1152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
zibs
merged 2 commits into
FormidableLabs:main
from
federicobartoli:fix/ios-completed-session-crash
Oct 19, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "react-native-app-auth": patch | ||
| --- | ||
|
|
||
| Fix an iOS crash ("An OAuth redirect was sent to a OIDExternalUserAgentSession after it already completed") by not keeping an authorization or logout session that completed synchronously, and by forwarding at most one redirect to each session. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new
__block BOOL flowCompletedflag is set in three callbacks (lines 405, 442, 568) and read once on this line 478 (and again at 581 inendSessionWithConfiguration:). The invariant "callback fired synchronously → flag is YES → drop the session" lives in the heads of maintainers, not in the code. AppAuth 2.0.0'sOIDAuthorizationService.presentAuthorizationRequest:factory returns the session unconditionally even afterdidFinishWithResponse:fired synchronously, so a future present-callback author who forgets to set the flag silently re-introduces the exact crash this PR closes — no compile error, no test failure.Why it needs to change
OIDAuthStateoverload the author hasn't read). Each new callback widens the open trap.Code suggestion
Wrap the flag-set inside a tiny adapter the present callbacks always go through, so
flowCompletedis unreachable directly:Or, more aggressively: factor the six present calls plus their six callbacks into a single
-presentAndMarkFired:externalUserAgent:callback:helper, and a sibling for end-session. The flag then exists in exactly one location per flow type.Why this differs
flowCompleted = YES;line plus the inline__blockdeclaration (18 lines removed, ~24 added across both methods). The maintainability win is bigger than the diff cost._currentSessionis nil afterwards" trivially possible; today the same test would need to hook into six separate callback bodies.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quick review, and for the approval!
Good point about the invariant. Today the three callbacks set the flag themselves (the six
authorizecall sites share two callback blocks, plus one forlogout), so a new callback could indeed skip it. I'll go with your second suggestion and route every flow through a single helper that wraps the callback and decides whether to keep the session, so the bookkeeping lives in one place. I'll re-run the verification steps on the simulator and push an update.