#eeynard_unexpected
wind pivotBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1288880013134790730
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
muted helm
What type of reader are you using?
fast furnace
tap to pay on react-native-stripe-terminal
"@stripe/stripe-terminal-react-native": "^0.0.1-beta.21",
"expo": "~50.0.19",
muted helm
Oh ok. So what connection is your app trying to make specifically when you put it in the background?
fast furnace
i think it's during the connectLocalMobileReader
Might be the cas also on discoverReaders but I'm not sure for this one
I don't know if it's related to this issue https://github.com/stripe/stripe-terminal-react-native/issues/595
but it does not happen at the same moment for me
muted helm
No seems slightly different than that one
Also you are on the latest version, and that bug has been fixed afaik
fast furnace
ok
muted helm
Oh actually it's not fixed
The fix was in 3.9.0 of the ios sdk
But latest react native sdk uses 3.8.3
But your issue is happening at different stage anyway it looks like so likely unrelated
But for sure it's on connectLocalMobileReader? And you're not sure about discoverReaders?
fast furnace
Yes
i had this error from the sdk
Could not communicate with the reader. Try resetting or recharging the reader.
I also had this error
Unable to communicate with the reader while the app is in the background. Try again.
muted helm
Why do you need to connect to the reader while it's in the background
Most flows do this while app is in the foreground
fast furnace
I don't need to do it but some of our users are puting there app in background whilst the connection is pending and the it fails. We are advising them not to do it but you know how it goes with users ... haha. On android it works though
fast furnace
oh ok, so is there any recommendations on how to handle this ?
wind pivotBOT
muted helm
You can see that that's slightly different from the android behavior: https://docs.stripe.com/terminal/payments/connect-reader?terminal-sdk-platform=android&reader-type=tap-to-pay#handling-disconnects
Android OS terminates the Tap to Pay reader service due to memory constraints.
The device loses internet connectivity.```oh ok interesting. Thank you for that. I'll look into it !
muted helm
No problem
fast furnace
have a good one !