#Pip-young-RN
1 messages ยท Page 1 of 1 (latest)
Hello ๐
Give me a moment to look into it
This error is super generic at this point so there could be many reasons why it'd show up
Can you confirm the following;
- Are you using a FlatList higher up in your view hierarchy? If so, can you remove it and check whether you still get the same error?
- Are you using a ScrollView?
- What version of the Stripe React Native library are you using?
- Can you also include some your code so I can see where you're using StripeProvider?
This thread has been archived. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
Sounds familiar to: https://github.com/stripe/stripe-react-native/issues/508
Hi thanks for reopening!
I'm not using a flatlist. I am using a scroll view but I've just removed it and tried again and still no joy.
version 0.2.4
I'm pretty confident that the stripe provider is set up correctly, its in my main app file and I'm able to use confirmPayment on another screen in the app.
I did had a look through that thread before reaching out on here but couldn't find anything that worked based on the responses in there.
Would there be an adverse effect to having the multiple stripe providers on a screen by screen level rather than one in the main app file do you think? Could that change anything?
That sounds like it could cause unintended side effects, yes
yeh... i've not tried it because i didnt think it would work
Is there another way i could confirm the setup intent?
Maybe some way to send a link to the customers email for them to confirm a card, does stripe have anything that does that out of the box?
Not with Setup Intents, no. We have recovery flows but only really for off-session payments that have payments that require action
oh that could work.. does that add a new off session payment method to the customer?
do you have a link to the docs if so?
Well, it assumes that you've already got a recurring subscription in place
we do
Then why are you trying to confirm a Setup Intent?
There's no docs, for it. You should configure it in your Dashboard: https://stripe.com/docs/invoicing/automatic-collection#secure-emails
great thanks i'll have a look at that
Try the Customer Portal: https://stripe.com/docs/billing/subscriptions/integrating-customer-portal
๐ thanks, i'll see if we can use that instead
Really though, you should figure out why you're seeing the error you're seeing. My guess is the multiple StripeProviders in the tree is related
we dont have multiple stripe providers, i was just asking about that as a suggestion of something to try, but i havent tried it
we just have one in the main app.tsx file
ideally it would be good to do it in app yeh
Got it. Yep, it's a common/known bug (as you can see from GitHub) without a known resolution right now unfortunately
we've sunk quite a few devs days into trial and error on this. Is there any way that Stripe might be able to add a bit more detail to the error to say what is actually missing?
or could it be the error doesnt actually match the issue
That's the thing: there's likely nothing missing
yehh... im pretty sure theres nothing missing
But for some reason the Elements instance from your app tree isn't being passed to the confirm function
got it
I'll do more digging around there
It's not a great user experience but since i know confirm payment works it's tempting to charge them a small fee and then refund them just to get the confirmed payment method on their customer
confirmPayment works in the same application stack?
yep
Like if you should swapped out confirmSetup for confirmPayment in the exact same component file?
I'll try that, its on another screen at the moment.
Yeah, if confirmPayment also fails there with the same error then I guess it's something in that component tree
makes sense
and if it doesnt fail... ๐ฌ
Anyway.. I have a few leads to go on with my debugging now so thank you
Np!