Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RemoteConfig.remoteConfig().fetch return .success while the app is offline #4100

Closed
julienbodet opened this issue Oct 16, 2019 · 2 comments · Fixed by #4438
Closed

RemoteConfig.remoteConfig().fetch return .success while the app is offline #4100

julienbodet opened this issue Oct 16, 2019 · 2 comments · Fixed by #4438
Assignees
Milestone

Comments

@julienbodet
Copy link

@julienbodet julienbodet commented Oct 16, 2019

Describe your environment

  • Xcode version: 11.0 (11A420a)
  • Firebase SDK version: 6.10.0
  • Firebase Component: Remote Config
  • Component version: 6.10.0

Describe the problem

RemoteConfig.remoteConfig().fetch returns a .success status (FIRRemoteConfigFetchStatus) even though I disabled the internet connection.

Note: I never configured defaults via setDefaults, and I ran the app for the first time to be sure no previous config was cached.

Steps to reproduce:

  • Create a new project importing Firebase/RemoteConfig through Cocoapods
  • Follow this guide by skipping the step 2 consisting of setting in-app defaults.
  • Disable the internet connection
  • Run the app, the remote config is fetched

What happened? How can we make the problem occur?
I got a .success status and a nil error even though the app is offline and I didn't set any defaults. I expect to get an error instead.

@google-oss-bot

This comment has been minimized.

@rizafran
Copy link
Contributor

@rizafran rizafran commented Nov 27, 2019

Thanks for reporting @julienbodet. I was able to get the same behavior, and I'll file this internally to see what's causing the issue. I'll let you know once I have an update.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants