google-services.json workaround

[existentialstudios]

Devs can't build local versions for debug without google-services.json
Does this file need to be kept confidential when the keys can just be extracted from the apk?

or can google-services be applied in app/build.gradle for 'release' only instead of /build.gradle with something like this:

if (getGradle().getStartParameter().getTaskRequests().toString().contains("release")) {
    apply plugin: 'com.google.gms.google-services'
}

or is there another solution to get a local dev build up and running?

[feruzm]

@existentialstudios have you tried adding empty json file and see if it builds? I remember it used to work

[existentialstudios]

I have not, but I definitely will. Thanks for that tip. I'll report back.

[existentialstudios]

empty file fails for

Execution failed for task ':app:processDebugGoogleServices'.
> Invalid root object

Empty root (just {}) fails for

Execution failed for task ':app:processDebugGoogleServices'.
> Missing project_info object

added project_info...

Execution failed for task ':app:processDebugGoogleServices'.
> Missing project_info/project_number object

Seems it at least needs the project info section...

[feruzm]

Ok, looks like we will create separate (blank) firebase project and provide json file for local versions/builds

[existentialstudios]

I don't know why I didn't think of it, maybe I misunderstood. However, creating my own firebase project with the id "app.esteem.mobile.android" and using the generated google-services.json worked fine.