#mattiaferrari_code

1 messages ¡ Page 1 of 1 (latest)

lone viperBOT
#

👋 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/1397947540284116993

📝 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.

dim cloak
#

I am using stripeterminal android sdk version 3.5.0

proud marsh
#

hey there, taking a look

#

I know there was an SDK issue with google play integrity checks last year, so i suspect you might need to update your SDK version

#

trying to find info on that

dim cloak
#

Ok so wait, so you are basically telling me that tap to pay no longer works with sdk version lesser than 4.0.0?

proud marsh
#

org.chromium.net.impl.NetworkExceptionImpl: Exception in CronetUrlRequest: net::ERR_NAME_NOT_RESOLVED
this part suggests there might be a network issue with your device reaching Google's integrity service/servers

dim cloak
#

Oh ok

#

So in the end tap to pay won't work if the sdk version is less than 4.0.0 due to this api

proud marsh
#

It's possible, though that may depend on your app & related integrity checks.

#

I would suggests trying to the update to see if it resolves your issue, and note that 4.5.0 surfaces better errors related to attestation/integrity checks:
https://github.com/stripe/stripe-terminal-android/issues/580#issuecomment-2913066378

Sounds good. Because this error is being reported directly to us by the Play Integrity API, I don't have any remediation suggestions other than what's recommended by Google for this error code: https://developer.android.com/google/play/integrity/error-codes

In Terminal SDK 4.5.0 you'll start to receive a more useful exception message from connectReader() when encountering a failure mode like this. I'll update this thread once this version is available.

#

from the 4.5.0 changelog:

Tap to Pay
Updates
Improved messaging for Play Integrity API failures during the reader connection process. Fixes issue 580.