Installation failed due to: 'null' - Android Studio 3.5

Question

I have updated Android studio to 3.5, ever since I am running into an APK installation problem. This is the only log it shows:

Installation did not succeed.
The application could not be installed: INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION
Installation failed due to: 'null'
Retry

This happens when trying to install APK on a real device. If I uninstall the app from the device and then rerun the build, it installs only one time and then it keeps throwing this error on the next installation. It runs fine on an emulator but I can not use an emulator for everything.

What I have tried:

Deleted Android Studio configuration file.
Deleted Gradle files from the project.
Invalidated and reset caches.
Cleaned/rebuilt the project.
Looked for similar problems Stackoverflow(nothing matches my problem)
Clean installed(Removed all files including SDKs) Android Studio 3.5

Update

I installed Linux Mint on my machine and tested the AS 3.5 there, for some reason everything is working fine even for Android 7 and below devices.

Previous OS: Windows 10 1903

Current OS: Linux Mint 19.2

I reckon this problem may be originating from Windows machines.

I have similar problem - but for me it's `INSTALL_PARSE_FAILED_NOT_APK` while running Espresso tests — adek111, Aug 21 '19 at 19:46
Did you check if the Instant Run is enabled in your Android Studio? — Reaz Murshed, Aug 23 '19 at 06:11
But I think I saw a similar thing like instant run when I updated my Android Studio. Let me check again. — Reaz Murshed, Aug 23 '19 at 06:38
@ManoharReddy I think the apply changes is the same thing as Instant Run. — Reaz Murshed, Aug 23 '19 at 07:07
@ReazMurshed Actually it's completely different from instant run , its a complete rewite from scratch — Manohar, Aug 23 '19 at 07:09
I see. Thanks for the information. Will dig for a better understanding once I have some time. — Reaz Murshed, Aug 23 '19 at 07:11
In android studio 3.5 instant run is removed so how to handle error — Suyog Dorlikar, Aug 23 '19 at 13:12
Oh I see. I haven't updated yet. But i got same error yesterday in 3.4 so above my comment worked! — Piyush, Aug 23 '19 at 13:14
Looks like this feature is broken as well as instant run. I have to clean build every time (which is on each run) to successfully install APK on the device. — Skyyy, Aug 25 '19 at 19:35
See my answer below. I found the solution here: https://developer.android.com/studio/run#apply-changes-run-fallback. Tested on a device running Android 9. I haven't tested it on other version. — Muhammad Baja Aksha, Aug 26 '19 at 13:57
Finally, I got the solution in the code edit run configuration changing in Installation option DEPLOY--> from select 4th option -->(Nothing) option --> Apply And the app works properly in android studio 3.5. In mobile and emulator also. This work properly in android version 9 also This is a permanent solution. — Suyog Dorlikar, Aug 28 '19 at 13:06
Apart from all the answers shared here, this error can also occur if your device support a different compile version than what is mentioned in the build.grade file. This can be tested by running the app on AVD with an emulator matching the API version mentioned in the file. If it runs fine, then to run it on your device you need to lower the API version to match with the one that is supported by the device. — skdhfgeq2134, Dec 29 '22 at 09:33

score 108 · Accepted Answer · edited Mar 02 '21 at 09:39

108

Open Run/Debug Configuration dialog (Windows: Run > Edit Configurations)

edit You app > General > Installation Options > Install Flags .

add install flags -r -t.

This flags means adb install -r -t apkpath

screen pic

edited Mar 02 '21 at 09:39

Saeed

3,294
5
35
52

answered Aug 27 '19 at 09:20

胡晟昊

1,196
1
7
6

2

This flags means `adb install -r -t apkpath`,I guess.@TaseerAhmad – 胡晟昊 Aug 29 '19 at 02:40
28

`-r` means "replace existing application". `-t` means "allow test packages" – duckbrain Aug 31 '19 at 00:01
2

Where did this man come from and how did he think of this solution? Give him a medal! – 0101100101 Sep 03 '19 at 02:44
7

