#Ortis-payment-element-loading
smoky marsh
upper widget
Hi 👋 sorry, but I don't think there is enough context here for us to immediately know what is going on. It looks like the Payment Element was mounted, but failed to (or was taking a long time to) load.
Does trying to drill into where that error is coming from provide you any additional insight?
abstract fox
In the debug frame of VSCode I see a bit more info
It looks like the error is coming from stripe.js
upper widget
That error makes it look like you may be serving the site over HTTP rather than HTTPS, which we do not permit for livemode transactions.
abstract fox
I am running in test
upper widget
Oh, okay, so I think that is just a warning rather than an error then, and that the uncaught errors under it may be more problematic.
You mentioned this was working a couple days ago, have any recent changes been made to the app? If so, does rolling those back cause the form to load again?
abstract fox
I havent commit since...
I just got it to work again by hardcoding the client secret to the Elements, I rolled back to using a variable -> didnt worked. Use hardcoded value again, doesnt work
This error is not consistent
Could React.StrictMode change Strip JS behavior in some way ?
upper widget
Sorry, I'm not sure, I'm not familiar with React.StrictMode. For each of these tests that you've run, have you looked for any errors? If hard-coding the client secret worked (at least initially) then maybe there is a problem with your process that generates those client secrets. Have you added logging to ensure that value is getting generated as expected?
abstract fox
Yeah, I logged the id and it matches the one I see on the dashboard
upper widget
I'm sorry, I'm not sure what could be going on then and think you'll need to do some further investigation. When you hardcoded the client secret and that worked, did you still encounter the uncaught errors that are shown in your screenshots?
Ortis-payment-element-loading
abstract fox
no
upper widget
Gotcha, I think whatever is causing those errors is likely the culprit then.
abstract fox
Yes, but there is no info whatsoever on what causes these error. I am completly in the dark
Again, I managed to show the PaymentElement on a bare page, rolled back to previous code and back again to bare page -> not working
upper widget
The errors seem to indicate that an undefined property of a variable is being referenced, but I'm not able to gather much more insight than that from the provided information. I'm not sure what changes were being made when you rolled backwards or forwards, so I'm not sure what the expected outcome of those changes were.
Is your test site publicly accessible?
abstract fox
OK, so: I am developing in VSCode and debugging in a standalone, no extension Chrome. When I load my test page in this debuggin chrome instance, it doesnt work (normal and private mode) BUT when I load it in Brave it does work ...
What kind of sorcery is this
abstract fox
The errors seem to indicate that an undefined property of a variable is being re...
Not public no
upper widget
Sorry, but I don't think there is any more insight that I can offer without trying to interact with the site. If during your investigation you find that those errors are being surfaced by the current version of stripe.js, then please let us know so we can look for ways to minimize the chance of an uncaught error being thrown.
abstract fox
ok