28

I am trying to run my app on my Xiaomi RedMi S2 from Android Studio 3.5. It throws an error while installing the app on the phone:

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

Syed Arsalan Kazmi
  • 949
  • 1
  • 11
  • 17

28 Answers28

40

I had the Same issue on a MAC, this is how I solve it, note: I was tried the method that mention @Manoj Kumar,

Un check this field in Preferences/Build,Execution,Deployment/Debugger

General Grievance
  • 4,555
  • 31
  • 31
  • 45
jcfuerte
  • 424
  • 4
  • 4
23

Targeting S+ (version 31 and above) requires that an explicit value for android:exported be defined when intent filters are present.

 <activity android:name=".MainActivity"
           android:exported="true">
      <intent-filter>
          <action android:name="android.intent.action.MAIN" />
           <category android:name="android.intent.category.LAUNCHER" />
      </intent-filter>
 </activity>
BASAVARAJ PATIL
  • 436
  • 3
  • 9
19

1.Open run/debug configuration dialog:- Run> edit configurations.

  1. Navigate to You app > General > Installation Options > Install Flags.
  2. add install flags -r -t.

Note: This flags means adb install -r -t apk path

enter image description here

I hope this will help.

Manoj Kumar
  • 332
  • 1
  • 7
9

For me, restarting the Android Studio solved the issue.

File> Invalidate Cache / Restart

6

Restarting the device after enabling developer mode and allowing usb debugging did the trick for me.

Syed Arsalan Kazmi
  • 949
  • 1
  • 11
  • 17
5

When you connect the mobile, it starts in the charging mode. Simply change the mode to Transfer Mode (Transfer Media or photos mode).

Now install the app again and it will work.

Akshay Chopra
  • 1,035
  • 14
  • 10
  • 1
    OH MY GOD!!! I spend multiple hours trying to fix this, toggling usb debugging, developer options, resetting authorizations, data and even factory resetting the device... Why isn't this switched automatically when you enable USB debugging??? – AXE Mar 20 '23 at 17:25
  • The libusb backend check option didn't help on Linux as suggested by another user. So unchecked, restarted PC. Then on the phone Selected `USB Tethering` on `'Developer Options' > 'Default USB configuration'`. This is with Android Studio Giraffe. – enthusiasticgeek Aug 19 '23 at 11:17
4
  1. You has installed the app which has same package name with different debug signature file.
  2. The different signature file lead to the fault
  3. At first please uninstall the apk that you has installed with different signature file。
  4. Then you install the apk again ,You'll sucess!
Ravi Makwana
  • 2,782
  • 1
  • 29
  • 41
3

It may be because of your phone's memory is full. you can delete some data from your phone and then try. for me it worked.

Aniruddh Parihar
  • 3,072
  • 3
  • 21
  • 39
PRIYA
  • 419
  • 4
  • 2
2

Tip: run from terminal adb install path/to/app.apk

Why? Cause it will give more information about the error - actually pointing to the place in manifest with the error. For example - in my case it was: 'Targeting S+ (version 31 and above) requires that an explicit value for android:exported be defined when intent filters are present]'

Ronen Rabinovici
  • 8,680
  • 5
  • 34
  • 46
  • Thanks a lot, this indeed led to an easy fix of the problem. The whole command with the default path where the auto-generated apks are stored is then as follows: `adb install app\build\outputs\apk\debug\app-debug.apk` – BenjyTec Jan 21 '22 at 12:17
1

A simple (unintended) restart to the computer did it for me (I tried to run on emulator)

Tiferet Cohen
  • 283
  • 2
  • 7
1

In my case I was using third party library, I have removed that library from gradle and reinstall the app. Successful

Abdul Basit Rishi
  • 2,268
  • 24
  • 30
1

Add this line to your '/gradle.properties':

# gradle.properties
android.injected.testOnly=false

Check https://gist.github.com/xujiaao/5fd127a72979cdc3c70dcc1324786f87 ,it work for me.

user14539562
  • 124
  • 3
1

