#ferriv3ra_error

1 messages ¡ Page 1 of 1 (latest)

olive spearBOT
#

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

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

wet depot
#

Hi there! Can you share your device serial number so I can investigate?

modest juniper
#

This is one of them WPC323228035178

wet depot
#

Hmm, it looks like I can't pull up the logs for that type of device. Do you have any logging on your side that may indicate any other errors?

modest juniper
#

All devices are brand new; the errors are more related to Android devices, and are both described in the question; no other errors.

wet depot
#

I know there was a recent issue with versions that can cause terminal readers to get stuck during updates and lose connections, trying to determine if that was the cause

#

Can you share what is in your android/build.gradle file so I can look at the versions to see if this is related?

modest juniper
#

I'm using the react native SDK. There is not too much in the file

// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
repositories {
google()
mavenCentral()
}
dependencies {
classpath 'com.google.gms:google-services:4.4.1'
classpath('com.android.tools.build:gradle')
classpath('com.facebook.react:react-native-gradle-plugin')
classpath('org.jetbrains.kotlin:kotlin-gradle-plugin')
}
}

allprojects {
repositories {
google()
mavenCentral()
maven { url 'https://www.jitpack.io' }
}
}

apply plugin: "expo-root-project"
apply plugin: "com.facebook.react.rootproject"

olive spearBOT
stuck hawk
#

Hi, I'm getting help from a teammate who has more expertise that I do here. Hang tight

jade crypt
#

Hello
Generally, when you see

NETWORK_ERROR.NETWORK_ERROR_CONNECTION: Execution error while retrieving connection token.
It means the SDK is unable to retrieve the Connection Token from your own server endpoint

modest juniper
#

Does that mean it's a backend issue? If so, why is it happening? because it's mostly happening on Android devices and not in all users, just about 25%

jade crypt
#

It could be a backend issue on your server. Stripe won't have much visibility into this. You should look into your application & server logs and then compare timestamps to see:
1/ if the application made the request and failed
2/ And if the server received a request but failed internally

modest juniper
#

Usually, it is a timeout error

jade crypt
#

Yeah that generally means that either there was an issue with the network where the request died before completion OR there was an issue with your backend server that didn't respond to the request the Application made.

modest juniper
#

I believe that something is going wrong when the update is starting, and the worst is that the update is required because all devices are brand new

jade crypt
#

The update wouldn't cause an issue with Connection Token retrieval or timeouts

modest juniper
#

Thank you for your support, let me debug a bit more if it's needed, I'll be back