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

Question

Context:

I'm trying to set up Google Analytics for my app. (having 4 custom buildTypes and more than a few productFlavors)

It works fine when I select the Build Variant which has the applicationId set to com.my.app.package.name (the package name used when generating the google-services.json). But, my other flavors have different applicationIds.

I followed the offical devguide to set it up.

Error I get when any another build variant is selected in Build Variants Tab (which has a different applicationId (package name) is as follows:

Error:Execution failed for task ':app:processAllcategoriesDebugfreeGoogleServices'.

No matching client found for package name 'com.my.app.package.name.debug'

Explanation of Error Message:

In the task name in the error message above Debugfree is my custom buildType and Allcategories is one of my productFlavors.

I understand the error and know the package name is different from what i used when generating the json, but that is what I'm trying to figure a way around.

Problem:

Now, the google-services.json resides in the app folder and hence I am not being able to separate them out for each product flavor by dropping them in the flavor specific source set folder.

Questions:

My custom byildType for debugging suffixes .debug to the applicationId (package name). Is there a way I can make it work with the google-services.json which has my release applicationId (i.e. without the suffix .debug)
Is there a way to have multiple product flavors configured in the same google-services.json file without using separate files and tasks to copy the required file to app folder. I know it can be done using task as mentioned in this post. Is there a simpler way to just have one file or pick right file based on gradle configuration?
I see the package_name field in google-services.json has the package name com.my.app.package.name. Can I add multiple package names manually to work for all build variants? If yes, how to do that? Could not find any instructions in documentations.

I'm in similar situations. I need analytics support for one of prod-release flavour version only. I could able to [limit added dependency](https://stackoverflow.com/a/26249615/2624806) to prod-flavour but it still search for right package as part of son file. Any suggestion ! — CoDe, Dec 06 '17 at 07:37
I am also facing the same issue, Let me know if anyone finds the solution for this? — Deepanshu Sinha, Jul 14 '18 at 06:26
if your using firebase in app then add your new applicationId as sub app(add app) issue will fix — Mohd Qasim, Aug 21 '21 at 09:59

Muhammed Fasil · Answer 1 · 2018-09-13T07:07:15.513

675

Check your package name on your google-services.json it should be same with your local package name of your app

Example

"client_info": {
    "mobilesdk_app_id": "1:6596814400689:android:65d6f25f5006145",
    "android_client_info": {
      "package_name": "com.my.app.package.name"
    }

In this case my local package name is com.my.app.package.name so also i have changed my package name in google-services.json with my local package name

edited Sep 13 '18 at 07:07

answered Jul 05 '16 at 07:51

Muhammed Fasil

7,909
2
19
28

google-services.json is a file!!! within a app directory. Should find this file with the help of the Windows Explorer (for example). Should edit this file by the usual editor. – user_MGU Dec 02 '18 at 16:28
to find this go to Project view in Android Studio and search inside your app package – Gastón Saillén Jan 23 '19 at 22:32
58

No... we all know **google-services.json** is invalid in this issue... What we want is how to solve this issue in build variant situation!! – MJ Studio Apr 11 '19 at 07:56
1

If your activity is in a subpackage such as: com.example.aaron.myproject22.Activities.... you need to go into the google-services.json and change the client_info's package_name to com.example.aaron.myproject22 Also make sure you have apply plugin:'com.google.gms.google-services' at the bottom of build.grade (Module app) – WHOATEMYNOODLES Aug 22 '19 at 23:20
This fixed it for me. I'm using Firebase push notifications inside a library, and the google-services.json file that the Firebase Console generated used the app's package name instead of the library's package name. Thanks! – ScottyB Dec 01 '19 at 02:52

score 313 · Accepted Answer · edited Jan 25 '16 at 12:09

313

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

edited Jan 25 '16 at 12:09

ChrisF

134,786
31
255
325

answered Jan 25 '16 at 11:02

Viral Patel

32,418
18
82
110

35

Is there any way to disable analytics easily for a build type? I want to disable it for Debug? I thought it would be disabled if I don't add google-services file, but even if I disable, it still asks for google-services file. – Gokhan Arik Feb 09 '16 at 00:52
2

What would the difference each of the josn file added in each flavour?? – Android Feb 09 '16 at 08:44
2

Is there a possibility to use google services inside a module (that two apps share)... cause i can't even gradle-sync without having a google service file for that package... the embedding app should provide the json, but not the module. is this anyhow possible? – Georg Jan 30 '17 at 15:05
When I moved `google-service.json` to new folder named `staging` I got this error: ```File google-services.json is missing. The Google Services Plugin cannot function without it. ```. I need firebase only for staging, still - this doesn't solve the problem :( – shurrok Aug 27 '20 at 14:51

score 175 · Answer 3 · edited Jan 29 '19 at 01:22

175

No matching client found for package name 'com.tf' I am pretty sure that the "package_name" in google-services.json is not matching with your "applicationId" in app gradle.

app gradle:

defaultConfig {
        applicationId "com.tf" //replace with the package_name in google-services.json =
        minSdkVersion 23
        targetSdkVersion 26
        versionCode 7
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }

google-services.json

"client_info": {
        "mobilesdk_app_id": "1:23978655351:android:2b2fece6b961cc70",
        "android_client_info": {
          "package_name": "in.ac.geu.debug"
        }
      },

Solution: Just make sure the package_name and applicationId must be same.

edited Jan 29 '19 at 01:22

user5854648

1,029
2
11
36

answered Sep 25 '18 at 14:18

Kailash Karki

2,106
1
12
6

15

Author was asking about a workaround to this. They have different build types with different applicationId – Dmitry Guselnikov Feb 07 '19 at 07:46
2

you have given to most valid solution. Kudos man !! – Devansh sadhotra May 09 '19 at 07:28
3

The `application id` in app gradle nailed it – BlackPearl May 19 '20 at 07:09
2

This is the correct answer. Just make sure the package_name = applicationId. In my case, I was created a new project with a new name (A) and copy the old code from old project named (B). In project B the package_name is the name I chose on firebase console, but it is not matter, we do not need to match the name we have set on the SDK installation instruction. – Phil Nguyen Jan 28 '21 at 08:30

score 90 · Answer 4 · answered Dec 27 '16 at 10:58

90

I have found the solution:

We have to create two "apps" in the firebase project, and then we can download json file from any one app (I downloaded from the flavoured app). It will contain the data for both the apps. We can simply copy the json file to the app's root directory.

Source: https://firebase.googleblog.com/2016/08/organizing-your-firebase-enabled-android-app-builds.html

answered Dec 27 '16 at 10:58

Usman

2,331
2
21
29

13

This is the best answer as all the product flavours can be covered by one json file. No need to create other sourcesets. – Tash Pemhiwa Feb 19 '17 at 10:46
2

Please note, you have to create the apps inside the same project. Project Overview on the upper left corner has a settings icon. Press it and it will open to the General tab, scroll down and under Your Apps section there is a button Add App – galaxigirl Jun 18 '19 at 18:04
1

The biggest problem will happen when you forget to change your google-service.json and push it to prod. – Edhar Khimich Apr 29 '20 at 14:23

Ravi Vaniya · Answer 5 · 2020-12-05T04:31:14.703

82

Whenever you create or update package name Make sure your package name is exactly the same [Upper case and lower case matters]

Do below step.

1). Check applicationId in App level gradle file,

2). Check package_name in your google-services.json file,

