Menu
We recently implemented Firebase Remote Config on Android w/ v10.0.1. Everything was great until we handed it over for testing and 2/5 devices did not pull the cloud config values. Digging in we discovered that the 2 devices were all running Google Play Services v9.6.83. After moving our app back to Firebase v9.6.0, remote config properly synced on 5/5 devices.
I know we can query whether a Google Play Services update is available and direct the user to update, but this is obviously not ideal. Are we stuck choosing between using older vs newer versions of the Firebase SDK to minimize update friction w/ Google Play Services vs getting the latest fixes and features? Am I maybe missing some config to support backwards compatibility?
665
Core. DEPRECATED: FirebaseApp. configure method is now deprecated in favor of the Firebase.
Especially when you don't have a "digital analytics team" or a "marketing team" as a single app developer. The question is whether Firebase uses the AD_ID internally to track visitors or not, not whom to ask. Ok then. I did some research and and I found that Firebase is not using the AD_ID at all.
From ian-barber's comments we've gone with the following:
Switch from Firebase 10.0.1 to 9.8.0. 10.0.1 didn't introduce anything we need and testing on 9.8.0 has been fine. Unless a new version provides functionality or fixes we absolutely need, we'll probably stagger a version back to decrease risk of failure.
Use GoogleApiAvailability to check for Google Play Services compatibility. If an update is available and the user can update it (per util method), we post a notification encouraging the user to update.
Otherwise, we fail silently.
73
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
