Skip to content
webtoapkfree

How do I test an APK on my phone before publishing?

To test an APK on your phone, install the signed release build by file transfer, adb or a Play internal test, then check the flows a WebView app breaks.

GuidesNookesh Karri

Light cover card with the title 'How do I test an APK on my phone before publishing?' in dark text and a green accent bar

To test an APK on your phone, copy the signed release APK to the device, allow installs from that source under Install unknown apps, and tap the file. For repeated installs, use adb install over USB. To reach other testers, use a Google Play internal test. Then walk through the flows real users will hit, not only the home screen.

Why test the release APK on a real phone

The build you test should be the build you ship. Android’s publishing guide says to “thoroughly test the release version on at least one target handset device and one target tablet device” before you distribute it.

The hardware device guide is blunter: “Always test your Android app on a real device before releasing it to users.” Emulators miss things like a weak mobile signal, a manufacturer’s file picker and the real back gesture.

Four ways to get the APK onto your phone

Which route you pick depends on how often you reinstall and who else needs the build.

Method Needs Best for Watch out for
Copy the file and tap it A file manager or browser A quick check by yourself Install unknown apps permission
adb install USB cable or Wi-Fi, developer options Reinstalling many builds One-time setup on the phone
Play internal app sharing Play Console account Sharing a build by link Builds are re-signed by Google
Play internal testing track Play Console account, an AAB Testing the real store install Testers are added by email

My take: start with a direct install, and move to a Play testing track only once the app works for you. Store tracks add a review of steps you don’t need while you’re still fixing bugs.

How to test an APK on your phone by direct install

A direct install takes three steps: move the file, allow the source, and tap the APK.

  1. Move the APK to the phone. Email it to yourself, put it in cloud storage or copy it over USB. The guide to sharing an APK from a website covers hosting the file for download.
  2. Allow the source. The publishing guide says that on “Android 8.0 (API level 26) and higher, users must navigate to the Install unknown apps system settings screen” for that source. Allow it for the app you used to open the file, such as Files or Chrome. On Android 7.1.1 (API level 25) and lower there is a single Unknown sources setting instead.
  3. Tap the APK and install. If an older build with the same package name is on the phone, uninstall it first when the install fails.

If Android shows “App not installed,” the cause is usually a signature or version conflict. The post on the App not installed error lists the fixes.

How to install the APK with adb

adb installs from your computer in one command, which is faster when you rebuild often. First, turn on developer options: the developer options page says to “tap the Build Number option seven times.”

Then enable USB debugging under Developer options and plug in the phone. The device guide says the phone “shows a dialog asking whether to accept an RSA key,” so accept it. Now run:

adb devices
adb install app-release.apk

The adb reference notes that with only one device connected, commands go to it by default. With several, add -s and the serial number. On Android 11 and higher, wireless debugging lets you pair with adb pair ipaddr:port and skip the cable.

How to test with Google Play before publishing

Play’s two testing tools put the app on phones through the Play Store, which is closer to what users will get. Both need a Play Console developer account.

Internal app sharing gives you a download link. Google’s internal sharing help page says “a maximum of 100 users will be able to download your app using the link.” Testers must turn on internal app sharing in their Play Store app first, and links expire 60 days after upload.

One catch: builds uploaded there are “automatically re-signed with an Internal App Sharing key.” That build has a different signature from the APK you sideloaded, so expect to uninstall one before installing the other.

The internal testing track uses your real AAB. Google’s testing tracks page says “an internal test can have up to 100 testers per app,” and recommends starting there before closed testing. New personal accounts face extra rules, covered in Google Play’s tester rule for new accounts.

What to check in a WebView app before publishing

A WebView app can install fine and still fail on the parts a browser normally handles. Run through this list on the phone, with the release build.

  • Sign-in. Log in and log out. Google sign-in in particular often behaves differently inside a WebView.
  • Links. Tap a link to another domain, a mailto: link and a phone number.
  • Uploads and downloads. Attach a photo in a form, then download a PDF or invoice.
  • Back gesture. Go three pages deep and press back. It should step back through pages, not close the app.
  • No connection. Turn on airplane mode and open the app. Check what users see.
  • Permissions. Try anything that asks for the camera, microphone or location.

If you built with WebToAPK Free, the builder gives you a signed APK to install and test on a device, plus an AAB for the store. Generated apps need Android 8.0 or newer, so an older test phone won’t install them. The site also says it can’t promise every website works in a WebView: sign-in, downloads, permissions and external links can behave differently than in Chrome.

Limits of testing on your own phone

One phone tells you the app runs, not that it runs everywhere. Your device has one screen size, one Android version and one manufacturer’s quirks, which is why Google’s guide asks for a handset and a tablet at minimum.

A direct install also skips Play’s own install path. Before you submit, confirm whether the store wants an APK or an AAB; the APK vs AAB guide explains the difference.

FAQ

Can I test an APK without publishing it on Google Play?

Yes. Copy the APK to your phone and allow installs from that source, or install it from a computer with adb. Neither needs a Play Console account.

Why does my phone block the APK install?

On Android 8.0 and higher, each app that opens APK files needs permission in the Install unknown apps settings screen. Allow it for the file manager or browser you used, then tap the APK again.

How many people can test my app through Google Play?

An internal test can have up to 100 testers per app. An internal app sharing link also allows a maximum of 100 users, and you can upload again for a new link.

Should I test the debug build or the release build?

Test the release build. Android’s publishing guide says to test the release version on at least one handset and one tablet before you distribute the app.

Sources