Urgent.News

What's breaking now, across thousands of outlets.

Tech

Closed Testing on Google Play: A Step-by-Step Setup Guide for 2026

Short answer: closed testing on Google Play lets you release a build to a group of testers you control, through Play Console's closed track. You set it up after completing app setup, add testers by email list or Google Group, and share an opt-in link. For new personal accounts it is also the required step before production. Here's the setup, end to end. Before you start: finish app setup Google's…

Closed testing on Google Play allows developers to release a build to a group of testers they select directly through the Play Console's closed track. To set this up, developers must first complete the app setup process in Google Play Console, which includes tasks such as app access declaration, ads declaration, content rating, target audience definition, and data safety.

After completing these steps, developers can create a closed track in the Test and release section of Play Console, either using a default track or creating a new one with a recognizable name.

Testers can be added in two ways: through email lists for small, known groups or Google Groups for groups that may have members joining and leaving. Once testers are added, developers upload their app bundle, add release notes, and roll out the build to the closed track, ensuring the release is available in countries where testers reside.

After the rollout, an opt-in link is generated, which testers must open while signed in with their Google account to install the app from Play Store. Testers are required to send a screenshot of their opt-in confirmation, allowing developers to log the date and track their participation.

For closed testing to be required, the developer's account must have been created after November 13, 2023. The closed testing requirement specifies that at least 12 testers must be opted in continuously for a minimum of 14 days before production access can be applied for. During this testing period, developers must run tests similar to a production environment, collecting feedback on app functionality, identifying bugs, and making necessary updates to the app.

Upon successful completion of the closed test and meeting the requirement, developers can apply for production access by filling out three sections in Play Console: About your closed test, About your app/game, and About your production readiness. Review typically takes seven days or less, but can be longer if there are issues.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

New Lovable app shows 404 on every page on Vercel

Lovable projects made since May 2026 use TanStack Start, which renders pages on a server. Built for Cloudflare Workers, they 404 on Vercel until they're built with Nitro.

  • Lovable apps use TanStack Start for server-generated pages on Cloudflare Workers.
  • Vercel fails to run apps built for Cloudflare Workers, causing 404 errors.
  • Developers must modify package.json and use Nitro for Vercel compatibility.

A practical browser checklist for testing small transparent images

Small icons and emotes often look fine in a design file but lose detail on a busy page. A useful test is to review the exported asset at its final display size, on both light and dark surfaces, before…

  • Keep original artwork separate from exported version to avoid unintended resizing
  • Export PNG with clear, descriptive filename like wave-32.png and verify size restrictions
  • Display against contrasting backgrounds (white, dark, mid-tone) to spot halos and lost details

More from Wednesday 28 October →