#motoraton8
jolly lintelBOT
Hello! We'll be with you shortly. 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.
- motoraton8, 5 hours ago, 4 messages
lunar shoal
Can you check your dashboard logs and tell me if you see an API request that gets this error? https://support.stripe.com/?contact=true
Also can you send me the text of the code for your confirmSetupIntent call?
molten zodiac
`const { error } = await confirmSetupIntent(clientSecretId, {
paymentMethodType: 'Card'
});
<CardField
postalCodeEnabled={false}
countryCode={Config.COUNTRY_CODE}
style={cardFieldStyles.cardStyle}
cardStyle={cardFieldStyles.cardInputStyle}
onCardChange={cardDetails => setCardFormDetails(cardDetails)}
/>`
That does look pretty close to what I can see in our docs. Trying to figure out what you may need to do here. https://stripe.com/docs/payments/save-and-reuse-cards-only?platform=react-native#react-native-collect-card-details
molten zodiac
yes, it's very weird, I've tested with several versions and the same error.
fallen walrus
Was this working at some point or under other conditions and something has changed in what you observe, or was this never working?
molten zodiac
#1178700251616526426 message I don't have permissions at the moment, I will be able to check it soon
molten zodiac
Was this working at some point or under other conditions and something has chang...
yes, it worked until beginning of last week aprox
fallen walrus
Did you change/upgrade any part of your integration?
molten zodiac
nothing relevant, the implementation is the same, using <StripeProvider />
I tried several solutions but without success https://github.com/stripe/stripe-react-native/issues/508
fallen walrus
nothing relevant, the implementation is the same, using <StripeProvider />
Can you explain more? What did change?
molten zodiac
I would say nothing related to Stripe, related with a loader and the way that we charge the publishableKey
fallen walrus
related with a loader
this is suspicious
If your loader ends up unmounting the card at the wrong time, it could cause this
molten zodiac
before those changes still failing, we made some test releases all of them are failing with same error
