Add two custom APK same Identifier

Solved
Klevebrand
Here to help

Add two custom APK same Identifier

Hello.

I´m trying to add two Chrome APK.

One for API 21-23 and one for 24+.

 

But the identifier is the same on both "com.android.chrome"

Error message  "Identifier is already being used. You are most likely trying to add a duplicate app."

 

Is there an easy solution for this?

1 Accepted Solution
MattMorg
Meraki Employee
Meraki Employee

Currently the SM > Apps page on each network needs unique app identifiers. You could create a new SM network within the same Organization and then add the same app identifier over there, though. That would allow you to move devices between networks (without unenrolling) and allow you to test two different .apks of com.android.chrome

View solution in original post

5 Replies 5
MattMorg
Meraki Employee
Meraki Employee

Currently the SM > Apps page on each network needs unique app identifiers. You could create a new SM network within the same Organization and then add the same app identifier over there, though. That would allow you to move devices between networks (without unenrolling) and allow you to test two different .apks of com.android.chrome

Dustindepp
Just browsing


@Klevebrand wrote:

Hello.

I´m trying to add two Chrome APK.

One for API 21-23 and one for 24+.

 

But the identifier is the same on both "com.android.chrome"

Error message  "Identifier is already being used. You are most likely trying to add a duplicate app."

 

Is there an easy solution for this?


Change the package identifier: To resolve the conflict, you can modify the package identifier that is also known as the application ID of one of the Chrome APK files. By changing the identifier, you ensure that they are recognized as separate apps. For example, you can add a suffix like ".api21" or ".api24" to the package identifier of one of the APK files, making them unique.

Johnandrew
New here

Use different app flavors or build variants: If you're building the Chrome APKs yourself, you can utilize build flavors or variants to create separate APKs with different package names. This approach allows you to maintain separate codebases for different API levels while still having different package names for each version

Nathanisaac
New here

Yes, there is an easy solution for this. You can use different package names for the two Chrome APKs. The package name is a unique identifier for an Android app. It is used to identify the app in the Android system and in the Google Play Store.

Mattquil
Just browsing

There is no easy solution to adding two Chrome APKs with the same identifier. The identifier is a unique string that identifies an app to the Android system. Each app must have a unique identifier, and the system will not allow you to install two apps with the same identifier.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels