ryanturnbulleuc_code

[clear holly]

👋 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/1225233954483863634

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[leaden haven]

Normally it means you are invoking that code from a function catching the user interaction. Could you share your whole JS code?

And a screenshot of the error

or better a public accessible URL that we can look outself

[half salmon]

Error

Yeah that's exactly what we're doing - somewhat out of necessity.

The code in the ticket is essentially what we're doing at the top of our submit handler. The problem is that the confirmSetup redirects users, so we'd never be able to run updateProfile without it happening beforehand

Just wondering if we have any options here? And/or is this a common issue?

Delaying the redirect for example

[leaden haven]

This is a common issue, truth is Apple is unhappy about dev doing additional work before triggering their ApplePay sheet

[half salmon]

Damn, so no workarounds I assume?

[leaden haven]

Unfortunately no AFAIK. You can think of running updateProfile somewhere later, ie after the confirmation is done