The createCheckoutSession.url redirect server side creates a CORS error so Stripe recommends a client side redirect on success of the submit form, using “window.location”, eg the browser component. But the goto action is silently failing to do the redirect (I do get a 200 response but page remains idle)
Checked the code for you at the line it generated the error. I could probably improve the code there a bit, but the error comes when the url is not given, so the expression returned null or undefined.
“null/undefined” yet my set value does return the url from the session create which I use in my Browser goto. But I get it… there is a mysterious “redirect” with null value.
But was the value set at the moment you called the goto action, so didn’t you perhaps call the goto action to early before that value was set. At which moment do you call the action, perhaps you could use a flow instead with a wait step before calling the goto action to have a short delay to make sure the value was set.
Not understanding how your suggested flow makes it better.
UPDATE: I tested both with a 2s wait and with a condition (if a set value has a url then run goto) and the browser is still idle, with a redirect: null in the dev tool response.
The updated version should give a warning in the browser console when there is no url passed to the goto action and it should also output the data variables from that moment.
Thanks Patrick, so I’ve replaced the file inside C:\Users\fredk\WprojectX\dmxAppConnect\dmxBrowser then uploaded the installed file to our remote. I get this message in the browser console:
The source maps show the wrong code, the warning is something that I added. It should also output the data structure in the console, you can use that to see which data was set at the moment of the warning.