[flutter_appauth] fixed crash if main activity has been destroyed/unbound #630
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.