I have created with the use of android studio a small project and then I generated the signed apk. Then I tried to install it in three phones and in the first one (which has android 8) the app was installed successfully but in the second one (which has android 4.2) and third one (which has android 5) I got the "app not installed" error. This is my second app (project) and my first one has been installed successfully in all these three phones. The minimum SDK version of the app is Android 4.0.3 (API level 15), so that's not causing the problem. Can anyone guess where the problem is?
Sign the apk with both v1 and v2 signatures. this is the most likely culprit given your scenario. apk will not get installed on devices with less than marshmallow if you only sign with v2
Well you can try following:
Change install location of app on the phones it's creating problem.
Try resetting app preferences
Clear Data and Cache of Package Installer
Allow Apps from Unknown Sources (Go to Settings → Security → Unknown Sources. Enable Unknown Sources. And then try installing App)
Try Deleting .android_secure/smdl2tmpl.asec file from your SD Card if using SD card
Resign the app.
Try changing app codes by using some apk editor app
Related
I have an Android app that would not install on a Samsung S6 running Android 7. It would not install both from the Play Store and directly from Android Studio deployment.
I checked logcat and it stated that I have a package/class listed in my manifest as Managers.MyApp. I indeed had a folder named Managers and so files in there used the same name for their package.
I renamed the folder plus all references to managers (lowercase m). I did a global search to make sure there were no remnants. The app was finally successfully deploying to the Android 7 Samsung S6.
I uploaded the app to Internal Testing in Play Console (where the Samsung device would previously also fail to install the app from, with the same error). This time it was able to install from internal testing, so surely all is well with the app.
However, when I released the app to production, the Samsung device is again unable to install the app, showing the same error as before: Malformed manifest, invalid class: Managers.MyApp.
I do not have any instances of Managers anymore with an uppercase m. I checked the manifest and it certainly has managers.MyApp.
Is there some caching going on with Play Console? Or are there extra steps I need to implement. MyApp is a class that extends Application.
I installed the app through android studio and its working fine, but when I create the apk and then I installed the apk, on some devices my app is crashing.
Can someone know how we can see the logs or errors in case when we installed through apk, in can't debug the app bcos its working that time.
here are few details,
build variant: debug,
my apk name: app-debug.apk,
and I am using 2 3rd party libs as an .aar files
If you have installed the apk also you can able to get the logs if you have connected your device with studio. For that you have set the No Filter in Android Monitor.
In the phones, your app is crashing, don't just install the app by apk there. May be some of your 3rd party dependency is not compatible with those versions or phones.
Debug your app in those phone with cable and check error logs. You will get to know the problem
I updated my app and tested it on my device. Everything works fine if I test the app via the run button in eclipse but if I export it into an apk and try to install the apk it fails.
There is no error code or anything else, it just says the app has not been installed.
Any idea why this happens? I only changed a few things in my app: I removed the basegameutils lib from my app and migrated to the new api without basegameutils. Thats it (except for some bugfixes but that can not be the cause).
I did already restart eclipse and cleaned all projects mutiple times.
The target sdk is 22 and I am using newest system images and so on for that api level (my divce is a stock nexus 6 with 5.1.1 running). I also updated my build tools to 23.0.1 from 22.0.1 and removed the 22 version. Is this the cause?
I also tried to upload the apk in the dev console and there were no erros.
Thank you for your help.
EDIT:
The logcat output says the signature does not match the previously installed version.
If i try to install the current live version via the play store there is also an error message saying i can not install this app because another user already installed an incompatible version on this device (but i dont have it installed and i dont have multiple users on the device).
If i got to the app menu in the settings my app is shown at the bottom of the list but there is a note saying the app is not installed for the users. If i click on it all buttons are unclickable (so i can not uninstall it).
What is happening?
For me, selecting Signature Version v1 and v2 both solved the problem
Your signature changed, so as you mentioned you must uninstall the previous version. You tried to uninstall from the device UI and that fails - so try it from the command-line:
adb uninstall your_package_name
Seen on Nexus devices, occasionally only command-line uninstalls work.
I found a solution but I still have no idea what caused the problem.
somewhere on my device my app was still installed even though it didnt show up in the app drawer and the play store told me the same. In the settings/apps menu my app was still present (as i mentioned in the edit of my original post) so i clicked on it. If you click on the menu button you can chose unisntall for all users which did the trick. now I can install my apk again.
I have no idea how this happened but there you go, i hope this helps.
EDIT:
I had the same problem as this guy had. the accepted answer over there is much nicer than my poorly foramtted text ;)
"You cannot install this app because another user has already installed an incompatible version on this device"
I was facing same problem And I solved it this way, For Current Updated Android Studio 2.3
Build > Generate Signed apk.
Create Keystore path.
Put Password, alias, key password.
Build type select accordingly(eg to release in playstore use release).
Signature Version select both V1 and V2 checkboxes.
Finsih.
Go to the apk from explorer and use it for your playstore or in devices as Signed and Certified apk file.
For me the solution was to disable Play Protect on device.
You can not run signed apk directly in your android device .
I you want to run your apk then follow below steps :
1) Go to your device settings
2) In setting you find applications
3) In application checked unknown sources
This will allow you to run your signed apk without downloading from play store.
or
try this link :
"You cannot install this app because another user has already installed an incompatible version on this device"
The problem is because you have a version of your testing app. So, you're not really upgrading the app! Those are two different apps. You must first uninstall previous version (testing) so you can install the release (signed) version of your app.
I encountered this problem today and tried a few suggestions here, and this is how I solved the issue: I cleared my phone's caches / junk files and also uninstalled the test versions of the app and their APKs, and then reinstalled the new APK. Try this first before getting worried. 🙂
I got the save Error just incase someone faces this. For me it was because i have multiple projects for the same app on the phone. you need to delete older versions of the app from your phone.
If you have two options (V1 (jar signature) and V2 (Full APK Signature)) before generation signed apk. you should use V1 jar signature now, because there is no backward compatibility and all android phones with version < 7 won't accept this signature. Backward compatibility will be added in some next N Developer Preview.
There are also explanations on this developer.android in this link :
https://developer.android.com/about/versions/nougat/android-7.0#apk_signature_v2
In my case it was the proguardFiles path in build.gradle that caused this problem
Currently PlayStore performs regular checks for apps and device for harmful behavior. Installing signed APK manually is treated like unusually behavior so is preventend.
So turn off play protect feature temporary and your install will work as charm!
step one - open play store and select play protect
step two - click play protection setting button
step three - disable
step four - close and install your APK manually
I've been building an application, and it works fine on all the ICS phones I've tried to install it on. However, when I try to install the apk on my friend's new Jelly Bean phone, it just says "Application not installed". I've set his device to not verify installs and I've made sure his install applications not from google play option is checked.
In the actual code, I have the minimum api set to 14, and the target set to 17. Still I can't get it to install.
Does anyone have any idea what could be causing this?
The apk needs to be signed. You can do this from Eclipse: right click on your project -> Android -> Export Signed Application package. More info here: http://developer.android.com/tools/publishing/app-signing.html.
For others still wondering why this is happening.
Please note that if you are using android studio 2.3 or above and have
used signature versions v2(full apk signature) then your app may cause
installations problems on previous versions.
Solution use traditional jar signature scheme v1 while Generating APK.
for more info hit this link
I am a newbie to Android world and started learning it few days back. I developed a sample application Using Eclipse and ADT pluggin. Checked it on Emulator, it's working. But when I exported that App as *.apk and tried to install it in my phone (Samsung Galaxy S running 2.2) ... it gives error that "Application not installed"
Can somebody throw some light on this ?
If the one on your device is signed with another key (e.g., debug), you
won't be able to install the other one over the top. You're not allowed to replace an application with another that has a conflicting signature. Uninstall the old APK, then try again.
I'm a newbie too & i had the same issue.Just uninstalled the previous app, and freshly exported a new apk file with keystore information. Then i was able to install it the newer version.
Did you enable "Unknown Sources" in the Applications Settings menu on your phone?