-
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
Docs inconsistency about the location of apply plugin: 'com.google.gms.google-services' #3875
Comments
I've looked at StackOverflow and it looks like the firebase docs used to specify that they should be at the bottom. Example 1, Example 2. They don't anymore, though, so I guess maybe our docs are outdated. |
I may be wrong about the root cause but I think if you don't get this correct, you'll see this with current versions of react-native-firebase that are checking for google API availability:
I got those android compile errors at any rate, remembered this issue and moved the plugin up, then it seemed to work - I may only be describing a tangential problem but the correlation is strong 🤷♂️ |
I was just integrating the new Crashlytics SDK (#3580) into my project, and I ran into this little docs inconsistency.
When setting up the
/app
module, the docs state thatapply plugin: 'com.google.gms.google-services'
should be placed at the very bottom of the/android/app/build.gradle
file.However, in the new setup docs for Crashlytics, that command is actually placed at the top instead. Clearly, order does matter, since
apply plugin: 'com.google.gms.google-services'
is always placed afterapply plugin: 'com.android.application'
, andapply plugin: 'com.google.firebase.crashlytics'
is meant to be placed afterapply plugin: 'com.google.gms.google-services'
(wherever that may be).So what there a reason the docs seemed so insistent that it should be at the bottom? I didn't get any build errors when I moved it to the top
The text was updated successfully, but these errors were encountered: