#collinng_19852
sterile vector
brisk nimbus
Hi there, how can I help?
iron hazel
Hi, I have a production issue regarding stripe-react-native component
The problem is only happening for SG users. I have a video showing that the same app in SIT working well by my taiwan colleague, but failing in Singapore.
Our customer reported this case few days ago and is also an android user
brisk nimbus
Any build configuration difference between these two apps?
iron hazel
We tested with IOS no issue at all
no exactly the same
We even tried using the same account and strangely it works in Taiwan and not in singapore
And we tested in SIT with the Stripe test card, so the card error is bizzare
brisk nimbus
Are you testing with the exact same credit card in these two apps?
brisk nimbus
Sure
iron hazel
Is this a private channel?
brisk nimbus
No, it's public
you can DM to me
btw, are you using the latest stripe-react-native SDK?
iron hazel
Hi, I tried to DM you but failed
We are not using latest stripe-react-native, this app has gone live long back last year and we have not update the payment since no issues so far
brisk nimbus
I'd suggest you to try again with the latest version of the SDK
@iron hazel I've received the video from your DM, let's continue the discussion here.
iron hazel
OK sure
We've tested on an IOS device and found that this works fine even for SG users! So this problem is confined only to Android SG users
We found this issue described by another of your customers that looks similar to our problem below : https://github.com/stripe/stripe-react-native/issues/1475
We added debug log of CardField component after checking some posts of other Stripe users developers online and found that the fields are indeed different for Singapore and Taiwan users as below and in screenshot.
From these investigation, we theorise that since the component is the same, the component must be sending API to some Stripe backend and getting different result for SG and TW users. After card entry completed?
So we're thinking if it is possible for you to monitor the backend API as I simulate again on the app this card entry, so you can see what is the different in SG vs in Taiwan user?
brisk nimbus
I don't think so, the card info integrity check is performed locally in your app, the data is not yet sent to Stripe API.
https://github.com/stripe/stripe-android our SDK is open-sourced, you can visit our github repo and check.
iron hazel
Oh? Then after card entry complete, is there any chance that TW user gets success and SG user gets null for those 2 fields?
Is there some local check in the component using geolocation information?
brisk nimbus
No
iron hazel
How can we debug further on this?
brisk nimbus
My advice is to use the latest version of SDK and see if the problem persists
iron hazel
When we set the build to use latest version of the SDK, we are getting a build error
give me a min ...
We are on ReactNative 0.72.6
brisk nimbus
Run with --debug to get more info
iron hazel
O k we'll give it a try
brisk nimbus
Are you able to compile successfully with the latest Stripe SDK?
iron hazel
Nope
Actually the developer originally working on this left. I need to wait for another dev to have time out from another project to work on this.
This came too suddenly
brisk nimbus
Can you run with --debug and see what additional info that gradle gives us?
iron hazel
I'm not the dev, don't have the build to try out. Need to get a developer from another project to help out. Will update you when I manage to get someone to try this out. Tks.