#wise_fox-taptopay-rn

1 messages · Page 1 of 1 (latest)

maiden saffronBOT
gaunt seal
#

Hello! Which version of the stripe-react-native terminal SDK are you using?

wicked hawk
#

Hey 😎 ,

Package.json
"@stripe/stripe-terminal-react-native": "^0.0.1-beta.13",

app/build.gradle
implementation "com.stripe:stripeterminal-localmobile:2.23.1"
implementation "com.stripe:stripeterminal-core:2.23.1"

gaunt seal
#

Interesting... and is this somethign you're able to repro reliably? Or do you just have the one report you're seeing in your logs?

wicked hawk
#

Yes, I believe so. I do not have access to lots of devices on Android 14, but on Google Play Store I have a list of devices that are creating this error.

#

Our customers say they go to take a payment and the app just closes down at this stage.

#

I have shared the issue via google play to the stripe sdk team.

gaunt seal
#

Is this something you're seeing happening recently? I know we had issues with Android 14 in october, but those should be fixed

wicked hawk
#

I would say we noticed it happening about a 3 weeks to a month ago. That is when customers started reporting it to us at least.

gaunt seal
#

wise_fox-taptopay-rn

wicked hawk
#

And I got a team member to test it this morning and that is why it was easy to see in Google Play Store the crash report.

gaunt seal
#

Gotcha - what have you set as the targetSDK?

wicked hawk
#

We have another app running, which is configured in a similar way but not exactly and it has no issues. It is running the following packages:

"@stripe/stripe-terminal-react-native": "0.0.1-beta.13",

implementation "com.stripe:stripeterminal-localmobile:2.20.0"
implementation "com.stripe:stripeterminal-core:2.20.0"

The only other difference between these two app is that the one app which is having the issue is targetSdkVersion = 34 where as the one with out the issue is targetSdkVersion = 33

gaunt seal
#

You need to continue targeting 33 for now

wicked hawk
#

Ah ok great. Do you know if google will allow me to target a lower version?

#

As we have already released to 34

gaunt seal
#

As far as I know it should - that'd be somethign you need to take up with them if they push back

wicked hawk
#

Ok thanks. Will create a build and test. Thanks for your help.

gaunt seal
#

👍

wicked hawk
#

Whilst I have you.... I have one more question.

gaunt seal
#

go ahead!

wicked hawk
#

Just to confirm we cannot run a simulated: true on android. Is that correct?

#

On iOS we can

# 
const getReaders = async (connectionType) => {
        if (!connectedReader && isInitialized) {
            console.log('Discovering readers...', connectionType);
            const result = await discoverReaders({
                simulated: true,
                discoveryMethod: connectionType,
            });

            let error = result?.error;
            if (error) {
                if (error.code !== 'USER_ERROR.CANCELED' || error.code !== 'Busy') {
                    captureException(error, (scope) => {
                        scope.setTransactionName(`getReaders`);
                        return scope;
                    });
                }
            }
        }
    };
gaunt seal
wicked hawk
#

Ok thanks. I will have a look then. Thank you

gaunt seal
#

👍

wicked hawk
#

Hi Karbi, Do you know the time frame on the issue we spoke about getting fixed?

gaunt seal
#

I don't know any specifics on the timeframe - I think the fix is ready for the next release, but I don't know when that release is scheduled for