3). Check package in your AndroidManifest file

and for full confirmation make sure that your working package directory name i.e.("com.example.app") is also the same.

EDIT [ Any one who is facing this issue in productFlavour scenario, go check out Droid Chris's Solution ]

edited Dec 05 '20 at 04:31

answered Jun 18 '18 at 09:40

Ravi Vaniya

1,562
1
17
28

3

Thanks Bro it worked for me .In app level gradle file my package was different .When I changed it worked for me – fazil Aug 16 '18 at 09:50
wel come @fazil – Ravi Vaniya Aug 16 '18 at 10:19
You don't have to change `package` in manifest (and all files in all packages), as `applicationId` will change app id. – CoolMind Feb 27 '19 at 14:35
This is not what the author was asking about – shurrok Aug 27 '20 at 14:40

score 78 · Answer 6 · answered Jan 21 '17 at 13:40

78

make sure your package name in "google-services.json" file is same with your apps's package name.

answered Jan 21 '17 at 13:40

cahit beyaz

4,829
1
30
25

5

common issue when forking a repo for a new project. – Zapnologica Feb 14 '17 at 06:17
1

yes if both package name are not same than it is not working – Priya Mar 21 '18 at 06:39

Droid Chris · Answer 7 · 2018-07-17T20:51:04.137

64

First off, add a suffix to the application package in Gradle:

yourFlavor {
   applicationIdSuffix "yourFlavor"
}

This will cause your package to be named

com.domain.yourapp.yourFlavor

Then go to Firebase under your current project and add another android app to it with this package name.

Then replace the existing google-services.json file with the new one you generate with the new app in it.

Then you will end up with something that has multiple "client_info" sections. So you should end up with something like this:

"client_info": {
    "mobilesdk_app_id": "YOUR APP INFO",
    "android_client_info": {
      "package_name": "com.domain.yourapp"
    }
  }

"client_info": {
    "mobilesdk_app_id": "YOUR APP INFO - will be different then other app info",
    "android_client_info": {
      "package_name": "com.domain.yourapp.yourFlavor"
    }
  }

edited Jul 17 '18 at 20:51

answered Jul 17 '18 at 20:45

Droid Chris

3,455
28
31

3

This is the right answer! You need both Apps (ids) in the google-services.json file. – Bojan Hrnkas Jul 01 '19 at 13:47
1

this is the way. +1, here's some [old discussion](https://github.com/googlesamples/google-services/issues/54#issuecomment-181807020) that relates to this issue – lasec0203 Sep 27 '19 at 07:57
2

Simple and straight forward. – Umair Jan 13 '20 at 17:42
6

This should be marked as correct answer regarding build variants – Zamrony P. Juhara Jul 16 '20 at 19:11
1

even tho I have answered to this question here [https://stackoverflow.com/a/50906585/4696610], but for the `productFlavour` scenario, this is the best solution, I will sure link your answer in mine to help future devs, thx +1 – Ravi Vaniya Oct 14 '20 at 04:31
1

Correct answer !! Worked ,Thanks – Annie Feb 23 '21 at 07:00
this did not work for me – Anna Harrison Nov 30 '21 at 16:27
@AnnaHarrison post your code and see what your issue is. It seems now that Firebase automatically does what I had posted here. – Droid Chris Dec 02 '21 at 17:49

devDeejay · Answer 8 · 2019-12-05T08:01:47.760

58

This error occurs when you have a Google Services Json file downloaded in your project whose Package name doesn't match with your Project's package name.

Recently renamed the project's package name?

It does update all the classes but not the Gradle File. So check if your package name is correct in your Gradle, and also maybe Manifest too.

edited Dec 05 '19 at 08:01

answered Apr 29 '19 at 05:35

devDeejay

5,494
2
27
38

score 46 · Answer 9 · edited Nov 10 '16 at 04:10

46

You need to place google-services.json into app/ dir. And for each build type, there should be accordant director in app/src folder.

For example, if you have release and debug:

app/google-services.json
app/src/debug/google-services.json

In all google-services.json files you should specify correct package_name according to build type.

For example, inside debug dir it should be like {com.myapp}.debug

edited Nov 10 '16 at 04:10

ישו אוהב אותך

28,609
11
78
96

answered Sep 03 '16 at 10:38

Bogdan Ustyak

5,639
2
21
16

8

Apparently you can even just duplicate the main set's element in the `"client"`'s array (add a comma between the elements) and change just the `"package_name"`'s value of the new element to include the `.debug` suffix. Then rebuild. It worked for me on AS 2.3.3. – et_l Jul 31 '17 at 14:20

score 31 · Answer 10 · answered Feb 27 '19 at 07:05

31

1.Verify Package name and Application ID should be same

2.Verify google-services.json package name which is available in app folder

answered Feb 27 '19 at 07:05

John Ruban Singh

1,284
14
19

I had to `Invalidate Caches / Restart...` as well to get this working. – Anthony Cannon Sep 14 '20 at 08:22

score 26 · Answer 11 · answered May 30 '16 at 17:21

26

check if client_id and package_name in the google-services.json has a correct value according to your package name.

You should add the mentioned file into the flavors directory with corresponding package name in the client_id and package_name field.

answered May 30 '16 at 17:21

Shayan Amani

5,787
1
39
40

Michal Zhradnk Nono3551 · Answer 12 · 2021-01-20T08:42:04.230

21

In my case I forgot google-services.json in app root directory which was for different flavour. It was used by default instead of using json stored in flavour's folder. This messed up plugin and since package names were not matching it failed.

Wisdom I taught, check for all google-services.json in your project structure when this problem occurs.

edited Jan 20 '21 at 08:42

answered Dec 08 '20 at 14:25

Michal Zhradnk Nono3551

1,694
18
25

score 20 · Answer 13 · answered Dec 21 '16 at 05:02

20

Make sure you rename ApplicationId in gradle file after rename your package

answered Dec 21 '16 at 05:02

Syed Arsalan Shah

614
6
17

2

Saved me. Thanks. – VipulKumar Jul 07 '17 at 07:40
glad it helped someone – Syed Arsalan Shah Sep 12 '17 at 11:20
Solved my problem too! – Kanagalingam Apr 29 '20 at 06:34

score 20 · Answer 14 · answered Jan 18 '21 at 16:48

If anyone change their existing package name then sometimes it makes problem like that, so you should change local package name, build.gradle file package name and if your project have any google-services.json file then simply you need to change your JSON file package name too.

Old File look like that

"client": [
{
  "client_info": {
    "mobilesdk_app_id": "1:517104510151:android:8b7ed3989db24a6f928ae2",
    "android_client_info": {
      "package_name": "com.techsajib.oldapp"
    }
  },

New File look like that

"client": [
{
  "client_info": {
    "mobilesdk_app_id": "1:517104510151:android:8b7ed3989db24a6f928ae2",
    "android_client_info": {
      "package_name": "com.techsajib.newapp"
    }
  },

Note: sometimes JSON file have several package name so change all of them

score 17 · Answer 15 · edited Mar 03 '17 at 04:09

17

Open your Google-services.json file and look for this section in the file:

"client": [
{
  "client_info": {
    "mobilesdk_app_id": "1:857242555489:android:46d8562d82407b11",
    "android_client_info": {
      "package_name": "com.example.duke_davis.project"
    }
  }

check whether the package is the same as your package name. Mine was different, so I changed it and it worked.

edited Mar 03 '17 at 04:09

Pang

9,564
146
81
122

answered Mar 03 '17 at 04:04

DAVIS BENNY 15MIS0426

228
2
5

Worked :) Thanks – Shujat Munawar Apr 05 '18 at 17:06

score 11 · Answer 16 · answered Aug 01 '17 at 18:16

Im coming from react native but I think that this applies to this question as well. To specify.

Within the file android/app/build.gradle search for applicationId (within android, defaultConfig)

and ensure that that value is the same this

client[0]client_info.android_client_info.package_name

as the value within google-services.json.

score 10 · Answer 17 · answered May 01 '18 at 08:17

10

You also need to change package name in google-services.json

answered May 01 '18 at 08:17

Syed Hussain Mehdi

1,168
1
11
15

score 8 · Answer 18 · answered Mar 12 '17 at 04:09

8

If your package name on Google-services.json file is okay, Go to gradle.properties file. Then change your APPLICATION_ID="com.yourpackage.name"

answered Mar 12 '17 at 04:09

Dulal Kisku

81
1
2

score 8 · Answer 19 · answered Jan 11 '23 at 12:46

Only two easy step to change package name:

Open "build.gradle" file
Then add your new package name in "applicationId", now then click on "sync now" the project.

Note: If your "google-services.json" file is added in project then change your name package name there inside "client_info"

package name inside "google-services.json"

That's all. No need to change package name anywhere else.

score 6 · Answer 20 · answered Mar 17 '18 at 12:07

I think you have added firebase json file "google-services".json with the new file. Make sure to create a new file check the link on how to create json file from firebase and it should match with your package name

Second thing is that if you are changing the package name use the option " replace in path" when you right click under files when you select project from the drop down. You have to search for package name in the whole project and replace it !

Hope this helps !

score 4 · Answer 21 · answered Apr 04 '17 at 15:50

4

if none of it worked for one of you guys, my problem was with a package name that didn't start with a 'com'. changed it, now it works.

hope that helps

answered Apr 04 '17 at 15:50

eiran

1,378
15
16

score 3 · Answer 22 · answered Oct 09 '17 at 11:42

3

I solved the same problem by re-syncing the file google-services.json.

Tools > Firebase > Connect to Firebase > Sync

answered Oct 09 '17 at 11:42

Nabin Bhandari

15,949
6
45
59

where did you do that? what does it replace exactly? Screenshot? – Nasenbaer Oct 25 '19 at 14:31
You can do that in Android Studio (Firebase plugin must be enabled). It updates the file `google-services.json`. – Nabin Bhandari Oct 26 '19 at 06:31

score 3 · Answer 23 · answered Nov 13 '17 at 14:44

go your project directory and create folders on app/src path that named your product flavors (like Alpha, Beta, Store or what ever your flavor's name is). then copy your google-services.json file to each folder. don't forget to change "package_name" field on your each product flavor's google-services.json file that you subfoldered.

score 3 · Answer 24 · answered Mar 17 '18 at 08:33

Go to google-services.json file and in client part check the package name and compare it with App package name if they are different then change the client package name according to your app package name it worked for me best of luck..

google-services.json file-> "package_name": "com.example.application.tracker"

App package name->package "com.example.application.tracker";

score 3 · Answer 25 · edited Jul 17 '18 at 09:12

3

android {
    compileSdkVersion 27
    defaultConfig {
        applicationId "com.package.name"
        minSdkVersion 19
        targetSdkVersion 27
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }

make sure Gradle.app's applicationId is same your package name. my problem was this and I solved this way

edited Jul 17 '18 at 09:12

Desdenova

5,326
8
37
45

answered Jul 02 '18 at 13:48

Bayar Şahintekin

447
5
12

score 2 · Answer 26 · answered Nov 13 '16 at 10:48

I solved it by making two sourcesets , one free and one paid. Both of these folders will contain required java code and resource files, which will be edited to the requirements of the particular flavor. For example, You would like to remove AdMob Code in the Paid both from Java Classes and Layout Files.

score 2 · Answer 27 · answered Dec 01 '17 at 12:01

I solved the same problem here is simple solution: when you create firebase connection follow these guidelines:

Add your application name in firebase
Add your application pakage name (write same pakage name ,you are using in app)
when firebase make google-services.json file just download it and paste it in your app folder
Sync your project Problem is solved :)

Thank you

score 2 · Answer 28 · answered Jun 13 '18 at 04:37

I also get this issue when i change package name of my application.

In your android studio project find "google-services.json" file. Open it. and check whether package name of your application is same as written in this file.

The package name of your application and package name written in "google-services.json" file must be same.

score 2 · Answer 29 · answered May 21 '19 at 09:37

2

you can do that for sovling this problem.

answered May 21 '19 at 09:37

指尖上的Android

4,798
2
9
2

5

This will mask the problem instead of solving it. See other answers for a solution. – Vadim Kotov Aug 13 '19 at 12:57
Please use code instead of a screenshot, your answer is good in my case because I only want to create a "mockup" of an application clone. – user2078023 Aug 26 '19 at 10:54
4

Sharing the code rather than screenshot would have been more useful. – vipin agrahari Jul 27 '20 at 16:36

score 1 · Answer 30 · answered Jan 24 '18 at 20:16

This means your google-services.json file either does not belong to your application(Did you download the google-services.json for another app?)...so to solve this do the following:

1:Sign in to Firebase and open your project. 2:Click the Settings icon and select Project settings. 3:In the Your apps card, select the package name of the app you need a config file for from the list. 4:Click google-services.json. After the download completes,add the new google-services.json to your project root folder,replacing the existing one..or just delete the old one. Its very normal to download the google-services.json for your first project and then assume or forget that this specific google-services.json is tailored for your current project alone,because not any other because all projects have a unique package name.

score 1 · Answer 31 · answered Jan 20 '19 at 13:33

1

Check for applicationIdSuffix in your app's build.gradle file. See if it is concatenating any text to your applicationId. If so, remove it.

answered Jan 20 '19 at 13:33

Syed Arsalan Kazmi

949
1
11
17

score 1 · Answer 32 · answered May 20 '22 at 15:45

1

If your applicationId is different between your buildTypes, you can add those particular artifacts to specific dependency flavor like releaseImplementation for example.

answered May 20 '22 at 15:45

Mohsents

691
11
9

score 1 · Answer 33 · answered Sep 20 '22 at 08:45

1

I forgot to add SHA certificate fingerprint in Firebase. I just re-imported google-services.json and it worked

answered Sep 20 '22 at 08:45

Peter

340
4
13

score -1 · Answer 34 · answered May 16 '18 at 12:04

-1

Just simple. Sign-out from Android Studio, close it completely. Reopen Android studio and then again Sign-In to Android Studio.

Then try to connect to firebase from the Android studio IDE. This procedure worked for me.

answered May 16 '18 at 12:04

Prakash Palanisamy

94
4

this is not working if google-services.json exists. we must delete google-services.json if it exists. – Dika May 23 '18 at 22:19
this will work once after you change the package name in the json file as well and before save that, you need to close the android studio and then save the json file and restart the studio. – Anish Kumar May 28 '18 at 11:13

score -3 · Answer 35 · answered Jul 16 '18 at 20:27

-3

It is simple to solve this: just make sure the package name in your app/build.gradle file is this same package name as the ones in your App Manifest file. and ensure the package name is correct. That should solve this

answered Jul 16 '18 at 20:27

James Idowu

223
3
4

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

35 Answers35

Linked

Related