#rodolfo-wom_unexpected
1 messages ¡ Page 1 of 1 (latest)
đ 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/1466447115285827686
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello, this is the video on that behavior
hi there, thanks for providing that video, I'm looking into this now
does this error only occur when you switch away from the app to a different browser?
No, if I switch to any other app it happens
Even minimizing the app will trigger that behavior
Hey, can I add my engineer into this chat?
Don't need to
Can you share the exact code you're using to trigger this in the WebView? Just want to make sure I can reproduce it myself
Also, if you don't use a webview and open the link in a Safari (dedicated browser) instead -- are you still seeing the same behavior?
Also, I wonder if enabling a background fetch might prevent this - https://developer.apple.com/documentation/xcode/configuring-background-execution-modes
You can just @ them in the thread
@old crown hey
Hello eveyone
So I have tested opening the signed URL with both
- WKWebView
- SFSafariViewController
and in both cases I get the same result
Gotcha. Can you try enabling the background mode
Specifically the fetch to see if that makes a difference?
Same results if you pop out the site into a dedicated safari session (not using webviews)?
ussing SFSafariViewController?
No this button in the bottom right corner
I think I have found something, I will investigate it further with our BE team
if we are able to resolve the issue we will close this
@errant sparrow since we have you here, can I get a quick answer on one Stripe behavior, not directly related with this issue, but why do we have this 10 second delay in the end? There's any way to remove it?
You mean the redirect delay? I don't believe there's a way to remove that no..
I think I have found something, I will investigate it further with our BE team
Out of curiosity, what was/is the issue?
I am not sure 100% sure but when we come back to the App we refresh the internal user data, and that looks to be expiring the link
not sure in what way that connects to Stripe yet, so just a theory
I see. If you create a new Financial Connection session for the customer on reload, that may be expiring the old/existing ones