-
Notifications
You must be signed in to change notification settings - Fork 578
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
Firebase remoteConfig return no value #2186
Comments
I found a few problems with this issue:
|
I have the same issue. |
I've encountered the same issue. The value has been synced in previous remote config SDK version when it updated with the version of 20.0.1 the data was lost. Although can be resolved simply by staling the remote config this is not the convenient way I think. |
This is reproducible, try to build with the version 19.2.0 everything is okay, then rebuild with the version 20.0.1 remote config return no value for the given key |
@AgiMaulana Same here. And when downgrading to 20.0.0 it works fine again. I have downgraded RemoteConfig in my production apk again. |
Looking into this. I'm unable to reproduce it in a new Kotlin app with |
@danasilver I'm seeing the same as others have reported, with a
If, between steps 3 and 4, I "clear data" for this app on the device, everything works correctly. If, instead of clearing data, I set the device to airplane mode before steps 4/5, correct values are still not shown. Because of this, I believe the problematic part is not actually the fetching but the activating of a remote config that is already cached on the device. |
Could the issue be It seems that, if a config was written to disk without personalization (version <20.0.1), then trying to read it with personalization (version =20.0.1) should lead to Line 105 in 0fa174c
|
@bocops Thanks for the help investigating. I'm able to reproduce the issue now with those steps. It does seem like the issue is reading the cached config. Working on a fix for this. |
This issue is really scary. Now that Firebase is recommending BoM (Bills of Materials) for adding dependencies, I don't want to specify an older version explicitly just for Remote Config. |
For everyone who has shipped the remote config 20.0.1 within your production app and already implemented propagating realtime update, you can to try propagate realtime update to stale the local config so the app can rewrite local config with a new one using the new writing scheme. I've fix the issue on production app using that workaround |
We have had the same issue and fixed by noticing when the app has been updated and calling |
Remote Config SDK version 20.0.2 is live now with a fix. A new version of the Firebase BOM (26.1.1) has been released, too, including this version. Thanks all for your help reporting and investigating the issue! |
Was this bug impacting the Flutter version? |
@XinyueZ I don't think this affected Flutter since it looks like the Flutter SDK is using Firebase Android BOM 25.12.0 and this issue was in version 26.1.0 of the BOM. It's fixed in version 26.1.1. |
[REQUIRED] Step 2: Describe your environment
Hello everyone,
Since I've updated the component
firebase-config
from 20.0.0 to 20.0.1, I can't get values fromFirebase.remoteConfig
.Nothing has changed in my code since previous version :
First I fetch and active in my
MainActivity
And then in a fragment I get values :
The text was updated successfully, but these errors were encountered: