Android 安装_FAILED_UID_Changed

Just uninstall the app itself (not the data folders) then reinstall it, and it should be fine. Android's complaining because you may have previously debugged the app from another computer.

Restart your device, and clear your project. Basically , uninstalling would have done this for you in case if doesn't then try restarting.

You probably introduced an SharedUserID which causes this.

Sometimes you have to also uninstall the data folders. For me, I had a package in userspace of com.kikin.cts, and also a folder directory in /data/data/com.kikin.cts. Kept getting INSTALL_FAILED_UID_CHANGED, but after removing the data folder, the error went away.

Okay, so for my LG NEXUS 4 rooted here is the solution: (

• make sure you have somewhere your working app apk signed or unsigned)

and

• you uninstalled this file from your phone (if exists of course)

Let's say it is: app-debug-unaligned.apk

Now in console you write:

adb push app-debug-unaligned.apk /sdcard/
adb shell
su
rm -fr /data/local/tmp/app-debug-unaligned.apk
rm -fr /data/data/app-debug-unaligned.apk

Now exit from adb and call

adb shell su -c "pm install /sdcard/app-debug-unaligned.apk"

Working?

I got another solution working for me. You can change the package name of application, so that device recognizes it as different application and installation completes successfully. Might be helpful for those who don't have root access and also don't want to reset device.

This worked for me:

adb shell rm -rf /system/app/<package.name>

I do have root on my Nexus 5, but nothing worked, so I had to run a factory reset from the settings which worked.

For me, there was a bit more to it. Simply removing /data/data/appfolder didn't help.

The additional reason was that my external libs weren't included in .apk file because the name of folder was lib instead of libs. This has caused [INSTALL_FAILED_DEXOPT] during apk installation followed by [INSTALL_FAILED_UID_CHANGED].

So changing libs folder name worked for me in this case.

A solution for non-rooted device. Go to the Application manager and uninstall the app called "Selendroid" and retry again. This solution works for me.

For me the trick was done by unchecking "Verify apps over USB" in the "Developer options" section.

