Android Question app not installed as package conflicts with an existing package

Is this the exact error message?

My guess is that there is an existing app with the same package name, signed with a different key.

app not installed as package conflicts with an existing package

Click to expand...

I got this message yesterday - unfortunately on an app that I had just uploaded to the PlayStore. It was an old app, although last updated only six months ago. My first thoughts were that it might be a signature problem (although I am not sure why) or maybe connected with switching jdk in the last B4A update (although that does not make sense either). Basically I panicked. But I have not resolved the problem.

An update to my previous post :

a) The update from the Playstore installed on an old phone running Android 8, but not on a tablet running Android 11.

b) This post might be describing a related problem.

Erel said:

Is this the exact error message?

My guess is that there is an existing app with the same package name, signed with a different key.

Click to expand...

yes that is the exact cut and paste error. I would think that copying all the files and I do mean all the files, would keep everything the same so I would be able to switch dev computers easy. I have a different name from the config builder and private key. so stumped on this one.

I am thinking that the signing key may not be transferring this way or maybe some other settings. I do my work in different locations, maybe I need to know how to make sure the key and settings for each project are transferred. In my mind I should not need to do separate keys and all for different computers I develop on. I can see so much going wrong that way.

Nothing special about the signing key. The key is a separate file that you set with Tools - Private Sign Key. You do need to copy it yourself.

Just an update from me . . .

Yes, this problem has all the hallmarks of a signature error, but all of my work for the last few years has been on the same PC and in the same file environment.

Last night I released a second app to see if the problem repeats. I had taken this app out of production last year so it was something that I could release quickly with no risk. It comes from the same PC and file system so is a good rerun of the previous release path. The app will be a few days in review before I can see the results.

Meanwhile, no change on my earlier release. I have put a note in the release notes advising users to uninstall their previous version, but I don't expect many will see it. Otherwise the update seems to just sit in the Playstore queue in a "Pending..." state. I have left one of my devices in that situation to see if that ever changes.

Erel said:

Nothing special about the signing key. The key is a separate file that you set with Tools - Private Sign Key. You do need to copy it yourself

Click to expand...

I am pretty sure I did copy everything. I mean everything in the entire path which should include the signing key but it still caused the issue. I verified the file is in the folder path with everything else. I copied outside of b4a. I tried using the create zip option and just copying a ton of files of the entire path. both ended with same issue.

Maybe I am missing something? maybe a hidden file is not being found?

No hidden files.

Otherwise the update seems to just sit in the Playstore queue in a "Pending..." state. I have left one of my devices in that situation to see if that ever changes.

Click to expand...

I don't use automatic mode and I check updates every evening. Last night the update installed - a great surprise - so possibly not a problem with the signature after all. As a comment, I have noticed that some mainstream apps (Outlook, for example) have recently been reluctant to install and have not installed at the first session.

My seconf trial app was also released yesterday - sooner than I expected. It was again a little slow to install - it is a very small app - but it did install successfully.

Erel said:

No hidden files.

Click to expand...

well, in lieu of a solid direction on this issue I guess I will just have to use a laptop for all development. However I do have to ask if there is any chance that this issue would impact installation of multiple programs developed. Keeping in mind each will have its own key and unique name in the config builder. Or am I doing this in the wrong place? is the config builder global or only applies to the opened project?

The answer to the question in the first post:

- The IDE doesn't store the key in any special place. The IDE doesn't store the key at all.
- The key is set with Tools - Private Sign Key.

There is no problem with changing computers. You do need to move the signing key as well.

For any other question, please start a new thread.