ci

Two panels comparing what the Android Publisher API accepts before and after an app has been published once. Before: uploads, listings, images and draft releases all succeed, but a completed release returns 400 and country availability reads as zero countries. After: completed releases, staged rollouts and halts all succeed.

The Play Publisher API cannot make an app’s first release live — only draft releases exist until you publish once by hand

jerome / 30 août 2026

Uploading, listings and images all work on a never-published app. Setting a release to completed returns 400 until someone presses Publish in the Console.

Two processes open edits A then B on one app; the server drops A when B is created, so process 1's later read of A gets HTTP 400 'This Edit has been deleted' while process 2's read of B returns 200.

Android

Google Play’s edits.insert silently deletes the app’s previous open edit — two parallel API scripts fail with ‘This Edit has been deleted’

jerome / 30 août 2026

Two Play API clients on one app: the second edits.insert discards the first edit and every call on it returns HTTP 400. Serialize per package.

Sequence: a previous crash leaves a crash database in /tmp, the next start shows a consent dialog nobody answers, adb never sees a device; deleting the database restores a normal boot

Android

The Android emulator would not boot: a crash-consent dialog from the previous run was waiting for a click

jerome / 30 août 2026

adb devices stayed empty. The log said ‘Showing crashdialog to get consent’. Deleting /tmp/android-$USER/emu-crash-*.db fixed it.