Permission name C2D_MESSAGE is not unique appears in both C2D_MESSAGE

Question

I'm getting this error:

Permission name C2D_MESSAGE is not unique (appears in both my.packagename.permission.C2D_MESSAGE and my.packagename.acc.permission.C2D_MESSAGE) (Previous permission here)

In my Android manifest:

<permission
    android:name="my.packagename.permission.C2D_MESSAGE"
    android:protectionLevel="signature" />
<uses-permission android:name="my.packagename.permission.C2D_MESSAGE" />

The problem started after adding the applicationIdSuffix to a flavor in build.gradle (which at first glance seemed to have nothing to do with it).

Build.gradle:

flavorDimensions "type"
productFlavors {
    acceptance {
        dimension="type"
        applicationIdSuffix ".acc"
        versionNameSuffix "-acc"
    }
    production {
        dimension="type"
        applicationIdSuffix ""
        versionNameSuffix ""
    }
}

Application.java:

    if (BuildConfig.DEBUG) {
        GoogleAnalytics.getInstance(context).setDryRun(true);
    } else {
        setupGoogleAnalytics();
    }

I've created a copy of google-services.json.

I've added google-services.json to:

 app\src\acceptance\google-services.json (fake numbers)

 app\src\production\google-services.json

I've made different bogus values for the keys in the acceptance. I don't want Google Analytics in the acceptance version. So I prefer to not create a separate google-services.json. Is this possible?

Simply removing the permission in manifest doesn't work for API<23.

Have you checked the suggested answers in [this SO post](https://stackoverflow.com/questions/34990479/no-matching-client-found-for-package-name-google-analytics-multiple-productf)? — MαπμQμαπkγVπ.0, Apr 13 '18 at 10:48

score 2 · Answer 1 · answered Apr 19 '18 at 13:41

2

This looks like you're using the latest Firebase Cloud Messaging (FCM) SDK but retaining the old GCM permissions. The FCM SDK automatically injects the necessary permissions into your manifest at build time.

Remove the C2D_MESSAGE permission from your manifest per the migration guide here: https://developers.google.com/cloud-messaging/android/android-migrate-fcm

answered Apr 19 '18 at 13:41

Larry Schiefer

15,687
2
27
33

The documentation is not correct. I've tested this on API 18 and it failed. – Jim Clermonts Apr 19 '18 at 13:42
What failure(s) did you see exactly on API 18? – Larry Schiefer Apr 19 '18 at 13:45

score 2 · Answer 2 · answered Apr 19 '18 at 13:45

add a new androidmanifest into:

app\src\acceptance\androidmanifest.xml

and add the "acc" prefix:

<uses-permission android:name="com.google.android.c2dm.permission.RECEIVE" />

<!--this needs to be in there for API 23 and lower-->
<permission
    android:name="my.packagename.acc.permission.C2D_MESSAGE"
    android:protectionLevel="signature" />
<uses-permission android:name="my.packagename.acc.permission.C2D_MESSAGE" />

score 1 · Answer 3 · answered Apr 25 '18 at 04:22

This problem often occurs when you try to install debug and release version of your app on the same device.

In order to fix this bug, you try uninstalling and reinstalling the app.

About source code in file AndroidManifest.xml:

<permission
    android:name="my.packagename.permission.C2D_MESSAGE"
    android:protectionLevel="signature" />
<uses-permission android:name="my.packagename.permission.C2D_MESSAGE" />

I think your permission is OK.

Permission name C2D_MESSAGE is not unique appears in both C2D_MESSAGE

3 Answers3