Not working for me! :( Please look at my problem. Its a little different than yours. https://stackoverflow.com/questions/57770464/installation-did-not-succeed-the-application-could-not-be-installed-installati/57770776#57770776 – Syed Arsalan Kazmi Sep 04 '19 at 10:42
1

It's working for app install but not for tests. When I try to run androidTest. – Yogesh Umesh Vaity Sep 06 '19 at 10:36
3

The setting is Run > Edit Configurations, if windows version. – Beatrice Lin Sep 24 '19 at 02:25
1

That was just amazing – Minasie Shibeshi Oct 07 '19 at 18:22
Works like charm – Polycarp Kavoo Jan 21 '20 at 11:11
thank you so much for this tidbit - I was having to remove my app before each debugging session after upgrading Android-Studio ... now it works on it's own! – Ryan Barrett Jan 27 '20 at 17:06
It does not work for me – Gulnaz Ghanchi Oct 08 '21 at 12:43

score 24 · Answer 2 · answered Sep 25 '19 at 09:43

24

You need disable "Use libusb backend" in preferences--> debugger

answered Sep 25 '19 at 09:43

Houssin Boulla

2,687
1
16
22

Only this solution helped - Xubuntu 18.04 – Raskilas Oct 07 '19 at 04:00
Cant believe this worked! Android Studio 3.5.1 Android Debug Bridge version 1.0.41 Version 29.0.5-5949299 – Kebab Krabby Nov 04 '19 at 13:27
1

Works like charm. Struggled with this problem for months and only this answer worked for me – srisindhu saride Nov 15 '19 at 13:18
1

OMG! this has solved a big big problem. Struggled with this problem for months as wel.. Wow! – Vivek Jul 24 '20 at 23:16
1

Fixed this for me on OSx 10.15! Thank you! – Chris.Jenkins Oct 07 '20 at 23:17

score 12 · Answer 3 · answered Aug 22 '19 at 21:11

12

This issue in Android Studio happens for devices lower then API 26 (Android 8). This is caused by replacement of InstantRun, known now as ApplyChanges.

Seems to be there are only two ways before they fix it in the next update.

Run on API>=26.
After every change in code edit run configuration changing deploy from APK to App bundle and vise-versa. If I correctly understand, this will correctly rebuild app and workaround bug.

Of course, there is an option to manually delete app from device before running app from AndroidStudio.

answered Aug 22 '19 at 21:11

mohax

4,435
2
38
85

1

I have an Android 9.0 device and have this problem. However, when I mix running tests between emulator and then real device, app and tests appear to be running quite often. I don't really know why but maybe it will help someone. – adek111 Aug 23 '19 at 13:39
Maybe you can successfully rerun app on `API26+` if you click `Apply changes`, instead of `rerun`? This is new button to right of `rerun`. – mohax Aug 23 '19 at 17:01

score 11 · Answer 4 · answered Jul 07 '20 at 11:36

11

Build > Clean project its work's for me. Before change other setting try this first.

Happy coding :)

answered Jul 07 '20 at 11:36

happy_coding

1,064
1
13
24

score 7 · Answer 5 · answered Aug 24 '19 at 18:21

7

For me either uninstalling the app or cleaning project "solves" the problem. To make it less frustrating I added clean job to debug build type like so:

buildTypes {
    ...
    debug {
        clean
    }
    ...
}

answered Aug 24 '19 at 18:21

Sancho

220
2
9

score 6 · Answer 6 · answered Aug 26 '19 at 13:53

After reading the Release Notes regarding Apply Changes, I finally found a solution here: https://developer.android.com/studio/run#apply-changes-run-fallback

Enable Run fallback for Apply Changes

After you've clicked either Apply Changes and Restart Activity or Apply Code Changes, Android Studio builds a new APK and determines whether the changes can be applied. If the changes can't be applied and would cause Apply Changes to fail, Android Studio prompts you to Run Run icon your app again instead. However, if you don't want to be prompted every time this occurs, you can configure Android Studio to automatically rerun your app when changes can't be applied.

To enable this behavior, follow these steps:

Open the Settings or Preferences dialog:

On Windows or Linux, select File > Settings from the menu bar.

On macOS, select Android Studio > Preferences from the menu bar.

Navigate to Build, Execution, Deployment > Deployment.

Select the checkboxes to enable automatic Run fallback for either of the Apply Changes actions.

Click OK.

I have changed OS to Linux and AS 3.5 is working fine there. — Taseer, Aug 27 '19 at 22:10

Pedro Oliveira · Answer 7 · 2019-10-07T13:23:11.993

There is a problem with Lineage OS as stated by Google team in https://issuetracker.google.com/issues/139782879:

