<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: 12testers14day.com</title>
    <description>The latest articles on DEV Community by 12testers14day.com (@sundarclosedtests).</description>
    <link>https://dev.to/sundarclosedtests</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4197849%2F8b64ec5c-cd36-4052-8a6d-a2dc72747008.png</url>
      <title>DEV Community: 12testers14day.com</title>
      <link>https://dev.to/sundarclosedtests</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sundarclosedtests"/>
    <language>en</language>
    <item>
      <title>"Not Available in Your Country" During a Google Play Closed Test: What I Check</title>
      <dc:creator>12testers14day.com</dc:creator>
      <pubDate>Tue, 27 Oct 2026 10:30:10 +0000</pubDate>
      <link>https://dev.to/sundarclosedtests/not-available-in-your-country-during-a-google-play-closed-test-what-i-check-2bi8</link>
      <guid>https://dev.to/sundarclosedtests/not-available-in-your-country-during-a-google-play-closed-test-what-i-check-2bi8</guid>
      <description>&lt;p&gt;A tester messaged me on day two of a closed test: the opt-in link worked, they tapped "Become a tester", and then the Play Store page said the app wasn't available in their country. Everyone else on the list could install it.&lt;/p&gt;

&lt;p&gt;The cause wasn't the build or the tester list. It was the countries setting on the closed track itself. Here's how I track this one down now, because a tester who can't install is a tester who probably won't stay opted in long enough to help with the 12 testers for 14 days requirement.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Closed tracks have their own country list
&lt;/h2&gt;

&lt;p&gt;This is the part that catches people. Each testing track in Play Console has its own countries/regions setting, separate from what you plan for production. Open &lt;strong&gt;Testing &amp;gt; Closed testing&lt;/strong&gt;, pick the track your testers joined, and look at the &lt;strong&gt;Countries / regions&lt;/strong&gt; tab.&lt;/p&gt;

&lt;p&gt;If you created the track quickly and only ticked your own country, anyone whose Play Store is set to another country can opt in through the link but can't install. Add the countries your testers are actually in, save, and give it a little time before asking them to retry.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. The tester's Play Store country is not where they're sitting
&lt;/h2&gt;

&lt;p&gt;Google Play decides a user's country from their Play account, mostly from their payments profile, not from their current location or VPN. A tester who moved, or set up their account while travelling, can show up as a different country than you expect.&lt;/p&gt;

&lt;p&gt;I ask the tester to open the Play Store, go to &lt;strong&gt;Settings &amp;gt; General &amp;gt; Account and device preferences&lt;/strong&gt; and read the country listed there. That one answer usually settles it. I don't ask testers to change their country, because Google limits how often that can be done and it affects their whole account.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Device compatibility can look like a country problem
&lt;/h2&gt;

&lt;p&gt;Sometimes the message is really "your device isn't compatible", and testers report it loosely as "not available". Before touching countries, I check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;minSdk&lt;/code&gt; against the tester's Android version&lt;/li&gt;
&lt;li&gt;required hardware features in the manifest (camera, NFC, telephony) that a tablet or older phone may lack&lt;/li&gt;
&lt;li&gt;the &lt;strong&gt;Device catalog&lt;/strong&gt; in Play Console, in case a device was excluded&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1z6fv3t0lhser20kj88x.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1z6fv3t0lhser20kj88x.png" alt="Example checklist for testers who see not available in your country" width="799" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Check the release actually reached the track
&lt;/h2&gt;

&lt;p&gt;If the latest closed release is still in review or was never rolled out to that track, testers can see odd Play Store states. I confirm the release shows as available on the same closed track the opt-in link belongs to before I start adding countries.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Re-test with the opt-in link, not a search
&lt;/h2&gt;

&lt;p&gt;Closed test apps usually don't show up in Play Store search. After fixing the countries list, I ask the tester to open the opt-in link again on the phone signed in with the invited Google account, then tap through to the store listing from there.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I keep in mind about the 14 days
&lt;/h2&gt;

&lt;p&gt;Fixing availability doesn't backfill the days a tester couldn't install. If someone joins late, I count their 14 continuous days from when they're actually opted in and able to use the app, and I plan the test with a couple of extra testers and a couple of spare days so one country mix-up doesn't push the whole timeline. If you want to sanity-check the setup before inviting anyone, I keep a short run-through of how a closed test is put together on the &lt;a href="https://www.12testers14day.com/google-play-closed-testing" rel="noopener noreferrer"&gt;Google Play closed testing guide&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Production access is still Google's call after the test, so none of this is a shortcut. It just removes one avoidable reason testers drop off in the first week.&lt;/p&gt;

</description>
      <category>android</category>
      <category>googleplay</category>
      <category>mobile</category>
      <category>testing</category>
    </item>
    <item>
      <title>Six Build Checks I Run Before Every Google Play Closed Test</title>
      <dc:creator>12testers14day.com</dc:creator>
      <pubDate>Wed, 21 Oct 2026 08:44:35 +0000</pubDate>
      <link>https://dev.to/sundarclosedtests/six-build-checks-i-run-before-every-google-play-closed-test-438b</link>
      <guid>https://dev.to/sundarclosedtests/six-build-checks-i-run-before-every-google-play-closed-test-438b</guid>
      <description>&lt;p&gt;Most closed-test problems I get asked about aren't tester problems. They're build problems that look like tester problems. A tester says "it won't install" or "there's no update", and the real cause is a versionCode, a signing key, or a minSdk that quietly shut them out.&lt;/p&gt;

