AppCenter "App not installed as package conflicts with an existing package"

Question

I have seen a similar stack overflow question but none that was for AppCenter. You can see that I have completely different version number and version codes for each release. I downloaded release 332, then tried download release 333 and this error message happens. How do I fix this? Why does this not happen on iOS appcenters?

score 0 · Answer 1 · edited Nov 21 '22 at 08:51

0

Your old app has the same package name that the new app has. Whatever the version number maybe, you cannot install another app with same package name. Assuming, the old package name is com.demoapp New app will not accept its package name as the same as above. It should be something like com.demoappCopy.

edited Nov 21 '22 at 08:51

Mark Rotteveel

100,966
191
140
197

answered Sep 01 '22 at 13:51

Robert S

626
6
13

So everytime I want to download a new build on AppCenter I have to change the package name? It won't update the existing one? – Android Dev Sep 01 '22 at 15:09

score 0 · Answer 2 · answered Sep 01 '22 at 15:06

0

Are all of your builds signed with the same release signing config? If the builds are not signed with the same key then you will get this error because it treats them as two different applications instead of an upgrade to the existing application.

answered Sep 01 '22 at 15:06

rjschnorenberg

661
1
9
30

I don't think they're signed at all ... – Android Dev Sep 01 '22 at 15:09
This is probably the issue, App Center has a nice guide to build signing which links through to Google's guide as well: https://learn.microsoft.com/en-us/appcenter/build/android/code-signing – rjschnorenberg Sep 01 '22 at 15:15

score 0 · Answer 3 · answered Mar 20 '23 at 07:03

0

You may keep its data! Install the same app again and then remove it without checking keep data!

answered Mar 20 '23 at 07:03

Mohsen Abasi

2,050
28
30

AppCenter "App not installed as package conflicts with an existing package"

3 Answers3