Skip to content
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

Getting stuck in Tap to Pay Screen when using auto-reconnect #338

Open
ronzohan opened this issue Dec 9, 2024 · 8 comments
Open

Getting stuck in Tap to Pay Screen when using auto-reconnect #338

ronzohan opened this issue Dec 9, 2024 · 8 comments

Comments

@ronzohan
Copy link

ronzohan commented Dec 9, 2024

Summary

I'm encountering a bug right now that happens when you try to collect payment and then try to background the app. In most occasions, the Tap to Pay screen will just Cancel automatically. But sometimes, the Tap to Pay screen will show up but it will get stuck.

The TapToPayConnectionConfigurationBuilder is currently set to auto-reconnect on reader disconnection in the setup above.

Code to reproduce

Here is a video showing me trying to reproduce it (at around 00:10 where the Tap to Pay screen gets stuck). https://drive.google.com/file/d/1-FHLkrYrhhFiOqWqUhqAo3PqWlgsEmnV/view?usp=sharing

iOS version

iOS 18.1.1

Installation method

SPM

SDK version

4.1.0

Other information

@maggiewhite-stripe
Copy link

@ronzohan Thanks for reporting this issue. I noticed that in the video, you are backgrounding the application immediately after pushing the "pay" button. Does this issue happen if you background the application after the payment screen is already being displayed? Can you share a payment intent when this issue is happening so we can find the logs?

@yliu342
Copy link

yliu342 commented Dec 18, 2024

Does this issue happen if you background the application after the payment screen is already being displayed?

No, if the payment screen is shown, then when to try to background the app it will simply dismiss the tap to pay payment screen first.

Can you share a payment intent when this issue is happening so we can find the logs?

Unfortunately Ron is on holiday until the 10th of Jan. I will try to replicate on my device and if I can replicate then I will reply here with an payment intent id

@yliu342
Copy link

yliu342 commented Dec 18, 2024

Hi @maggiewhite-stripe I did reproduce it once pi_3QXC8EEhqOG9KqpJ0Jgzx2HR this is the payment intent id. And this pi_3QXCESEhqOG9KqpJ1ylU7gkz as well

@yliu342
Copy link

yliu342 commented Dec 18, 2024

I think I found a relative reliable way to reproduce:

  • press a button to trigger the payment screen. (payment screen will take a small amount time to appear)
  • Then quickly background the app (at this stage payment screen is still preparing)
  • On the home screen, try to wipe the home bar which will try to switch app, then if you do it in the right time(i.e. the same time the payment screen will be presented) Then you will see the app get stuck for some time like 10-20 seconds.

@maggiewhite-stripe
Copy link

@yliu342 Thank you! I was able to pull up the logs on our end from pi_3QXC8EEhqOG9KqpJ0Jgzx2HR. The UX shown here is owned by Apple's logic, so I've reported this issue to them and will let you know if there are any updates I can share.

@maggiewhite-stripe
Copy link

@yliu342 Apple has asked if you can provide a sysdiagnose (iOS system log file) to help them debug. The instructions on how to collect a sysdiagnose are here:
https://it-training.apple.com/tutorials/support/sup075/

@ronzohan
Copy link
Author

Hi @maggiewhite-stripe, if it helps, I've also been able to reproduce it again with this payment intent pi_3QgvbFEhqOG9KqpJ0DkNUKeO.

I've also uploaded the sysdiagnose in this Google Drive link since it was quite large (~300mb) to be attached here in GitHub

@maggiewhite-stripe
Copy link

maggiewhite-stripe commented Jan 13, 2025

@ronzohan Thank you for the quick response! I shared the sysdiagnose with Apple and the reader serial number for the payment intent you shared.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants