Google Play error: cannot upload a test-only APK
Solution 1
Building your app through Android Studio 3.0 and later will add android:testOnly="true"
to your application manifest, marking the APK as FLAG_TEST_ONLY
for the PackageManager. More information on CommonsBlog here.
Attempting to install such an APK outside of Android Studio will fail with:
Failed to install app-debug.apk: Failure [INSTALL_FAILED_TEST_ONLY: installPackageLI]
Attempting to upload it to Google Play will also fail, with :
You cannot upload a test-only APK
There are four solutions to this:
Build from Android Studio
Simply select "Build APK(s)" from the "Build" menu in Android Studio.
Sign from Android Studio manually
Simply select "Generate Signed APK..." from the "Build" menu in Android Studio. Provide the keystore and enter the signing details in the dialog that displays.
Build through Gradle
You can of course simply execute Gradle from the terminal for some automation, for instance if your deployment cycle runs through CI (which I highly recommend!):
./gradlew assembleRelease
(Alternatively, you may prefer running this Gradle task from the Gradle pane from within Android Studio.)
Disable this feature in Android Studio
If you don't like this behavior, you may elect to add this flag to your gradle.properties
. Beware that the test flag is for your own protection, so you don't accidentally publish a test-only APK!
# Disble testOnly mode for Android Studio
android.injected.testOnly=false
Solution 2
Click on Build and then press BuildAPK(s) and then upload it will work. Instant run APK on android studio 3.0 runs only on the device attached to adb.
Solution 3
Looks like I found something very related: ADB Install Fails With INSTALL_FAILED_TEST_ONLY
I'm using 2.4.0-alpha6 of gradle plugin and that's seems to be far from ready to be used for production.
So the solution is to use the latest stable gradle plugin:
classpath 'com.android.tools.build:gradle:2.3.1'
Solution 4
I found this blog that addresses the cause of the "test-only" bug
https://commonsware.com/blog/2017/10/31/android-studio-3p0-flag-test-only.html
basically, there are two things to note about it:
You cannot install an app with android:testOnly="true" by conventional means, such as from an Android file manager or from a download off of a Web site
Android Studio 3.0 sets android:testOnly="true" on APKs that are run from the IDE
android studio 3.0 now sets this "testOnly" flag when you compile a release version using the green Run button (make project CTRL+F9).
The solution I found is to not call "make project", but to call either
- build > build APK or
- build > Generate Signed APK...
Solution 5
I am using Android Studio 3.1 Canary 5
What I had tried (but not worked):
- I tried all the answers as above,but Unfortunately I didn't get solution.
- I removed kotlin dependency and signed but doesn't worked.
- I tried use command line like
./gradlew assembleRelease
- I tried to build apk using "Build APK" and "Generate Signed APK"
After all the possibilities I got solution by following way:
- Compile SDK Version changed from Android P to Android Oreo 27
- Changed AppCompat Version to 27.0.1
and Its successfully working now.
Thank you.
![Vito Valov](https://i.stack.imgur.com/1soa9.jpg?s=256&g=1)
Vito Valov
Software Engineer focused on mobile development since 2013. Wide experience in implementation, design, testing, support and maintenance of applications from different sectors such as e-banking, medicine and home automation for mobile devices on Android and since 2017 also iOS native platforms. Active development of own apps that are being used by more than 100 000 users worldwide. Strong knowledge of Android SDK, Kotlin, Java, Coroutines, RxJava, Dagger, Clean, MVP, MVVM.
Updated on June 02, 2022Comments
-
Vito Valov about 2 years
When trying to upload the first apk to a recently created project in GooglePlay console, I receive this error:
You cannot upload a test-only APK
Searching Google gives me 0 results for that exact string as per today.
I also have submitted a ticket for Play Console. Will update here if have any answer.
UPDATE Nov 29th 2017
As @paul-lammertsma suggested, there's a workaround. Still would be good to know why we need to go gradle way and we cannot do it via IDE.
-
Parker almost 7 yearsIf you're on AS3 Canary, be sure to downgrade the gradle AND the plugin
-
Northern Captain almost 7 yearsIt worked for me with AS 3.0 beta2. Thanks Paul, you saved my day
-
droppin_science almost 7 years...or upgrade to
com.android.tools.build:gradle:3.0.0-beta2
;) -
vovahost over 6 yearsIt's true, if you build from Android Studio you'l get this error but works fine from the terminal. Just tested with Android Studio 3.0 beta 7, gradle-4.1, gradle plugin 3.0.0-beta7
-
mbonnin over 6 yearsSame thing with AS3 rc2
-
Uwe Post over 6 yearsThe workaround works for me, as even AS 3.0 produced an APK causing the error.
-
Vito Valov over 6 yearsAccepting your answer as a workaround but still not happy taking this as a solution. IMO Android Studio should work as expected and not cause this trouble..
-
Radu over 6 yearsGoogle "wants you".... kotlin, gradle 3....Why not just focus on making their tools work. Honestly I've had enough...
-
Pratik Butani over 6 yearsI didn't get solution, getting error while uploading on playstore.
-
user924 about 6 yearsSolution is much simpler you should use Build apks rather than apks which you build from run button
-
Rômulo Z. C. Cunha about 6 yearsAs the user924 said, to solve this, in Android Studio, just click Build-> Build APK (s), and then send the new generated apk
-
Vito Valov about 5 yearswhat you say is already the accepted answer for this question