
My Google Play Account Got Banned, So I Opened a New One
The day my account got banned, my first reaction was the same as yours: register another one.

The day my account got banned, my first reaction was the same as yours: register another one.

Someone asked me again last week what to do about a rejected Play developer account. Going through his materials: ID photographed, card linked, the $25 charged successfully. The problem was the address — his card’s billing address was the office, the address on his ID was his hometown.

Chinese tutorials on Play developer accounts mostly stopped updating two years ago: $25, a credit card, an address, wait a day. That is no longer enough.

You have an agent write some Kotlin. It says it’s done. Now what?

By the time a cross-platform project reaches release, there is usually more than one distribution path. One through Google Play, one straight from your own site, and sometimes a test build for the QA folks. Android’s developer verification reprices the entry cost of each path, and the three bills are not calculated the same way at all.

If you have friends in Brazil, Indonesia, Singapore or Thailand, after September 30 they may run into something new: tap install in some app store, get a prompt saying the developer isn’t verified, and it won’t install. At the same moment, the China-market Android phone in your hand installs anything with no change at all.
Flutter 1.7.8 stable is out, fixing a batch of bugs.