#liam-hunt-bonterra_error
raven orbitBOT
👋 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/1361353173440401521
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
bitter matrix
Hi there 👋 thanks for taking the time to raise this! We came across this bug recently as well and our teams are working on building a fix for it.
keen beacon
Ok thank you! I did want to ask - is this feature expected to be stable? I ask in part because it isn't documented on https://docs.stripe.com/elements/express-checkout-element#supported-browsers and caught us a bit by surprise, also we've seen the button inconsistently across browsers
We're releasing our donation form soon and want to prioritize stability, so it'd be helpful to either: a) be able to turn this non-apple-device-ApplePay behavior off, or b) have a workaround until the shipping name bug is fixed. Thanks again!
bitter matrix
This is a new feature that Apple recently launched, that we're working on implementing into our flows. It's currently being rolled out in such a way that only a very small portion of those eligible to use it will see it, to help us be able to spot issues like this and correct them before rolling it out more widely.
Unfortunately, there is no way to be opted out of these kind of slow releases. But I will make sure the team understands the impact that this approach has on your integration and launch.
keen beacon
Ok thank you! This all makes sense. Two final questions:
- Is there any good way to check on the status of this bug, other than just trying the ApplePay flow every once in a while?
- Does the workaround I described in my original message of passing a shipping name
stripe.createConfirmationTokenhttps://docs.stripe.com/js/confirmation_tokens/create_confirmation_token#create_confirmation_token-options-params-shipping seem dangerous / particularly inadvisable?
bitter matrix
We'd have to move this conversation to a support case for ongoing tracking of the release of that fix. I can't give any sort of firm commitment of when the fix will be released, but we are hoping to deploy that today. Let me know if you want to move this discussion to a support case, I'll have our bot DM you a link for that.
The workaround doesn't sound like it would cause problems, as long as you don't have any sort of downstream flow that triggers purely on the presence of shipping information. But I'd strongly recommend testing that pretty extensively in testmode before trying it in production.