Just use in this link. Disable Preference -> Build,Execution,Deployment -> Debugger -> Use libusb backend

Uncheck Use libusb backend

that's all. Enjoy your coding...

Mahendren Mahisha
  • 1,072
  • 11
  • 9
0

Chech to manifest file and search for a required library tag. And delete it. I solve it by this way.

0

I was trying everything but nothing seemed to work. But then I suddenly noticed that my phone blocked installation, so I unchecked "reject this to install" and at the another try the security checkbox popup, asking for letting the installation. After allowing everything worked. Conclusion: I just were probably too angry that i didn't noticed this popup earlier.

Noh Kumado
  • 1,551
  • 2
  • 9
  • 15
Yakub
  • 1
0

Just check in the AndroidManifest.xml file to make sure you are using permission and libraries that you need for your app. In some cases you may have wearable libraries and permissions in your AndroidManifest.xml file and yet you do not need them. This happened to me when I was adding more activities and Android Studio was creating them as Wearable Activities

0

I'm trying every thing from the answers but only one solution is just free some space on your phone for proper install the debagged app.

  • This recommendation was already provided. Instead of creating a duplicate answer, it's better to add a comment on the original answer, or simply up-vote it. – Bafsky May 09 '21 at 17:13
  • Or you can upvote an existing answer if it is the same as yours. – Jeje Doudou May 10 '21 at 08:28
0

I had this problem at one point in time. the only solution that worked for me was to delete the SDK and download a new vision. It turned out that ADB had a problem and it was not able to detect my device. uninstalling the SDK and installing another resolved the problem for me

The Codepreneur
  • 236
  • 3
  • 12
0

Create a signed apk and drag that apk to the emulated device, that worked for me

dreinoso
  • 1,479
  • 17
  • 26
0

go to the path of your debug apk, and rename of your apk like :

myApp.apk to myApp1.apk(just rename it) and try to run it again.

its works for me every time :)

Geet Thakur
  • 1,966
  • 1
  • 16
  • 23
0

TRY THIS!

  • Delete the build folder in your App and re-build the project, it should work now.
0

Accept agreement of terms and conditions by opening Google Maps and Google Chrome on a newly created emulator, your application might be using Google play or location services.

Fakhar
  • 3,946
  • 39
  • 35
0

I was faced this same error while running application. I am just rebuild the program and run again the application..

Dev Sagar
  • 1
  • 3
  • This does not really answer the question. If you have a different question, you can ask it by clicking [Ask Question](https://stackoverflow.com/questions/ask). To get notified when this question gets new answers, you can [follow this question](https://meta.stackexchange.com/q/345661). Once you have enough [reputation](https://stackoverflow.com/help/whats-reputation), you can also [add a bounty](https://stackoverflow.com/help/privileges/set-bounties) to draw more attention to this question. - [From Review](/review/late-answers/33463135) – JustSightseeing Dec 23 '22 at 02:07
-1

For me ı had this problem i fixed it because i did not use Android studio Emulator i was using another one i fixed the problem when I enabled Developer Mode from Emulator and that is all for
I hope that can help some one like me
Regards

-1

As I am currently using IntelliJ IDEA 2021, In order to work for me, I had to disconnect android device(Emulator) to Computer by USB and Free up some space on phone storage Lastly It was to refresh my device by restarting it(phone)

Again, I had to go to:

Settings, Debugger, And Check Hide debug Window on process termination

I hope this helps, if U are using IntelliJ IDEA, for instance.

Gadrawin
  • 87
  • 1
  • 7
-1

You might wana check your phone storage too. Your apk wouldn't install if there is no space

  • 1
    This has already been mentioned in several other answers. *When answering older questions that already have answers, please make sure you provide either a novel solution or a significantly better explanation than existing answers.* – Eric Aya Oct 03 '21 at 11:26
-1

I resolved the problem by switching off the emulator, clean the project and rebuild it again.

Ramya Bm
  • 27
  • 2
-1

Its because the devie on which you want to install the app does not have enough space, just clear some items to get space. Then try agian