&lt;p&gt;So before I upload anything to a Google Play closed track, I run the same short check. Here it is, with the reasoning.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjowcv6hn8s0yk5hjh9io.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjowcv6hn8s0yk5hjh9io.png" alt="Six build checks before a Google Play closed test" width="799" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Bump the versionCode, every time
&lt;/h2&gt;

&lt;p&gt;Play Console won't accept a bundle whose &lt;code&gt;versionCode&lt;/code&gt; has already been used for that app, and testers only get an update when the new code is higher than what they have installed.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight kotlin"&gt;&lt;code&gt;&lt;span class="c1"&gt;// app/build.gradle.kts&lt;/span&gt;
&lt;span class="nf"&gt;android&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nf"&gt;defaultConfig&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="n"&gt;versionCode&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;14&lt;/span&gt;        &lt;span class="c1"&gt;// must be higher than the last upload&lt;/span&gt;
        &lt;span class="n"&gt;versionName&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s"&gt;"1.0.3"&lt;/span&gt;   &lt;span class="c1"&gt;// what testers see&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If you build in CI, derive it from something that only goes up (a build number), not from the date string you might reuse.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Upload an App Bundle signed with your upload key
&lt;/h2&gt;

&lt;p&gt;New apps go to Play as an Android App Bundle (&lt;code&gt;.aab&lt;/code&gt;), and with Play App Signing Google re-signs what testers download. What you sign with is your &lt;strong&gt;upload key&lt;/strong&gt;. Two things I check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The release build is signed with the upload key registered in Play Console, not a debug key.&lt;/li&gt;
&lt;li&gt;The build isn't &lt;code&gt;debuggable&lt;/code&gt;. Play rejects debuggable bundles.
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;./gradlew bundleRelease
&lt;span class="c"&gt;# then confirm which certificate signed it&lt;/span&gt;
keytool &lt;span class="nt"&gt;-printcert&lt;/span&gt; &lt;span class="nt"&gt;-jarfile&lt;/span&gt; app/build/outputs/bundle/release/app-release.aab
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  3. Don't mix sideloaded builds with the Play build
&lt;/h2&gt;

&lt;p&gt;This one causes a lot of "App not installed" messages. If a tester sideloaded an APK you signed yourself (debug or a local release key), the Play-signed build has a different signature. Android won't install one over the other.&lt;/p&gt;

&lt;p&gt;The fix is boring: ask that tester to uninstall the sideloaded copy, then install from the Play Store link on the opt-in page. Uninstalling the app is fine. Tapping "Leave the program" is the thing to avoid.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6plhzzasji6yluu1dahb.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6plhzzasji6yluu1dahb.png" alt="Example: common build-side reasons a closed tester can't install" width="799" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Check minSdk and device filters against your testers' phones
&lt;/h2&gt;

&lt;p&gt;A high &lt;code&gt;minSdk&lt;/code&gt;, a required hardware feature in the manifest, or a narrow ABI list can make the app "not compatible" with a tester's device. In Play Console, the device catalog for your app shows which devices your current bundle supports. I look there before blaming the tester.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight xml"&gt;&lt;code&gt;&lt;span class="c"&gt;&amp;lt;!-- make optional hardware optional, or some phones get filtered out --&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;uses-feature&lt;/span&gt; &lt;span class="na"&gt;android:name=&lt;/span&gt;&lt;span class="s"&gt;"android.hardware.camera"&lt;/span&gt; &lt;span class="na"&gt;android:required=&lt;/span&gt;&lt;span class="s"&gt;"false"&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  5. Meet the current target API level
&lt;/h2&gt;

&lt;p&gt;Play sets a minimum &lt;code&gt;targetSdk&lt;/code&gt; for new apps and updates, and it moves up roughly once a year. I check the current number in Play Console Help before each first upload instead of trusting memory, because a bundle below it gets blocked at upload time.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Send the release to review and confirm it's live on the closed track
&lt;/h2&gt;

&lt;p&gt;Uploading isn't publishing. After I roll out to the closed track, I check the Publishing overview so the change actually goes to review, then wait for the track to show the release as available before I send testers the opt-in link.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this doesn't fix
&lt;/h2&gt;

&lt;p&gt;None of this gets you production access by itself. For newer personal developer accounts, Google still wants at least 12 testers opted in for 14 continuous days on a closed track, and it reviews the production access application on its own terms. A clean build just means the testers you invite can actually install and stay in.&lt;/p&gt;

&lt;p&gt;I keep the full pre-launch list, including the tester side, as a free &lt;a href="https://www.12testers14day.com/tools/google-play-closed-testing-checklist" rel="noopener noreferrer"&gt;Google Play closed testing checklist&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Once the build clears those six checks, &lt;a href="https://www.12testers14day.com/pricing" rel="noopener noreferrer"&gt;12testers14day.com&lt;/a&gt; puts 14 testers on it for 16 days from $15. See the plans.&lt;/p&gt;

</description>
      <category>android</category>
      <category>googleplay</category>
      <category>mobile</category>
      <category>testing</category>
    </item>
  </channel>
</rss>
