#julio_apple-pay-payment-sheet
1 messages ¡ Page 1 of 1 (latest)
đ 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/1344697982037000222
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- julio_code, 21 hours ago, 13 messages
hi there,
while using apple pay, if I call intentCreationCallback with this values as error:
{
code: 'Failed',
message: 'Your card has insufficient funds.',
declineCode: 'insufficient_funds',
stripeErrorCode: 'card_declined',
type: 'card_error',
}
I got a native crash as in the picture:
It works really good if I'm using just a regular credit card tho, it shows the error even if I send a localizedMessage
Hmm I'm confused... you are confirming server-side here?
yes
What happens if you just pass the error message as opposed to the whole object?
Looks like we just recommend passing back: {error: e.error.message}.to_json
same crash if I call this:
intentCreationCallback({ error: 'Your card has insufficient funds.' });
What version of the Stripe React Native SDK are you using?
And are you testing on an actual device or an emulator?
version: 0.41.0
Testing in an emulator
Can you test with a real device?
I updated to 0.42.0 and it looks like is working
Oh wow that's great
Yep, it's definitely working now, thanks.