#ot123_unexpected
feral inletBOT
đ 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/1275163271011368971
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
tepid fjord
Do you have a request ID for the request that's timing out?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
It's possible there isn't one, but I just wanted to make sure you'd checked
feral inletBOT
lethal vessel
Do you have a request ID for the request that's timing out?
Here's how you can ...
I can't find it. The last request id for a connection token is req_uBvt7SWcpafnRu, but that request does go back to the app. I'm able to see the token on the app
hasty hill
Which part is timing out specifically? Is the reader being discovered but then nothing seems to happen when you try to connect with the connection token?
lethal vessel
When I try to the connect to the reader, it doesn't even try getting a connection token. I. just get an error saying Timeout Out waiting for connection token.
At the times that it does connect to the reader it does call the api to get a connection token.
Hopefully that made sense
hasty hill
Can you send the snippet of stripe code that you are calling when this timeout happens and point to the line where it is happening?
lethal vessel
its the same code as the example-app in the stripe-terminal-react-native repo
this does work in beta.19 but not in beta.20
hasty hill
Interesting, so when you revert it starts working again?
lethal vessel
yes. And again it only doesn't work on a fresh install. If I reopen the app everything works fine
hasty hill
Honestly I think it would be best to open this as an issue on the repo page. If our standard code is not working and only the first time, I don't think there will be something SDK wise that you can do to prevent that
lethal vessel
ok thanks