I want to ask a little issue which I found out why testing my application. When I update my application from Android Market after I upload new apk, everything is working fine without any errors. But when I try to install older apk manually, not from market and after that install newer version of it again not from market, there are some errors which I don't get if I update my app from market.
Any ideas if it's normal, because as I know Android market app takes care of installing the updates and etc.
it's normal if in your phone have a debug version ,
you must unistall old version on your phone, so after you can install the apk ( market version) manually .
for market update , you can update it only if your app is gratis.
Related
I was installed old version(version 1) of my application from google play store in my phones. Now I would like to update this app to new version(version 2), so, I generated new apk file by using android studio and I upload this generated apk to google drive. Then download and install from my several devices(Android 5.1.1, and Android 4.2.2).
In android 4.2.2, I can install the downloaded apk and my application was upgraded to version 2 successfully.
In Android 5.1.1, I can click on install button, after that show the "App not installed" error message and the application was not upgraded to new version(version 2).
Could you please give me some advice?
Please see the attachment picture of android 5.1.1 device.
I think it is bug. It happened to me once while upgrading to a new version. The problem occurs when there are 2 users in Android OS(i.e. Settings>Users. Probably in your case, guest user must be present). So when app was previously installed, it must be installed for both primary and guest user. So when Android OS tries to uninstall the app to upgrade, it only uninstalls app for primary user and not for guest user. So the app is still present in the OS but not for primary user preventing installation of the new app. At least this is what I think it is.(I am using a Moto G)
But I have never encountered this bug when upgrading from playstore. It only happened when trying to upgrade app by installing apk from external source. I hope it helps...
When you upgrade your application and build for release, make sure that you sign your application with the same keystore you used to sign your previous application version.
When you use new keystore to sign your new application version and attempts to install it into the device with your application(old version) already installed, android will halt the installation and you can tell exactly why it does not install by looking at the logcat.
I have developed an android application and installed apk in Blackberry and android devices.
The first time installation works fine.
When i try to update for next release i changed 'android:versionCode="1" android:versionName="1.0.0.0"' to 'android:versionCode="1" android:versionName="1.0.0.1"' in android manifest file.
Its working fine in android devices, but in blackberry the update is not working getting "Installed application is lastest".
Note: The application is not released from playstore.
Increment the version code also. I'm actually surprised that it worked in Android. Google Play Store won't let you upload an updated app unless the version code is "greater".
I have my application in Google Play, I've downloaded and installed it on my phone.
I'm also currently working on update of this application, and whenever I want to install my .apk file on my phone it shows me, that I can't do it, because the app is already here.
Where in Eclipse can I set some settings, which will allow me to install my updated app without installing original one?
EDIT
I want to have two versions on my device at the same time.
One simple solution is to change the package name, since that's how the OS identifies the .apk. Indeed, the package is unique to the Market: how does an android phone(or market) recognize an app
You can not install and run the app from eclipse because the app installed on the device (the one from play store) is signed with a different key.
When you export your app you sign the apk with a specific key and when u run it from eclipse you sign it with a different key - the debugkey.
If you HAVE to install another version on the device without uninstalling the old one from the device (the one you got from the play store) you should:
1.export your app and sign it with the same key you signed the app you uploaded to the play store.
2.upload the exported apk to the device.
3.install it.
EDIT:
If you want to versions on the same device you should change the app package name.
i'm new in android developing. (and in developing after all)
Here is my problem: If i install my android application onto my mobile device or AVD, i want it to check the current app version number and if it's lower than the one i want to install currently then install it, and if it is higher , then alert the users that they already use the latest version.
Because now when i install the .apk file, it just installs the app again and nothing happens.
Is it possible to develop this?
Best regards,
weeyas
The install process is managed at the system level, so your application has no control over it. As per the versioning guide, the Android system will only allow you to install updates from the same or newer version codes (i.e., version 1 can be replaced by version 2, but version 2 can never be overridden by version 1 unless you do a complete uninstall/reinstall). This applies to both Google Play updates and sideloading APKs yourself.
I don't know if it is possible if you try to install application from .APK file. However, you will not be able to publish the newest apk to Google Play if it has the same or lower version number than the current one.
I have a new version of my app on the market and an old one installed on tablet. I expect to see download/install option when I navigate to the application page on the market but instead I see "open" button as if the market version were already installed on the device. versionCode is incremented in market's version.
What could be a reason for this?
The version of your app installed using adb is probably not signed, or if it is the signature doesn't match the one on the app in the market. First need to uninstall the version that was installed using adb then the market version should install without a problem.