-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
fix(app, android): require default firebase.json boolean key #4791
Conversation
This fixes the case where firebase.json existed but the key being query was missing. Previously the config system would silently fail on the missing key and return false even though the default for some keys should be true In particular this caused analytics auto collection to be disabled if you had a firebase.json but no analytics_auto_collection_enabled = true entry, even though the default should have been true Credit to @WadhahEssam for discovery, diagnosis, and general solution
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/invertase/react-native-firebase/8cxwoofco |
As soon as this passes CI I will merge and release 10.4.2 @WadhahEssam |
Codecov Report
@@ Coverage Diff @@
## master #4791 +/- ##
=======================================
Coverage 89.09% 89.09%
=======================================
Files 109 109
Lines 3712 3712
Branches 347 347
=======================================
Hits 3307 3307
Misses 363 363
Partials 42 42 |
Actually @WadhahEssam - since I know you are watching this :-), it will be 10.5.0 because I'm going to merge the feature / minor bump to the underlying SDKs when they finish too #4792 |
…se#4791) This fixes the case where firebase.json existed but the key being query was missing. Previously the config system would silently fail on the missing key and return false even though the default for some keys should be true In particular this caused analytics auto collection to be disabled if you had a firebase.json but no analytics_auto_collection_enabled = true entry, even though the default should have been true Credit to @WadhahEssam for discovery, diagnosis, and general solution
…se#4791) This fixes the case where firebase.json existed but the key being query was missing. Previously the config system would silently fail on the missing key and return false even though the default for some keys should be true In particular this caused analytics auto collection to be disabled if you had a firebase.json but no analytics_auto_collection_enabled = true entry, even though the default should have been true Credit to @WadhahEssam for discovery, diagnosis, and general solution
Description
This fixes the case where firebase.json existed but the key being
query was missing. Previously the config system would silently fail on
the missing key and return false even though the default for some keys
should be true
In particular this caused analytics auto collection to be disabled
if you had a firebase.json but no analytics_auto_collection_enabled = true entry,
even though the default should have been true
Credit to @WadhahEssam for discovery, diagnosis, and general solution
Related issues
Fixes #4784
Obsoletes #4786 (different API shape, same solution though)
Checklist
Android
iOS
e2e
tests added or updated inpackages/\*\*/e2e
jest
tests added or updated inpackages/\*\*/__tests__
Test Plan
I tested:
Seems to work fine although I did discover some problems and was able to break my tests - the tests I was doing were testing it and I proved it locally by toggling back and forth
the logic is not engaged if firebase.json is not present
Think
react-native-firebase
is great? Please consider supporting the project with any of the below:React Native Firebase
andInvertase
on Twitter