We are able to reproduce it on a device with LineageOS. It does not fully support a system call that we use for DeltaInstall.

There is no apparent solution (other than removing the APK from build folder or uninstalling the application).

We should have a workaround for it but as it stands right now, LineageOS will not have DeltaInstall and will always need to perform a slower full install.

Changing to Nothing as pointed out by OP will not deploy the APK to the device (that's why an error will not be displayed), so it will not solve the problem.

Edit:

This has been fixed in Android Studio 3.6.

Thanks for the feedback. This should be fixed in the latest versions of 3.6.

Suyog Dorlikar · Answer 8 · 2019-09-13T06:29:13.900

I got the solution in the code edit run configuration changing in Deploy select Default APK and install flag =-r -t and then Apply for the run. The app will run in all devices and emulator. I was testest in OPPO 1 plus, Samsung Tab, Emulator Also.

Please Go thought the Edit Run configuration near to run button in Android Studio

edit app > general ==> installation options ==> Install flags

add install flags -r -t

-r means "replace existing application". -t means "allow test packages"

score 3 · Answer 9 · answered Feb 18 '21 at 16:34

3

1-clean project from Build -> CleanProject

2-delete folder outputs from ProjectPath/app/build/outputs

3-then build gradle and run app

answered Feb 18 '21 at 16:34

Farid Sharif Moghaddam

157
3
12

Chooven · Answer 10 · 2019-09-03T22:26:51.133

2

I too am having this same problem after upgrading to 3.5. I was wondering if you have had any luck getting 'Run' to work with a connected device?

UPDATE: I was am to get this to work by Setting "APK from app bundle" under Installation Options in the "Run/Debug Configurations" dialog

edited Sep 03 '19 at 22:26

answered Aug 26 '19 at 21:52

Chooven

105
5

score 2 · Answer 11 · answered Oct 03 '19 at 08:42

2

I also got this error when I ran the application on real xiaomi pocophone 1 and solved this problem by running the application first on the emulator, and then on my xiaomi pocophone 1

answered Oct 03 '19 at 08:42

ch13mob

261
6
11

score 2 · Answer 12 · answered Sep 13 '21 at 02:27

2

I got this because the device was locked and required user to accept permissions in order to install it. (Huawei Harmony OS)

Unlocking the phone to prepare for the installation process solved the issue.

answered Sep 13 '21 at 02:27

htafoya

18,261
11
80
104

score 2 · Answer 13 · answered Dec 22 '21 at 07:27

If your app targets Android 12 or higher, you must declare these attribution tags in your app's manifest file. If the app component includes the LAUNCHER category, set android:exported to true.

 <activity
    android:name="com.test.activity.SplashActivity"
    android:clearTaskOnLaunch="true"
    android:label="@string/app_name"
    android:launchMode="singleTop"
    android:noHistory="true"
    android:screenOrientation="portrait"
    android:theme="@style/AppTheme.NoActionBar"
    android:exported="true">

Also check receiver or service in Androidmanifest, if you are using any receiver or service set android:exported="true" or false according requirement.

<receiver
    android:name="com.test.receiver.ShareReceiver"
    android:exported="true">
    <intent-filter>
        <action android:name="com.test.fcm.android.action.broadcast" />
    </intent-filter>
</receiver>

 <service
    android:name="com.google.android.gms.tagmanager.InstallReferrerService"
    android:exported="true" />

Also update all your gradle dependency. I have updated following dependency as per requirement.

testImplementation 'junit:junit:4.13.2' 
androidTestImplementation 'androidx.test:runner:1.4.0'


androidTestImplementation 'androidx.test.espresso:espresso-core:3.4.0'
implementation 'com.razorpay:checkout:1.6.15'

Hope it will help you as well.

score 1 · Answer 14 · edited Aug 22 '19 at 13:26

1

Deleting/uninstalling the app from the device fixed the problem for me.

edited Aug 22 '19 at 13:26

MaartenDev

5,631
5
21
33

answered Aug 22 '19 at 09:58

Alex Sag

21
2

I uninstalled the app from API 29 emulator and it helped. – CoolMind Mar 04 '20 at 16:52

shizhen · Answer 15 · 2019-08-29T07:17:04.383

Add a "clean" gradle task dependency before installing/running your apks using below configuration.

project.afterEvaluate {
    android.applicationVariants.all { variant ->
        variant.outputs.each { output ->
            def capitalizedVariant = variant.name.capitalize()
            def assembleVariantTask = project.tasks."assemble${capitalizedVariant}"
            assembleVariantTask.dependsOn clean
        }
    }
}

Copy and paste above code into your app/build.gradle file, this works for all the build variants.

In specifically, above code will be equivalent to below if you only have debug and release build types:

assembleDebug.dependsOn clean
assembleRelease.dependsOn clean

score 1 · Answer 16 · answered Sep 11 '19 at 06:38

1

What Worked for me to remove old application, then rerun the project. In that case old sign certificate does not bother.

answered Sep 11 '19 at 06:38

Azamat Mahkamov

912
14
18

score 1 · Answer 17 · answered Oct 07 '19 at 03:28

splits {
    abi {
        enable true
        reset()
        include 'x86', 'armeabi-v7a','x86_64'
        universalApk true
    }
}

Due to the different constructions such as 'armeabi', 'x86', 'armeabi-v7a', 'x86_64', and 'arm64-v8a', we have to add the configuration above into build.gradle file.

score 1 · Answer 18 · edited Sep 04 '21 at 16:05

1

For me I added accidentally new BlankActivity which is inherited from Wearable Activity. Then I deleted the activity code and layout file. But I forgot to delete the wearable related tag in App Manifest.xml file. This is the main problem for someone like me.

edited Sep 04 '21 at 16:05

Vadik Sirekanyan

3,332
1
22
29

answered Sep 02 '21 at 13:39

Wai Yan

137
1
9

score 0 · Answer 19 · answered Aug 21 '19 at 14:02

0

At last, I found the solution

just set v2SigningEnabled true

 signingConfigs {
    release {
        v2SigningEnabled true
    }
}

answered Aug 21 '19 at 14:02

yefeng

111
1
14

score 0 · Answer 20 · answered Aug 23 '19 at 07:06

I did not face the problem myself. However, previously we had some problems with the Instant Run of the Android Studio. I would like to suggest checking the following settings in your Android Studio and uncheck the settings to check if your code works now.

Go to the Android Studio -> Preference and then uncheck the following under the Deployments.

Here's what is new in Android Studio 3.5 regarding this which will help you to understand the feature better.

score 0 · Answer 21 · answered Aug 31 '19 at 10:49

0

Try to run the command "adb devices", if the output is empty, then reconnect the device. This helped me with the same error. Android studio 3.5 does not determine that the device has disconnected.

answered Aug 31 '19 at 10:49

Boris Timofeev

101
3

score 0 · Answer 22 · edited Oct 22 '20 at 11:22

0

It bug still have on my mac os, when i get new real device and try install apk from android studio 3.5 - and I find ugly way how it fix - open terminal in studio and follow:

cd app/build/outputs/apk/debug
adb install -r -t your_app_name.apk

And it need to do with each project and each device!!

Edited:

I eventually installed

Android Studio 3.6 Canary

it's more working version than 3.5

But stiil need add into install flags -r -t

edited Oct 22 '20 at 11:22

Boken

4,825
10
32
42

answered Sep 08 '19 at 07:27

nicolas asinovich

3,201
3
27
37

We have to wait for a 'stable' 3.6 release. – Taseer Sep 11 '19 at 13:39

score 0 · Answer 23 · answered Oct 17 '19 at 16:00

0

I uninstalled the app from emulator, ran and everything went back to normal

answered Oct 17 '19 at 16:00

Woz

350
7
13

score 0 · Answer 24 · answered Nov 26 '19 at 02:36

0

For me minSdkVer = 22, tarSdkVer = 28,run Gradle -> app -> Tasks -> build -> clean && cleanBuildCache action, problem solved.

answered Nov 26 '19 at 02:36

Shanksiscool

33
7

score 0 · Answer 25 · answered Dec 01 '19 at 20:29

0

I pressed the hammer icon to rebuild the app then it installed. So I don't know? The whole android hack job platform sucks.

All that money yet google can't hire or find programmers good enough to come up with their own true operating system.

answered Dec 01 '19 at 20:29

dcarl661

177
3
9

score 0 · Answer 26 · edited Oct 22 '20 at 10:54

0

In my case, it only works by disabling the APK signature verification:

$ adb shell settings put global verifier_verify_adb_installs 0

And using the -r -t flags mentioned above

edited Oct 22 '20 at 10:54

Boken

4,825
10
32
42

answered Dec 13 '19 at 04:34

lgallard

462
3
10

score 0 · Answer 27 · answered Feb 20 '20 at 08:19

0

I also faced the same issue , i followed the following steps 1) Clean Project 2) Rebuilt Project

