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!
Related
So I recently uploaded my Android application to the Google Play store and it published successfully. This is the application here: https://play.google.com/store/apps/details?id=com.kyoudai.sudioku
The problem is, when anyone installs thiis application, they cannot open it i.e. the open option does not appear on the playstore, only the uninstall option. This application also cannot be found in the application drawer on any device, or in the list of installed applications. I've tried editing my manifest and included everything necessary but I have no idea why this happens. I generally believe if there was an issue with my code that should not be possible for an android application, the play store would flag it. When I was developing this, it showed up on the emulator application drawer so I assumed it was fine. I'm not sure why this happens, and I'm not even sure where to contact google regarding this. Any help is appreciated.
Given people are gonna jump on the manifest configuration, here it is: https://github.com/BerserkerLan/Sudoku-Android/blob/master/app/src/main/AndroidManifest.xml
make sure that your build is signed APK/Bundle
So basically, the issue was that I just had too many category elements in my intent-filter and thus somehow that was interfering with the MAIN, VIEW and LAUNCHER elements, so now I only have those three in it and it launches fine.
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.
I have created a application and released it with out signing it. also i have updated my application few times after the first release.
After few months , now would like to give a another update. if i install my application in mobile , its not getting install, its installed only after i uninstalled the existing application from the mobile.
in console its showing , "Change in application signature"
I know i made a mistake by not signing the application with private key at first time. But please any one tell me How my default debug key has changed now.. so that i can roll back.
is there any way to solve the issue? or i should ask my users to uninstall the app.
Thanks.
Several things can cause the debug key to change, such as reinstalling the SDK or building the APK from a different system. The only way to upload a new version of your app now is to delete the old one and upload the new one, e.g. adb uninstall com.example.appPackageName first.
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.
I have an android app on the market for some time (7 month) that was labeled as "Beta" in the title.
Yesterday I published a new version and thought it's time to leave the beta state. Therefore I switched the app-title in the market backend and removed the "beta" tag.
The problem is: now, the users don't receive any update notification! If you search for the app in the market, the red update label is shown correctly. But in the "my apps" section, the update label and the notification is never shown. The user doesn't see that there's an update.
It didn't work on my two phones (both 2.2, I cleared the market cache) and it seems like, nearly all users continue to use the old version.
So, is this a known problem? Or was it just a temporary problem on my phone? Can anybody confirm this behaviour?
And, what can I do now? Switching the title back doesn't seem to help.
Thanks a lot
Marcus
Are you sure you didn't change your package name? (although the Market console should have thrown an error if you tried to upload and upgrade with a different pname)
Just change your label and version...