[flutter_appauth] fixed crash if main activity has been destroyed/unbound#630
Merged
MaikuB merged 1 commit intoMaikuB:masterfrom Oct 26, 2025
Merged
[flutter_appauth] fixed crash if main activity has been destroyed/unbound#630MaikuB merged 1 commit intoMaikuB:masterfrom
MaikuB merged 1 commit intoMaikuB:masterfrom
Conversation
MaikuB
requested changes
Oct 19, 2025
Owner
MaikuB
left a comment
There was a problem hiding this comment.
Thanks for the PR. I left a comment about renaming a variable as ERROR was being repeated. Could you take a look?
...appauth/android/src/main/java/io/crossingthestreams/flutterappauth/FlutterAppauthPlugin.java
Outdated
Show resolved
Hide resolved
MaikuB
reviewed
Oct 20, 2025
...appauth/android/src/main/java/io/crossingthestreams/flutterappauth/FlutterAppauthPlugin.java
Show resolved
Hide resolved
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
We've seen a couple of instances in our crashlytics logs of a crash happening due to the activity object being null when
startActivityForResultis called.Crash log
Solution
A null check with a new error code
Alternative solutions considered
Possibly a more robust solution would be an exponential backoff waiting for the activity to be re-attached with a timeout. Given the maturity of this library though it seems (from what I can see) this issue is very rare, and adding more complexity seems unneeded. Handling it elegently seems sufficient to me.