Getting Started with APKTester

Pass Google Play's 14-day closed testing requirement in 3 steps. Real Android devices, fully automated.

On this page How it works 3 steps to start FAQ Troubleshooting

How it works

We run your closed testing on 12 real Android devices for the full 14 days. You give us your opt-in link, we handle the rest:

  • ✅ 12 dedicated Gmail accounts opt-in to your test
  • ✅ Real daily engagement sessions per device, timed naturally throughout the day
  • ✅ Full 14-day engagement period — Google's exact requirement
  • ✅ Real-time progress updates in your dashboard

After 14 days, you'll be eligible to apply for production access in Play Console.

3 Steps to Start Testing

1 Add 12 testers to your closed track

After signing up, you'll receive a CSV file with 12 verified Gmail addresses. Download it from your dashboard:

APKTester upload page with the Download CSV (12 emails) button

Then in Google Play Console:

  1. Open Play Console → select your app
  2. Navigate to Testing → Closed testing
  3. Click Manage track on your existing track (or create one)
  4. Open the Testers tab
  5. Click Create email list
  6. Give it a name (e.g. "APKTester")
  7. Click Upload CSV file and select the file you downloaded
  8. Click Save changes
Closed testing channel with the latest release Play Console Testers tab with an email list selected
⚠️ Critical step — don't skip this. On the same page, open the Countries / regions tab and add Turkey. Our 12 test devices are physically located in Turkey — if Turkey isn't on this list, our devices will see "This item isn't available in your country" and cannot install your app, no matter how correct your opt-in link is. This single missing checkbox is the most common reason a test fails to start.
Countries/regions tab with Turkey targeted
⚠️ Important: Google requires the CSV to be UTF-8 (without BOM). Our CSV is already in the correct format — don't open and re-save it in Excel (Excel adds BOM by default and Play Console will reject it).

2 Get your opt-in link

Once your closed testing release is approved by Google (typically 24–72 hours for new accounts), get the opt-in link:

  1. Go back to Closed testing → Manage track
  2. Open the Testers tab
  3. Scroll down to "How testers join your test"
  4. Under "Join on Android", click the Copy link button (we only use the Android link, not the web one)
How testers join your test — Android and web join links

The Android link will look like this:

https://play.google.com/store/apps/details?id=com.your.app.package
✅ Tip: Click your own opt-in link before pasting it into APKTester. Make sure the page loads correctly and shows your app name. If you see "App not available", your release isn't approved yet — wait a few hours and retry.

3 Submit & wait

Back in APKTester:

  1. Paste the opt-in link in the upload form
  2. Confirm you've added the 12 testers from our CSV
  3. Click Upload & Start Test
  4. Pay (or use a test credit if you have one)
APKTester upload form with the opt-in link field

Typically within 6 hours, our 12 devices opt-in via a natural rolling-start pattern.

Then daily testing runs for 14 days, with real engagement sessions per device. You'll see real-time progress in your dashboard.

After 14 days

Once the 14-day period completes, you'll have satisfied Google's testing duration requirement. To request production access:

  1. Open Play Console → Dashboard
  2. Click Apply for Production
  3. Submit your request

Google reviews production applications independently — review time and outcome depend on your app, content, and policy compliance, and decisions are made solely by Google.

FAQ

When you configure your Closed Testing channel in Google Play Console, make sure the country your test devices are in is added to the channel's Countries / regions list.

If you test with devices in Turkey, Turkey must be selected in the channel's country list. Otherwise, when a device opens your app in the Play Store it will see "This item isn't available in your country" and cannot download the test build.

Path: Play Console → Test and release → Closed testing → your channel → Countries / regions → add country → Save.

After adding a country it can take a few minutes to a few hours to propagate. If the warning doesn't clear right away, clear the Play Store cache on the device and try again.
We install your test build on each device with that device's own Google account, directly through the official Google Play Store app. This is the standard closed testing method Google recommends: a real device, a real account, an official store install — so your testing data accrues fully in line with Google's criteria.
Usually within 6 hours of submitting. We use a rolling-start pattern (15–60 second gaps between devices) so opt-ins look natural rather than synchronized.
Wait until your release shows "Available" in Play Console before submitting. Otherwise our devices will see "App not available" and the opt-in will fail.
Yes. Your dashboard shows real-time opt-in status, daily test counts, completion percentage, and full logs for every device.
Real physical devices. We use 12 Samsung Galaxy A26 5G phones, each with its own Gmail account and unique hardware fingerprint. Emulators are detected by Google and don't count toward the 14-day requirement.
For your own developer account: doesn't matter — Google approves new individual accounts. For our tester accounts: we use dedicated tester accounts on real devices.
If we can't successfully opt-in your testers, you're eligible for a refund. Once testing has started, refunds aren't possible (device time has been allocated). See our refund policy for full details.
No. We satisfy Google's 14-day testing requirement, which is one of several criteria Google reviews. Final approval depends on your app's content, policies, and Google's discretion.
Yes, you can run multiple tests sequentially. Concurrent testing across multiple apps is on our roadmap for the Agency plan.

Troubleshooting

My CSV won't upload to Play Console

Play Console only accepts UTF-8 CSV without BOM. Don't open the file in Excel — it adds BOM. Use a plain text editor or download fresh from APKTester.

"App not available" appears on the opt-in page

Your release hasn't been approved yet. Wait until Play Console shows "Available" for the closed testing track, then submit to APKTester.

Some devices showed opt-in failure

We retry failed devices automatically. If too many devices fail, you'll be eligible for a refund — see our refund policy for details.

Test progress seems stalled

Daily tests run at 09:00, 14:00, and 20:00 (Istanbul time). Check your dashboard after these slots. If nothing has run for 24 hours, contact us.

I haven't received my CSV

Make sure you've completed signup and are logged in. The CSV download button appears in the upload form.

Ready to start your 14-day test?

Sign Up