#gordon-macmaster_error
tender anchorBOT
👋 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/1372995523166081114
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
rocky charm
Can you share the request ID (req_xxx) for the error you faced? Here’s how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request
tropic hare
Looking
There are no failing api requests in the last day, but I can recreate the issue in this moment on both the production version and my dev environment
rocky charm
Which step is this error throwing? Is it inside handleConfirmation? Could you also share your account ID (acct_123), so that I can also check from my side if I can find anything? You can find your account ID by logging in to https://dashboard.stripe.com/settings/account. It looks like acct_123
tropic hare
It's failing in the if(error) statement here (never gets to confirmHandler):
async function initializePaymentSheet() {
const { error } = await initPaymentSheet({
merchantDisplayName: business.name || 'Vendora',
customFlow: true,
returnURL: '',
intentConfiguration: {
//@ts-ignore
mode: {
currencyCode: 'USD',
setupFutureUsage: 'OffSession',
},
confirmHandler: () => {
console.log('confirmHandler');
},
},
billingDetailsCollectionConfiguration: {
name: PaymentSheet.CollectionMode.ALWAYS,
},
});
if (error) {
console.log('\n\n\nStripe Error: \n');
console.log(error); <------------------
}
}
Error:
Stripe Error:
LOG {"code": "Failed", "declineCode": null, "localizedMessage": "There was an unexpected error -- try again in a few seconds", "message": "There was an unexpected error -- try again in a few seconds", "stripeErrorCode": null, "type": null}
Account: acct_1MqNndKA7JDnUlfh
rocky charm
Thank you for waiting and sharing the details! Checking if I can find more logs on my end
tropic hare
No problem. If there is any more info I can provide or if you want to see it live, let me know
rocky charm
I don't see any related error on your account. It looks like the request didn't reach to Stripe. Can you check if there is any error or information in your iOS or Android app logs? Does this error throw on both iOS and Android, or just one of them?
tropic hare
I've experienced on iOS, I can try android
Any particular logs you'd like me to look at?
It's happening on both ios and android
rocky charm
I see that the return_url is set to empty string in your code, which is likely the issue
Could you follow this guide to set up a return_url? https://docs.stripe.com/payments/mobile/accept-payment?platform=react-native&type=payment#set-up-return-url
tropic hare
I have tried with a return url and it doesn't work
It also doesn't explain why it just stopped working this afternoon
Just tried with versions of our app going back 50 days and get the same error
rocky charm
This is strange. Could you change a network / wifi? Could you share the mobile app log around "There was an unexpected error"?
We've seen the issue that the network blocked the outgoing request to Stripe which caused unknown error
tropic hare
Just tried on my wifi, a vpn set to nyc, a vpn set to San Fransisco, and my personal mobile data. The error happens on all of them
It's happening to both our dev team as well as our customers
rocky charm
Checking whether this error can be reproduced on our end
tender anchorBOT
cedar sandal
Hi river had to step away but I'm taking over
I'm asking a colleague if they can try to repro and will get back to you
@tropic hare What verison of the RN Sdk are you using?
tropic hare
We're on 0.38.6
cedar sandal
Ok thanks
tropic hare
np
cedar sandal
Also where are you globally while testing this
Are you using any sort of vpn
Any other network change?
tropic hare
I'm on the US east coast
I've tried testing on VPN, off VPN, on mobile data with the same error
Our customers are also seeing this issue out of no where starting this afternoon
cedar sandal
Ok gotcha
tropic hare
It's happening to my both on my dev computer as well as two production devices I have on me
cedar sandal
Gotcha. My colleague is trying to repro rn
tropic hare
Great, thank you
Happy to help however possible, this is part of our checkout flow so its important we resolve
cedar sandal
Yeah my colleague may have follow up questions so I'll keep you in the loop
tropic hare
I'm not sure if this is helps, but if I switch "customFlow" to false (it has been true since day 1 for us) "initPaymentSheet" succeeds" then fails on "presentPaymentSheet"
const result = await presentPaymentSheet();
console.log('result', result);
{"error": {"code": "Failed", "declineCode": null, "localizedMessage": "There was an unexpected error -- try again in a few seconds", "message": "There was an unexpected error -- try again in a few seconds", "stripeErrorCode": null, "type": null}}
My colleague was not able to repro with your exact params and version
Can you share your full code including StripeProvider
tropic hare
Sure, let me compile in an organized manner
cedar sandal
Ok no need actually
tropic hare
One second, I had test code in there. Reverting to what's in prod
tropic hare
Got it
tropic hare
Thank you!
tender anchorBOT
cedar sandal
We're still digging into this
cedar sandal
We don't know yet
It doesn't appear to be widespread at all
Appears to be isolated
tropic hare
Ok
sweet ivy
👋 @tropic hare it looks like the issue here is that there are no acceptable payment methods set on your account right now. Did you recently turn off Cards as an accepted payment method type in your Dashobard at https://dashboard.stripe.com/settings/payment_methods ?
tropic hare
Not that I know of, but I'll ask the team
sweet ivy
Okay well it looks like right now you only have ACH Debit and Bank Transfers enabled.
Since you don't set allowsDelayedPaymentMethods and Bank Transfers are not accepted yet on PaymentSheet there are no viable payment method types here which leads to the error.
Obviously we should improve this error message on our side (we are taking that as feedback)
tropic hare
Is there a way to see a history of when those configs are modified?
Team said we updated invoice config a month ago
But nothing should have been touched since then
sweet ivy
Oh yep it looks like you can see it at https://dashboard.stripe.com/settings/security_history
tropic hare
Reviewing, thank you
It looks like it was updated over a month ago
The ones from today are me turning on cards just now after you said that
That doesn't explain why today people stopped being able to add cards
sweet ivy
Cards have been off for over a month for that PaymentMethodConfig so something else must have changed in that case on your end.
For instance I see examples of you using on_behalf_of
So it seems there are times you are initializing as the Connected Account? Or have you been using Billing instead?
tropic hare
The only time we initialize as the Connected Account is for Stripe Terminal which is in a different app than the one that started throwing the errors today
sweet ivy
In our internal logs I can see these same errors happening on your account over the past week.
And if I zoom out then it appears they have been happening far longer.
I only have internal logs up to 30 days but these same errors, which show up as noPaymentMethodTypesAvailable in our internal logs, were happening all the way back on April 16th.
So unfortunately this seems to have been a latent bug that was just uncovered today...
sweet ivy
Our Mobile Eng team has an action item to improve the error message returned client-side via the SDK.
tropic hare
I can see the errors in our sentry as well but since it say try again in a few seconds we were ignoring it
sweet ivy
Yeah I'm sorry we didn't throw a better error for you here.
Unfortunately since there is such a variety of things server-side they don't always get perfectly mapped to the client-side SDK and a good user-facing error message.
We are working on improving that.
tropic hare
Is there a way I can see the actual error when this happens?
sweet ivy
You are already doing that correctly
tropic hare
I understand that things shouldn't be shown to end customers but I'm not sure how I could have debugged this myself
sweet ivy
Right now the "actual error" is just the generic "something went wrong".
Yeah this would have been extremely hard to debug yourself.
I've passed along that feedback internally to our Mobile Eng team.
Which is why they will improve the error here to make it easier to debug in the future.
But if you do encounter anything you are unsure about then you can also always reach out to us here and we can look too.
tropic hare
Or maybe being able to see it in the dashboards somewhere