This solved my problem

answered Feb 20 '20 at 08:19

Vivek

586
6
11

B M · Answer 28 · 2020-04-07T16:13:00.240

0

In my case, I can't solve with all of the above answers so that I find another way. Finally, I found the solution. Just find the correct drivers of phone. My development phone is Samsung Galaxy Note 2 (MODEL : GT-N7105 / Android 4.1.2). I just share my solution to how I solved it. Hope save your time.

edited Apr 07 '20 at 16:13

answered Apr 07 '20 at 10:42

B M

1,863
1
25
40

score 0 · Answer 29 · answered Apr 12 '20 at 17:14

0

The problem occurs when you are testing a new module. First, you write it individually, and then add it to the main app. When you add it to the main app, delete your "test_app" from your phone.

answered Apr 12 '20 at 17:14

Станислав Гордеев

1

score 0 · Answer 30 · answered Apr 29 '20 at 10:19

0

Run -> Edit Configuration -> install flags: -r -t -> Apply -> Ok

answered Apr 29 '20 at 10:19

Savita Sharma

344
3
9

score 0 · Answer 31 · answered Oct 30 '20 at 08:40

I got this problem a few minutes ago when I tried running my app on real device and stopped gradle build before it finished. What I just did was to uninstall the app on device and rerun the app on both AVD and real device (simultaneously) and it worked. Hope this works for you too

