fix(pay_ios): Fixed app freeze after canceling payment#295
Open
avalentic wants to merge 1 commit intogoogle-pay:mainfrom
Open
fix(pay_ios): Fixed app freeze after canceling payment#295avalentic wants to merge 1 commit intogoogle-pay:mainfrom
avalentic wants to merge 1 commit intogoogle-pay:mainfrom
Conversation
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
1 participant
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 had a problem with Apple Pay in our app where the Flutter app would be stuck in
AppLifecycleState.pausedand therefore appear "frozen" to the user if the user canceled payment (sometimes also when the user completed the purchase). That happened to us on one device, iPhone 11 (iOS 18.1.1), when building the app in the release mode with Flutter 3.19.6 and Flutter 3.24.5 (we haven't tested it yet with the latest Flutter version).I'm not too good, and I haven't even written iOS code professionally before, but I came up with this solution, which solves our problem. I don't know if this is good practice, but I wanted to share the fix and hear some constructive comments on whether this is good or bad.