Rooting and factory reset were not an option for me, but I was able to find an older version of my APK and install that (I'm guessing it was the same one that failed to uninstall properly). After uninstalling that one again, I was able to install new versions.

From the ADB shell you can find solution in two ways. 1. keep the data and find the solution and 2. solution without persisting the data

solution for 1. is to run the commandadb chown -R UID:UID /data/data/your.package.name through command prompt from ADB path.

solution for 2. is to run the command adb rm -r /data/data/your.package.name from the same path.

I fix this, maybe it will work anyone else.

I'm restart my phone, then remove a few more app. And try again to install, it's work!

Maybe problem is about to storage. I don't know why, but it's work now. Good luck! (Sorry about bad English)

Use

adb shell

go to the shell.
Then run the command follow:

rm -rf /data/data/package name

please repleace package name with your own, such as com.map.map

I was experiencing this issue for the past couple days on my Galaxy Note 3 test device. I have been using Calabash-Andrdoid and kept getting an error INSTALL_FAILED_UID_CHANGED, whenever the install_app method tried to execute. I was struggling with this issue because I had two test devices experiencing this. I tried everything above, including emptying out my /data/data/ app and app.test folders. I even deleted the instrumentation back-end stuff that Xamarin installs since that's the platform I used to develop my app. I could not find anything else to manually delete off of the device. When I attempted to do my work on third device and found that everything ran successfully, I realized the issue was with the devices. In the end, the only thing that worked for me was to execute a factory reset of one of the devices. I hope this helps.

Thanks, -Shah

Thought I'd share this in case it helps someone... I wrote a new version of my app in eclipse and tried to run it on my phone despite having a slightly older version on the phone that I downloaded from Google Play store. Eclipse popped up a dialog asking if I was happy to uninstall the existing on-phone version and I agreed. The uninstall was defective and led to INSTALL_FAILED_UID_CHANGED.

I tried most of the things suggested here with no luck. There was no apparent trace of the APK on my phone, or any data files I could find to delete, but something was preventing me from loading the APK onto the phone from eclipse. I also could not download my previous beta-testing version from Google Play - the download proceeded to 100% but then failed with a message reporting "unknown error", and a number (probably -24).

I was hesitant to rename my package because I already have beta testers and in-app products set up with the old package name, but I changed the package name in eclipse temporarily and I was able to install that new version onto the phone and then download the older Google Play version as well. Both versions sat happily beside each other on the phone with the same app name and icon (but different package names behind the scenes). I could then manually uninstall either or both by dragging the app icon to the uninstall icon of the phone. The manual uninstall removed the conflict and repaired eclipse's defective uninstall, so I simply renamed my eclipse package to the original name and carried on as before.

This was much less painful than a factory reset or permanent package rename. It probably only works when the source of the error is a conflict between an eclipse version and a Google Play version, but it is worth a try if you are in a similar situation.

In most cases INSTALL_FAILED_DEXOPT or INSTALL_FAILED_UID_CHANGED means that you have not enought space to install the app.

Remove some unused apps from your device or at least remove current version of your app.

adb uninstall package-name

In very rare cases there may be problem with application data. You have two options depending on whether your device is rooted or not

Non-rooted

Factory reset Settings -> Backup and reset -> Factory data reset (at least for Samsung S5)

Rooted (or emulator)

adb shell "rm -rf /data/data/package-name"

For anyone running Junit style tests from their computer and getting this error- while the console it told me there was a problem with my application (packaged in the format 'com.myapp.stuff'), the real issue was my test code package, which if you're running on a device gets installed as a separate app with the package name like 'com.myapp.stuff.test'. Deleting the test code "application" using the Application manager and deleting my actual app solved the problem for me. I'm posting this answer here to save someone else a "Duh" moment.

For rooted devices:

Run the below command

adb rm -rf /data/data/<your.package.name>

For non-rooted device:

1. Change the ApplicationId of the app. Refer this link to change ApplicationId.
2. Build and install the app. App will install successfully because it is treated as new app.
3. Now uninstall this app. Which will clear the data.
4. Now change the ApplicationId to the previous one.
5. Build and install. Magic.. It will install.

Same problem on a Mediacom device, first a

$ adb install -r platforms/android/out/android-debug-unaligned.apk
3958 KB/s (22887489 bytes in 5.647s)
pkg: /data/local/tmp/android-debug-unaligned.apk
Failure [INSTALL_FAILED_DEXOPT]

then a very persistent:

$ adb install -r platforms/android/out/android-debug-unaligned.apk
4949 KB/s (22887489 bytes in 4.515s)
pkg: /data/local/tmp/android-debug-unaligned.apk
Failure [INSTALL_FAILED_UID_CHANGED]

Doing a factory reset didn't change the dynamic (I got both errors, in sequence).

• installing the same app with a different id worked
• installing a different app with the previous id doesn't

Rooting not an option, the solution for me was a cache wipe: now the offending app id works fine and I didn't had to factory reset (again).

Hope it helps

I deleted /data/data/my.package.name and /data/app/my.package.name.apk, problem still persistent.

however I found a folder /data/user/0/my.package.name, delete it and problem solved.

Here's something not covered by the existing answers. This was happening to me on emulator. If I reset user data, I get INSTALL_FAILED_DEXOPT the first time, but INSTALL_FAILED_UID_CHANGED after that. I found that rm -r /data/data/com.foo.bar is enough to reset to the first state.

The actual culprit in my case is a java method name that caused dexopt to fail. Pay very close attention to what's in logcat. Here's what gave it away:

I/PackageManager( 1275): Running dexopt on: com.foo.bar
E/dalvikvm( 2857): Invalid name: '__jni_setLocation'
E/dalvikvm( 2857): Trouble with item 14787 @ offset 0x43b68
E/dalvikvm( 2857): Cross-item verify of section type 0005 failed
E/dalvikvm( 2857): ERROR: Byte swap + verify failed
E/dalvikvm( 2857): Optimization failed
W/installd(  941): DexInv: --- END '/data/app/com.foo.bar-1.apk' --- status=0xff00, process failed
E/installd(  941): dexopt in='/data/app/com.foo.bar-1.apk' out='/data/dalvik-cache/data@app@com.foo.bar-1.apk@classes.dex' res=65280
W/PackageManager( 1275): Package couldn't be installed in /data/app/com.foo.bar-1.apk

I can't tell you why dexopt doesn't like some method names, but that was the problem.

I found a solution that works both on a non-rooted device and on an emulator. While you can't directly delete the data folders on a non-rooted device you can utilize the pm command to do that:

1. Run adb shell
2. Run pm uninstall <app name> (i.e. com.example.myapp)
3. Run pm uninstall <test app name> (i.e. com.example.myapp.test) - you might receive an error if the test app wasn't installed before.

It seems that for some reason when uninstalling the apps from the Android UI this doesn't work (possibly it doesn't delete the data folders) however when uninstalling via the pm command it does work.

Tried it on a "Nexus 5" and on a "OnePlus One".

It is obviously because of improper uninstall (probably due to faulty cable connection).

Download SDMaid from play-store, and delete Corpse files (junk files). Re-run application. (But you need to have your device rooted)