Braian Coronel · Answer 32 · 2020-12-11T13:39:09.667

Main Solution

File -> Settings -> Build, Execution, Deployment -> Debugger > Disable Use libusb backend
Gradle (Flap to the right of the IDE) -> android -> app -> Tasks -> install -> uninstallAll or you can also do it by console in the following way:

$ ./gradlew uninstallAll

Other Tips:

Delete and create the app again in Run/Debug Configuration
- Installation Options -> Check Install for all users
Run/Debug Configuration -> Launch Options > Launch: Specified Activity > Choose an Activity
Install app using another physical device, version of the IDE or PC
Reinstall IDE and delete .android
Retry with the main solution

If you want to install and open the app you can use adb with the following commands:

$ adb install -r -t absolute-path.apk

$ adb shell am start -n "com.package.flavor.env/.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER

GL

Source

score 0 · Answer 33 · answered Jun 23 '21 at 05:14

0

For me the issue started when I created a new blank activity and Android studio created a Wearable activity for some reason. Once I removed all mentions to wearable activity from the manifest and I deleted the class everything went back to normal.

answered Jun 23 '21 at 05:14

Eddie

119
1
5

score -1 · Answer 34 · edited Aug 22 '19 at 07:44

-1

try to chang android:appComponentFactory="" to android:appComponentFactory="new","new" can be any words

edited Aug 22 '19 at 07:44

help-ukraine-now

3,850
4
19
36

answered Aug 22 '19 at 07:20

sh_ZJ

1

Suyog Dorlikar · Answer 35 · 2019-08-28T13:05:23.660

-2

Finally, I got the solution in the code edit run configuration changing in Installation option DEPLOY--> from select 4th option -->(Nothing) option --> Apply And the app works properly in android studio 3.5. In mobile and emulator also. This work properly in android version 9 also This is a permanent solution.

edited Aug 28 '19 at 13:05

answered Aug 28 '19 at 12:27

Suyog Dorlikar

88
7

score -2 · Answer 36 · answered Jun 30 '20 at 20:23

-2

gradle.properties -> android.enableAapt2=false

answered Jun 30 '20 at 20:23

sapeg

109
7

**DO NOT USE THIS!** Aapt has been deprecated in favor of aapt2, and will eventually be removed. This workaround will stop working, and cause other problems when aapt is removed – Zoe Jul 07 '20 at 11:54

Installation failed due to: 'null' - Android Studio 3.5

36 Answers36

Enable Run fallback for Apply Changes

Main Solution

Other Tips:

Linked