ADB Install Fails With INSTALL_FAILED_TEST_ONLY
AndroidInstallationApkAdbAndroid Problem Overview
I am having issues installing an apk to my device.
adb install <.apk>
Using the above command returns the following:
5413 KB/s (99747 bytes in 0.017s)
pkg: /data/local/tmp/AppClient.TestOnly.App3.apk
Failure [INSTALL_FAILED_TEST_ONLY]
Any idea on what might cause this issue?
It definitely recognizes the device. Could it be an issue with the apk?
Android Solutions
Solution 1 - Android
Looks like you need to modify your AndroidManifest.xml
Change android:testOnly="true"
to android:testOnly="false"
or remove this attribute.
If you want to keep the attribute android:testOnly
as true
you can use pm install
command with -t
option, but you may need to push
the apk to device first.
$ adb push bin/hello.apk /tmp/
5210 KB/s (825660 bytes in 0.154s)
$ adb shell pm install /tmp/hello.apk
pkg: /tmp/hello.apk
Failure [INSTALL_FAILED_TEST_ONLY]
$ adb shell pm install -t /tmp/hello.apk
pkg: /tmp/hello.apk
Success
I was able to reproduce the same issue and the above solved it.
If your APK is outside the device (on your desktop), then below command would do it:
$ adb install -t hello.apk
Solution 2 - Android
I had a similar problem with Android Studio 3.0.0 Beta 7
and could not publish anymore to the play store.
As stated here: https://developer.android.com/studio/run/index.html
> Note: The Run button builds an APK with testOnly="true", which means > the APK can only be installed via adb (which Android Studio uses). If > you want a debuggable APK that people can install without adb, select > your debug variant and click Build > Build APK(s).
Same goes for release build, with Android Studio 3
you need to go to Build > Build APK(s)
to have a non testable release apk that you can submit to the store.
Solution 3 - Android
Add -t
install flag, as on the screenshot below:
Solution 4 - Android
In my case this mistake was in unstable gradle version. Just use a stable version of gradle (not alpha, not even beta). And it was fixed for me
Solution 5 - Android
After searching and browsing all day, the only one works is adding
android.injected.testOnly=false
to the gradle.properties file
Solution 6 - Android
I agree with Elisey. I got this same error after opening my project in the 2.4 preview and then opening the same project in android studio 2.3
Fixed the issue by changing this line in build.gradle from
classpath 'com.android.tools.build:gradle:2.4.0-alpha5'
to
classpath 'com.android.tools.build:gradle:2.3.1'
Solution 7 - Android
None of the previous post solve my issue. Here is what's happening with me:
I normally load the app from android studio by clicking on the "Run" button. When you do this, android would create an app that's good for debug but not for install. If you try to install using:
adb install -r yourapk
you will get a message that says:
Failure [INSTALL_FAILED_TEST_ONLY]
When this happens, you will need to rebuilt the apk by first clean the build, then select Build->Build APK. See the image bellow:
This APK is ready to be installed either through adb install command or any other methods
Hope this helps
David
Solution 8 - Android
Android studio 3.0 generates test only APK.
I have solved the issue by adding the "android:testOnly" property to android manifest's
<application
.....
android:testOnly="false"
android:theme="@style/AppTheme">
And then generated the APK by Android studio3.0 menu:Build-->Build APK(s).
More Info: https://commonsware.com/blog/2017/10/31/android-studio-3p0-flag-test-only.html
Solution 9 - Android
add this line to your ‘gradle.properties’
android.injected.testOnly=false
Solution 10 - Android
If you want to test the apk, just add the -t
command line option.
Example command:
adb install -t .\app-debug.apk
Solution 11 - Android
In my case was by uploading an APK, that although it was signed with production certificate and was a release variant, was generated by the run play button from Android studio. Problem solved after generating APK from Gradle or from Build APK menu option.
Solution 12 - Android
Solution 13 - Android
I see the accepted answer but you dont have to actually push the apk and then run the command on adb shell direct adb install with -t flag actually works
> adb install -t "path to apk in ur computer"
Solution 14 - Android
In my case, using Android Studio 4.0, the below solved the issue;
Add to 'gradle.properties' file;
android.injected.testOnly=false
Solution 15 - Android
The easiest to solve this, without reverting to an older gradle version is to add the '-t' option in the run configurations (for pm install).
testOnly='false' had no effect whatsoever. The error is caused by the alpha version of gradle plugin that makes debug APK 'for test only purposes'. The -t option allows such APK to be installed. Setting it in run configuration makes it automatically install you APK as usual.
Solution 16 - Android
this works for me adb install -t myapk.apk
Solution 17 - Android
I don't know if it's gonna be useful for anyone or not, but I got this error message, when I accidentally tried to build and install my project with test gradle plugin ('gradle:2.4.0-alpha5'
) version in stable Android Studio version (2.3
, not in 2.4 preview 5
version I'd downloaded and installed before).
When I realized my mistake, I launched preview Android Studio version and it built and installed my project without any problem.
Solution 18 - Android
My finding is as below. If I compile using the Android Studio UI, and the APK generated, I can't just
adb install <xxx.apk>
It will generate Failure [INSTALL_FAILED_TEST_ONLY]
I need to compile it using the gradle i.e. ./gradlew app:assembleRelease
. Then only the generated apk, then it can only be installed.
This is because the Android Studio UI Compile, only generate test apk for a particular device, while ./gradlew app:assembleRelease
command is the actual apk generation to be installed on all device (and upload to playstore)
Solution 19 - Android
As mentioned in documentation: > Android Studio automatically adds this attribute when you click Run
So, to be able to install your apk with adb install <path to apk file>
you need to assemble build from terminal: ./gradlew assembleDebug
and install with adb. Or just run ./gradlew installDebug
to build and install on the device simultaneously.
Solution 20 - Android
Build your distribution .apk from Android Studio as follow
Build --> Build Apk(s) (for unsigned build) Build --> Generate Signed APK ( for signed build)
These option builds the APK with android:testOnly="false" option which allows you to install the APK expicitly into device by the commond.
adb install yourBuilT.apk
Solution 21 - Android
What worked for me is performing Refresh all Gradle projects
from the Gradle
toolbar from the right menu.
PFB the screenshot from Android Studio.
- Select
Gradle
toolbar from the right menu. - Select the
Refresh
icon
This resolved the issue for me.
Solution 22 - Android
Although I am sure Saurabh's answer will work for most other people, I did want to identify the extra steps I had to take in order to get my apk installed.
I tried pushing to the device with the following result:
? adb push AppClient.TestOnly.App3.apk \tmp\
failed to copy 'AppClient.TestOnly.App3.apk' to '\tmp\': Read-only file system
After looking around to change the filesystem RW permissions I ended up executing the following commands:
? adb shell
255|shell@android:/ $ su
shell@android:/ # mount -o remount,rw /
mount -o remount,rw /
I got this when I tried to push again:
? adb push AppClient.TestOnly.App3.apk /tmp
failed to copy 'AppClient.TestOnly.App3.apk' to '/tmp': Permission denied
I was able to push to the sdcard:
? adb push AppClient.TestOnly.App3.apk /sdcard/
3178 KB/s (99747 bytes in 0.030s)
At which point I was able to execute Saurabh's command:
shell@android:/ # pm install -t /sdcard/AppClient.TestOnly.App3.apk
pm install -t /sdcard/AppClient.TestOnly.App3.apk
pkg: /sdcard/AppClient.TestOnly.App3.apk
Success
Solution 23 - Android
For me it has worked execute the gradle task 'clean' (under :app, at Gradle pane, usually located at the right) and run again the project.
Solution 24 - Android
I tried external project, with multiple apk.
The command from Studio, looked like
adb install-multiple -r ....
Solution -
- select console
- aste command with
-t
Solution 25 - Android
If you are looking for a less permanent solution then adding android.injected.testOnly=false
to your gradle.properties file and you don't mind using the command line then the following two commands before installation will do:
rm -v **/build/**/AndroidManifest.xml
gradle build
For Windows users: delete all AndroidManifest.xml from all build directories. But not from the src directories so DEL /S
is not the best idea.
Solution 26 - Android
I got the same issue and no answer helps. At last, I find there's still an install in my Safe Folder(Or Secure folder depending phone brands), which had not been removed when Android uninstalled the ordinary install. Remove it and this issue fixed. Hope this can help some guys else!
Solution 27 - Android
first remove the unstable version:
adb uninstall
problematic-package-name
; and then reinstall the apk.