Unable to connect to the server. Check your connection and try again.

[johnjeremih]

[READ] Step 1: Are you in the right place?

Issues filed here should be about bugs in the code in this repository. If you have a general question, need help debugging, or fall into some other category use one of these other channels:

• For general technical questions, post a question on StackOverflow with the firebase tag.
• For general Firebase discussion, use the firebase-talk google group.
• For help troubleshooting your application that does not fall under one of the above categories, reach out to the personalized Firebase support channel.

[REQUIRED] Step 2: Describe your environment

• Android Studio version: 2023.1.1
• Firebase Component: Remote config
• Component version: com.google.firebase:firebase-config-ktx:21.4.1

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

I'm using real-time remote config and I'm getting these errors

What happened? How can we make the problem occur? This could be a description, log/console output, etc.

Relevant Code:

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[argzdev]

Hey @johnjeremih, thanks for reaching out. Looking through your code snippet, at first glance there doesn't appear to be any obvious reason why this issue is happening. Are you constantly able to reproduce this behavior? Or is there a certain condition to encounter this behavior?

[johnjeremih]

@argzdev these are the errors I'm getting on Firebase

[lehcar09]

Hi @johnjeremih, thank you for those details. I was able to encounter the issue once in the BOM version 32.2.0, however, I wasn’t able to reproduce the issue.

It seems to me that the behavior you’re experiencing is similar to this report (#5159). Based on this comment, according to the investigation of our engineers, the behavior is intended.

“The reason why Crashlytics says it in the background for these exceptions could be due to a race condition between when our SDK thinks it's in the background compared to when Crashlytics is in the background. In the stack trace, there is a reference to a method called notifyRCInstances. This method is only called when the app switches from background to foreground or vice versa. And in the case of background to foreground we retry the connection automatically which is what it looks like is happening. So in conclusion I think connections aren't being made in the background, it just looks that way due to a race condition between real-time and crashlytics logging.”

As mentioned in case, It should be safe to ignore.

With that, I'll close this ticket now. Feel free to let me know if you think this is a mistake. If so, please provide with us a minimal reproducible example or steps to reproduce this behavior showing repeated calling of the exception.

[johnjeremih]

I just got this error "Config update error with code: CONFIG_UPDATE_STREAM_ERROR"

[cotchoninha]

I'm having the same problem, but on my iOS application. The config listener used to work in the past and now I keep getting Optional(Error Domain=com.google.remoteconfig.update.ErrorDomain Code=8001 "Unable to connect to the server. Check your connection and try again." UserInfo={NSLocalizedDescription=Unable to connect to the server. Check your connection and try again.})

[asetiyadi-MLB]

I have similar error in iOS and it is happening whenever the app is brought into the foreground from background mode. iOS Firebase SDK 10.22.1

Error Domain=com.google.remoteconfig.update.ErrorDomain Code=8001 "Unable to connect to the server. Check your connection and try again." UserInfo={NSLocalizedDescription=Unable to connect to the server. Check your connection and try again.}

[lehcar09]

I just got this error "Config update error with code: CONFIG_UPDATE_STREAM_ERROR"

Hey @johnjeremih, this looks like a different issue to me. Please file a new issue with the details to help us conduct initial investigation.

[lehcar09]

Hi @cotchoninha and @asetiyadi-MLB, as mentioned in my comment, this is an intended behavior and is safe to ignore.

If you can provide with us a minimal reproducible example or steps to reproduce this behavior showing repeated calling of the exception we can open an investigation. Also, I would suggest filing the issue to the Firebase iOS Repository for better tracking and have the right set of Engineers to investigate the issue. Thanks!