No Matching Client Found for Package Name (Google Analytics) - Multiple Productflavors & Buildtypes

No matching client found for package name (Google Analytics) - multiple productFlavors & buildTypes

Found this:

The google-services.json file is generally placed in the app/
directory, but as of version 2.0.0-alpha3 of the plugin support was
added for build types
, which would make the following directory
structure valid:

app/src/
main/google-services.json
dogfood/google-services.json
mytype1/google-services.json
...

Source

Source 2

No matching client found for package name (Google Analytics) - multiple productFlavors/application ids

You can Add app for both the application Ids in Project setting in Firebase Console.

By doing so the new google-services.json file will contain two client-info, 1 for each application ID.

Putting a copy of the google-services.json file at at the base of each flavor should solve the issue.

google-services.json No matching client found for package name with any module

That means your app's application ID is "ru.company.acitive.activelife", but that same string wasn't found in your google-services.json file.

Looks like there's a typo in the part where it says "acitive". Should it be "active" instead?

No matching client found for package name '*****.test'

I just downgraded classpath 'com.google.gms:google-services:4.3.4' to classpath 'com.google.gms:google-services:4.3.3' and it worked, I think they changed something in 4.3.4 that we don't know about it yet.

No matching client found for package name (Google Analytics) - multiple productFlavors & buildTypes

Found this:

The google-services.json file is generally placed in the app/
directory, but as of version 2.0.0-alpha3 of the plugin support was
added for build types
, which would make the following directory
structure valid:

app/src/
main/google-services.json
dogfood/google-services.json
mytype1/google-services.json
...

Source

Source 2



Related Topics



Leave a reply



Submit