Getting error "The package appears to be corrupt" while installing apk file
AndroidAndroid StudioAndroid Problem Overview
I am having a weird problem.I got this error after I updated Android Studio from 2.3.3 to 3.0..The problem is when I try to install apk file it says
App not installed. The package appears to be corrupt.
I have tried generating apk in both debug and release version and tried to install but whenever I install apk it show the same message..
When I run the android project from android studio it is working. May be the gradle problem but couldn't fix it. Please help
Android Solutions
Solution 1 - Android
After searching a lot I found a solution:
Go to Build-> Build Apk(s).
After creating apk you will see a dialog as below.
Click on locate and install it in your phone
Enjoy
Solution 2 - Android
As I got this case at my own and the answers here didn't help me, my situation was because of I downgraded the targetSdkVersion in gradle app module file from 24 to 22 for some reason, and apparently the apk doesn't accept another one with downgraded targetSdkVersion to be installed over it.
So, once I changed it back to 24 the error disappeared and app installed correctly.
Solution 3 - Android
When you are releasing signed apk , please make sure you tick both v1 and v2 in signature versions
See below screenshot for more info
Solution 4 - Android
In my case; If you receive this error while updating your application, It may be because of the target SDK version. In such case you will receive this error on logs;
"Package com.android.myapp new target SDK 22 doesn't support runtime permissions but the old target SDK 23 does"
This is because your previous aplication was build with a higher version of sdk. If your new app was build with 22 and your installed application was build with 23, you will get The package appears to be corrupt error on update.
Solution 5 - Android
This is weird. I don't know why this was happening with me while generating signed apk but below steps worked for me.
- Go to file and select invalidate caches/restarts
- After that go to build select clean project
- And then select Rebuild project
That's it.
Solution 6 - Android
In my case, the target phone had the app already installed, but in a "disabled" state. So the user thought it was already uninstalled, but it wasn't. I went to the main app list, clicked on the "disabled" app, uninstalled it, and then the APK would go on.
Solution 7 - Android
In my case by making build, from Build> Build apks, it worked.
Solution 8 - Android
None of the answer is working for me.
As the error message is package corrupt
adb uninstall <package name>- Run app again / use adb install
Solution 9 - Android
Running a direct build APK will work. But make sure you uninstall any previously installed package of the same name.
Solution 10 - Android
In my case, I had a problem with my module level build.gradle file. I somehow had removed the line
compileSdkVersion 32
from the file. This didn't prompt any issue during the build time but only when installing which is where "The package appears to be corrupted" line occurred. Adding the line back solved my issue.
Please re-check your build.gradle and AndroidManifest for any anamolies since the corrupt message is very ambiguous and hard to debug the exact cause for the issue.