I removed an app existing in data folder of my device using adb shell , but while installing the app from my code in device its showing error that can not install over already existing signature. As of now, no app or package exist in my device of the same application.
Try to install it with help of "pm install" (not adb install) and post error text here. Possibly it's not fully uninstalled (which is ridiculous but possible in some cases). Also you need to be sure that app signed with production key and (if it's preinstalled app) with vendor key. In other case it's work would be unpredictable.
Related
I'm trying to make sure a particular test device (Pixel 3) will install a new version of an apk but whatever I do it seems to be running an older version.
Tried so far:
adb uninstall <app_name>
adb install -r <app_name>
Manually clearing it's cached data and uninstalling on device
Restarting device between uninstall and reinstalls
No matter what I do the app appears to be the previously installed version. I'd think I was crazy but I've had issues with the auto-backup on Pixel devices hiding logs, restoring preferences & cache data before.
Any suggestions on how I can 100% force a purge of all the data to do with this apk so I'm guaranteed a fresh install?
You have to set a property in your manifest allowBackup=false and make sure your instant run is disabled.
For manually uninstalling the app, try:
adb shell pm uninstall <app_package_name>
If the app is installed, this will say success. If the app is not installed, you usually get an error message.
For installing the app, try with out the "-r" parameter:
adb install <app_package_name>
Note that installing with the "-r" parameter is for an app update, and thus if you already have the app installed, and do not have a newer app build version (as declared in build.gradle) then it will keep the current version. With just adb install you will see a message if the app already exists.
To check if the app is installed, you can look for the app package name on the device with:
adb shell pm list packages -f
If you are installing via AndroidStudio, try turning off instant run options by going to Preference and searching for instant run, and having enabled unchecked. Cleaning build, maybe even an invalidate and re-sync caches and try again.
I've built a silly app to share among a few friends. No need to put it up on the app-store.
I built the first apk (signed), uploaded it to a web-server and all worked well.
A small issue arose, I fixed it, re-built, signed with the same keystore and uploaded it again. It now seems that I am unable to install from the new apk. The debugger tells me:
signatures do not match the previously installed version
So I uninstalled the old version by opening the app drawer and dragging it onto the "uninstall" button. When opening "Settings -> Apps", I don't see it anywhere anymore. I don't see any traces of the app on my device.
Yet I still get the above error message.
Is it possible some information still lingers on the device somewhere? Is there any way I can verify that?
Yes It is possible if somehow your old application is not removed 100% or its data is not removed.
Try:
adb uninstall "com.yourapp.yourapp"
If you don't know exactly what to put as replacement for "com.yourapp.yourapp", then you just open Android studio, Run your app while it is connected to a device and then look at Debug window.
It says:
Waiting for device.
Target device: samsung-sm_t531-xxxxxxxxx
Uploading file
local path: C:\Users\myapp\app\build\outputs\apk\myapp.apk
remote path: /data/local/tmp/com.myapp.myapp
Installing com.myapp.myapp
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.myapp.myapp"
pkg: /data/local/tmp/com.myapp.myapp
Success
com.myapp.myapp in this case is the name of the package you must use to uninstall.
I had the same issue and the adb uninstall solution did not work for me.
What worked was
On your device go to to Settings->Apps
Select your app, and in the menu select "Uninstall for all users"
Even if I had previously uninstalled the app it was still in the list there.
To me, if the app is meant to be distributed, the adb solution is a no-go: you can't ask one's friend to have the android sdk installed on their machine !
The way to go here is to edit the AndroidManifest.xml and to increment the android:versionCodeattribute in the <manifest>tag (which is the root element).
This would update your installed application
If you are seeing this while conducting connected tests, make sure to include .test when uninstalling via adb because uninstalling via app -> settings does not get rid of the test package
adb uninstall your.broken.package.test
if you just uninstall via
adb uninstall your.broken.package
your test package will still be there. This was only something i noticed while using the gradle command line, haven't come across this problem within android studio
Uninstall the old app from your phone or emulator and try to run again.
I got that error while trying to install release while signing it's certificate.
fixed with the :app Gradle task uninstallRelease and then installRelease again
If you are going in install the same app with a different signature, you may want to uninstall but keep the app's data.
adb -d shell pm uninstall -k <packageName>
adb -d install -r -t -d app.apk
For Unity users who come to this question, the best answer is indeed the one above by #Ehsan
adb uninstall "com.yourapp.yourapp"
I had already installed a previous version on my Android device then selected Development Build in Unity > Build Settings which caused the APK to use a different signature. If you install through the Android GUI it doesn't actually remove everything so you have to use ADB.
I had face same problem With POCO Mobile and Moto G30 Mobile while developing application in flutter
My Solution is:
I have open android project which automatically create in your project, in android studio and run project in connected device. It will automatically ask to uninstall old app with same package name and different signature. After click ok button it will install app.
I'm running on a device with a custom Android platform for which I have the platform.keystore certificate. I was able to build an application, sign it with the platform key, and install it on my device. However, now that the package has been installed, I can't seem to uninstall it from the command line.
Since the device is running a production build of the OS, I can't run adb root from the command line to gain permissions. Also, I'm unable to run su from adb shell since I don't have permissions, so I can't go into /data/data and force remove the package.
I can think of a couple ways of uninstalling the package NOT from the command line:
Go into Settings->Apps and click Uninstall
Create another platform-signed app that uses reflection to access the uninstall API from PackageManager to uninstall it. Along these same lines, I could have the app send an Intent to PackageManager to prompt the user to uninstall the package.
That's great, but I'd really like to be able to uninstall the package from the command line. It seems like there should be parity here. Is there a way to uninstall a platform-signed package from the command line considering I have access to the signing certificate?
Do you know the app's package? If so, try
adb uninstall *com.name.of.package*
(as documented, for instance, at this site ).
I'm tired of uninstalling and than reinstalling in development.
Is there a way to do adb -force install some.apk ? I mean this would save a lot of time. Each time going to system ->apps->uninstall every time a signature is different.
Obviously debug is a dev setting so I don't see why one constantly needs to uninstall the app manually, what a waste of time? Anything that can make development easier is going to result in better code, and better apps so whats up with this?
I have hot deployed to server side Java EE servers in less time. This is less an issue on command line, since one could do an uninstall or replace the adb script with an uninstall followed by an install.
However in eclipse its still a pain. It has been pointed out that this is largely about signature changes. Yes, it is. But why should signatures change in development, and debug mode, and cause the reinstallation issue?
adb has [-r] parameter to reinstall.
adb install -r some.apk
A web search you could have done reveals that the answer to your adb question is:
adb uninstall some.package.name
Note that it's not the file.apk name you use with adb install, but rather the actual package name it ends up installed as.
The normal build process uses the android debug keystore that can be found in your android folder in your home directory (path depends on your OS).
With this debug keystore your app will be signed. This debug signature can be installed on every android device in the world as long as there isn't your app with another signature already installed.
When you say you only do code checkouts, rebuild and your signature is different, than probably your build process is broken. Your debug keystore is valid for at least a year and as long as you are on the same PC while building the generated APK should never have a different signature.
For further checking you should bring some light in your development process. What do you use? Eclipse?
If you work on different developing machines, pick one keystore from one machine and put it into your version control and use this to sign your apk with the debug signature.
adb install -r -d path/to/file.apk
-r to replace
-d to force downgrade
You can install an app forcefully by passing -r parameter.
-r parameter lets adb to reinstall the app.
adb install -r app-release.apk
The debug keystore can be set in Eclipse in Preferences/Android/Build/Custom debug keystore, which is very helpful when working in a team. Every member should set up the same keystore there, and then it is no problem any longer to share devices.
for uninstall
adb uninstall app_package_name
for install
adb install app_package_name
into the command prompt in windows
and terminal in linex/Macos
I'm about to publish a new version of an app to the Market. In order to avoid any potential problems once its been pushed to the Market and people get notified of an update, I'd like to simulate that process on my phone using the .apk for the new version of the app I'll be publishing.
For instance, it has an update to the SQLite DB it's using.
The closest I can find is using the Android Debug Bridge (adb) using the command:
adb install C:\myApplication.apk
with my phone attached to my PC via the usb cable.
(the parameter represents wherever your apk file is on your PC).
When I do this, if the app is already installed on my phone, I get an error message:
Failure INSTALL FAILED ALREADY EXISTS.
If I delete the existing app from my phone, the adb install command works fine.
So, it looks like this can only be used to install an app that doesn't currently exist on your phone.
Is there any way to simulate the update process?
It'd be nice if there was an adb update command, but I don't see that.
Try using option -r to adb install:
adb install [-l] [-r] [-s] -
push this package file to the device
and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its
data)
('-s' means install on SD card instead of
internal storage)
The closest I think you can get is to put the APK somewhere, and download it on a phone. That is about the closest you can get to the real market situations, with the only difference being that you need to add the "unknown sources" option.
(on a sidenote: you can get an error installing an apk with the same package-name, but a different signing.)
I think your error is because you have the market signed version installed and your trying to install a debug signed version. If you sign it with your market key it should install fine.