#jarby_code
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/1362575284230160385
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
I may have missed the solution somewhere in this discord, but any help would be greatly appreciated. It doesn't appear to be a popup issue, because refreshing the page works in test and production.
Hi there
Hey!
So embedded components for Connect require authentication, which is why a pop up is trying to open (to ask you for login credentials)
When you say "When I refresh the page, I'm able to log in", does this mean that when you refresh the page and try to open the component, a pop up is able to open and you can log in?
that makes sense. The popup becomes visible, but right after an error message occurs saying there was a problem.
Here's a screen capture
Are you attempting to render the embedded component within an embedded web view by any chance?
yes I am
Aha, that's it. That's not supported at the moment: https://docs.stripe.com/connect/get-started-connect-embedded-components?platform=web#supported-browsers
I mean, it does work....
Looks like others have run into this as well: https://github.com/stripe/react-connect-js/issues/93
just requires a refresh
oh an embedded web view? No I don't think so. Not 100% sure what you mean by that, but this is simply react code in a react app. I'd expect it to work based on that documentation 🤷♂️
I saw that issue, was wondering if the answer was in here somwhere. It's very odd, but we can connect an account just fine by refreshing and retrying
Yeah very weird
Is this the onboarding component?
Yes
;<ConnectComponentsProvider connectInstance={stripeConnectInstance}>
<ConnectAccountOnboarding onExit={() => console.log('exited')} />
</ConnectComponentsProvider>
Just this
Got it. I'm not able to reproduce on my end and all of our React experts have logged off for the day.
Let's take this over to our support channels so we can discuss async
Hello @tiny brook, we have sent you a direct message, please check it at https://discord.com/channels/@me/1362579610453410053
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.