call ON_FRAGMENT_CREATED before INIT_PAYMENTSHEET to prevent potential null pointer crashes #783
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.
We noticed that we get from the Flutter Stripe community some nullpinter exceptions that happen a bit randomly. See issue flutter-stripe/flutter_stripe#416 . In my current project I also saw this issue happen and it looks like a race condition that causes the following cast being executed in the StripeModule while the fragment is being null.
After some investigation it looks like the promise is being resolved before the fragment is created. This fix will prevent this from happening.