APPSINITYSigning and releases
Internal testing
Internal testing is simply a project that is not published. Its value is that everything except visibility already works.
Open Appsinity StudioOn this pageRunning an internal testA device matrix worth havingThe internal checklistFrequently asked questions
Running an internal test
- Keep the status at
draft. Nothing is visible in the catalog, and the listing template answers This game is not available. - Complete the seven sections. Do it properly. The point of internal testing is to test the release path, not only the build.
- Upload and sign. Then download the signed APK from the build record rather than your local output — that file is what players receive.
- Install on a real device. Over an existing install if you have shipped before, to prove the upgrade works.
- Test the store surfaces. Temporarily publish, view every surface, then unpublish again.
Note: Short publish windows during internal test are visible to anyone who happens to be looking at the store. Do it outside peak hours if the listing already has an audience.
A device matrix worth having
The store's own compatibility text is generated from the visitor's user-agent and the listing's platform, so testing on a device also tests the message it receives.
| Target | Test on | Because |
|---|---|---|
| Android, low-end | An older phone with limited storage | Install failures come from space and ABI, not code |
| Android, high refresh | A recent flagship | Frame pacing bugs only appear at 120 Hz |
| Windows x64 | A plain Intel/AMD PC | The default the client offers first |
| Windows ARM64 | Snapdragon or Surface hardware | An x64-only build runs under emulation, slowly |
| Web | A phone browser and a laptop browser | The player frame and the rotate hint only show on one of them |
| Emulator | Anything — with care | An Android-only listing on a PC shows the Will not install note; the emulator is the documented workaround |
The internal checklist
- The download completes from the listing, not from your build folder.
- The Size row matches the file players actually receive.
- The gallery shows the right platform's art on a phone and on a PC.
- Data safety reads sensibly, because
N/11 collectedis public. - The buy panel says what you expect: Download Now, ▶ Open Now, Pre register, or Protected download - and ▶ Play in the desktop client, once that build is in the player's library.
- The desktop client unpacks the zip and creates a shortcut — the chip reads Ready - shortcut on your desktop.
- An 18+ rating produces the age gate you intended, and nothing else does.
Frequently asked questions
Is there an internal track or a tester group?
No. Draft status plus your own devices is the internal track.
Do internal tests pollute analytics?
Yes. Loads and downloads you make count in the same visit and download figures.
What is the most-skipped internal test?
Installing the signed output over a previous install. That is where signature and save-data problems appear.
Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]