#cargoinsiten_error
fierce geodeBOT
👋 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/1316527851574395041
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
solar sand
Good question, checking in to whether there are known issues here
To go through the normal debugging stuff, have you tried cleaning and rebuilding?
woven laurel
no I don't believe so but I'm happy to try. are directions for that easily found online?
solar sand
I am honestly not as familiar with RN, this stack overflow has some commands that may help. Still looking in to this error. https://stackoverflow.com/questions/51998636/how-can-i-clean-reset-cache-of-react-native-using-expo-not-sure-if-it-is-cach
Is it possible that other things have changed along with this upgrade? I've seen reports of this happening when live vs test mode keys get mixed up, though that would cause issues with Android too.
woven laurel
I'm sure we upgraded other packages during the upgrade, but as part of my minimal reproduction I did not include any code from any packages except stripe and react-native and I hardcoded the test mode keys pulled from the stripe test dashboard.
I can try the clean and rebuild step tomorrow
solar sand
Also if you print error.code what do we return there?
woven laurel
it was "Failed"
solar sand
Gotta love the informative errors
I am having trouble finding what this may be or how to debug it. I am consulting my colleagues and get back to you with what we can find.
Also what would differ between your local environment and test flight? Are there environmental variables that your code draws from that may be different across the two?
woven laurel
the only thing I can think of is that running locally is using Expo's dev client while the test flight app has been built with EAS build through Expo
solar sand
Gotcha, also I just realized that I may have been mixing some things up. So when confirm is set to true the payment sheet immediately closes with the unexpected error. When it is false and the app crashes do you see any errors printed in your debug logs?
solar sand
Gotcha, and in testlfight these both just operate completely normally with no errors?
Can you try printing out the full error object? It looks like it can have more info on the underlying error in it
woven laurel
{
"stripeErrorCode": null,
"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",
"type": null,
"code": "Failed"
}
correct, in test flight there are no errors
solar sand
We are still looking and trying to reproduce. I will get back with what we can find. Thanks for your patience on all of this. Also if you have to leave soon I can create an email ticket for us to get back to you through.
fierce geodeBOT
woven laurel
that would be great. I am just getting ready to head out. thanks for looking into this
solar sand
Sounds good creating that now. Also do you have the ID of a payment intent that you saw this error with?
One thing my colleague just pointed out is that if you are using a saved payment method, the payment sheet is likely also expecting you to pass a customer ID and ephemeral key. So passing those in may fix this (and is a thing that I can file with my colleagues so we raise a better error message)
fierce geodeBOT
Hello @woven laurel, we have sent you a direct message, please check it at https://discord.com/channels/@me/1316546210223620116
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
woven laurel
here is one of the payment intents I created while reproducing this error "pi_3QUxmfCSFXhQ8LB81DbkBymc_secret_ne2EKKqJfeNopcKgPT5hgI22n". We do pass in the customer ID and ephemeral key in our flow, but I did remove that as part of my minimal reproduction. I can try adding it back tomorrow to see if anything changes.
solar sand
Gotcha, that is helpful to know. So in your actual app this is code for a returning customer paying with an already saved PM?