I have uninstalled my app (debug version) with the options on my phone. But if I reinstall it with another version (signed) I get an error message that it already exists. But I do not see a symbol in the phone. I have to use adb uninstall. This happens on different devices.
Is this normal behavior or is there something wrong with my app?
If the signatures do not match, the old app must be uninstalled before another app with the same package name can be installed. The old application can be uninstalled from command line (adb uninstall) or just using the normal Android UI (go the all applications view, long tap the application icon there and drag it into trashbox that should appear at the top).
It is really very strange and wrong if you do not have your application icon at all. Even if you do not supply one, the default icon (a green Android) should be used together with your application name. But maybe you are talking about the main desktop where the icon may not be installed by default. You need to go to application list instead. For 4.1.0, the application list is opened with the button having six white dots in two rows, all surrounded by the circle, at the bottom centre.
If you try to install a signed app with the same package name as the unsigned version, it will return an error saying that it cannot be done. What you have to do is to check that the app really is uninstalled on your device before installing the new, signed version.
problem is that i was using 2 packages
Related
I'm using Android Studio 3.5 and can't install an app from it.
My app is already on play store and I'm upgrading the app.
It keeps saying there's a same application.
Okay, so I deleted it, but it keeps saying that.
First a pop-up window saying that I will have to uninstall the existing application. I know why it happens. I develop on my laptop and my desktop at the same time so it happens all the time. And this app doesn't have my data so I've clicked okay and proceeded and there was no problem. But,
The device already has an application with the same package but a different signature.
Retry
The application could not be installed: INSTALL_FAILED_UPDATE_INCOMPATIBLE
in new. And even I don't have the app, why does it say like that???
And installation is way too quick on play store.
I think the app isn't deleted properly.
So basically, I have no app on the phone, the data, cache, apk, anything, but it keeps saying there is a same app with a different signature.
I have
Deleted the existing app and it still didn't work
Re-downloaded the app and ran and didn't work
And as expected, it says if I wanna delete it, pushed OK. And the app is
automatically deleted.
also adb uninstall com.~~.~~ not working
Set debuggable true, still not working
Ran on a friend's phone which already has the exact same app from the store
and it works.
Tried to disable instant run but android studio 3.5 does not have that anymore.
Rebooted my phone.
Deleted caches of android studio and restarted it, as many as I could.
adb shell pm list packages -f : the package does not exist.
done adb uninstall com.~~.~~ and got Success code, but still not working
There's nothing wrong with codes.
Build works perfect. It runs perfectly on my friend's phone.
I expect for the app to run perfectly but,
the studio says
The device already has an application with the same package but a different signature.
Retry
The application could not be installed: INSTALL_FAILED_UPDATE_INCOMPATIBLE
Also, installation is too slow. It wasn't slow like this.
this happen when you have multiple spaces or user in single phone, it will be helpful if you can tell about your phone model
After i click my app, my app can't start.
There is the log print by system, i note there is a line say package not found in list.
My phone is XiaoMi and this problem is less show in nexus5.
Dose any one know what the problem is?
You might have installed the app in the device sometime before with a different build/signature. since the app has the same package name (i.e com.example.*), the android OS is not able to install the newer version with different signature. Please delete the older version and try running it again. This should help!
So I made an app for android, debugged it and it was a really great experience overall. However the app has a problem now. I went to publish the app and it told me I couldn't publish the app under the package name com.exmaple.ect, so I went to change it, no problem there. However foolishly when I changed the application package I did it manually and forgot to change the manifest so when it published, the app would crash. So I went back and updated it and I re-saved and went to tools to "export signed application package".
I then proceeded to update but realized I made a mistake and named the package wrong, so I went to fix it. It then published fine. However upon publishing the icon got taken out of the app so I had to (for a fourth time, sorry I'm still a beginner) update.
So now I update the app with Icon.. I updated the app after "export signed application package" again and when it went to upload the app onto my test phone, there are now 4 app icons on both my Android smartphone and when I click, one of them doesn't work as before, the other one without an icon, the other with an icon that works. However when I click the one that works it then says "Complete using action" with the four different package names. How can I get it so only the one that works is the app downloaded onto users phones?
As usual, I'm very appreciative to all responses. Each prior version is still showing. Could it be that I'm not suppose to "export signed application package" each time I tried updating?
If each app has a different package name, it is considered a completely different app. The package name is what identifies your application from all of the others, and is what makes each individual application uniques.
For example: if you were to release an app with whatever package name, this package name must stay the same for the lifetime of the app. If the package name were to change, it is released as a completely different app. Thus, your users will not be informed of an update, as it technically didn't receive an update.
Hope this helps, happy coding!
I am developing 2 android applications, which are clients for my server. I cannot install both applications on my android phone. I install the first app to phone, everything is ok. Then when I try to install the second app on the phone, I get the message that the application will replace another application (the first one), and then I get following error:
Application not installed: an existing package by the same name with a conflicting signature is already installed.
I mention that I have created one separate keystore file for every application, export them as in the android official signing application guide, then zipaligned them.
So the OS thinks that it is a single application? But in fact there are 2 different apps.
What am I doing wrong?
I think you are using the same package, which is not allowed for two different apps.
But for anyone who have the same error for installing another version on top of previously installed app:
I wanted to test released version of my app when the problem occured. I've had the app previously installed using eclipse, and than I wanted to install the same app but with released signature. I have even uninstalled the app using apps gallery, but the problem persisted.
The solution for me was to unistall the app using Settings->Apps->"the app"->top right corner menu->Uninstall for all users
I had the same error message, but these answers did not help. On a 4.3 nexus 7, I was using a user who was NOT the owner. I had uninstalled the older version but I kept getting the same message.
Solution: I had to login as the owner and go to the settings->apps... Scroll down to the end of the list where my old version was listed with a mark 'not installed'. Select it and press the 'settings' button in the top right corner and finally 'uninstall for all users'
Not sure what happens when you use the same signing key, because in all honesty, I never really tried it.
That being said, as Anand Tiwari, in his comment, has already simplified the answer, you cannot install two different applications with the same package name on one device. They, logically speaking, may be different to you, but for the OS, they are in fact, the same.
The problem also manifests itself when you try to upload the applications to the Android Market (Google Play). Google Play will simply not accept the second application. There is a short and simple explanation by Warren Faith here: https://stackoverflow.com/a/5788664/450534
As an example of how similar applications with a few changes are published to the Google Play store:
The free version of FriendCaster is: https://play.google.com/store/apps/details?id=uk.co.senab.blueNotifyFree
The paid version if the same app is: https://play.google.com/store/apps/details?id=uk.co.senab.blueNotify
Notice the ending of the package names. In this case, you will be able to install both the apps simultaneously on one device.
I think your problem is that both your files have the same package name. You can name both apps with similar packages, but they can't be identical. In fact, using the same package base can be used to communicate between applications ie. App1: com.mypkg.app1 and App2: com.mypkg.app2. However, they both can't be called com.mypkg.app - the package name is how Android identifies apps, and can't be identical.
You should be able to sign as many different apps (assuming their package is different) with the same key.
Make sure not to lose your signing certificate, if you lose it, you will not be able to upload a new app with the same package name. If you lose your signing certificate, you will be in big trouble.
Good luck.
We develop an app for android. When we installed the app for the first time, the app works. When we do some changes on the source, we can't install the app again without deleting it from the phone.
Is there any known workaround? When we install the app the second time, the phone shows "App not installed".
Any ideas?
It sounds like you are having some kind of namespace collision. I get this sometimes when I duplicate a project. You need to preserve a unique mapping of APK signing key to package name. See the Things That Cannot Change blog post for more details about preventing package confusion.