Once your Android app has been active for a while and there have been no updates (new builds), you might receive an email notification from Google with the message:
⚠️ Google Warning: “Your Developer Account is at Risk of Being Closed Because it's not being used"
If you’ve received a notification from Google warning that your Google Play Developer account is at risk of closure due to inactivity, this article explains what it means and what action you need to take.
Why You Received This Warning
Google Play closes developer accounts that it considers inactive. Developer accounts that are considered inactive may be closed without a refund of the registration fee.
There are two sets of criteria that can cause a developer account to be flagged as inactive:
Inactive Account Without Any Apps
Your account may be marked as inactive if:
It was created over a year ago
You have never submitted an app for review
Inactive Account With Apps
Even if your account has apps, it may still be flagged as inactive if:
The account was created more than a year ago, and
All apps (live, removed, or suspended) have fewer than 1,000 combined lifetime installs, and
Your Play Developer account phone number and contact email are not verified, and
You have not used Play Console in the last 180 days
What Happens Next
If your account is flagged:
You will receive an email notification from Google with a warning and a deadline
You’ll see a message in Play Console indicating your account is at risk
Reminder emails will be sent at 60, 30, and 7 days before the deadline
If no action is taken by the specified date, your developer account will be closed permanently.
How to Keep Your Developer Account Active
To avoid account closure, Google requires you to do two things: verify your contact details in Play Console, and publish an app update, which you can do by submitting a new Android app build from your SupaPass dashboard.
Follow these steps:
Log in to your SupaPass Dashboard
Go to Design > App > App Setup
Click Build app
Choose Android
A pop-up screen will appear
Select “Yes, submit this build to the Play Store for review”
In the “What’s New” notes field, write:
Minor fixes and updatesClick “Build & Submit for Review”
This will create a new version of your Android app and submit it to the Google Play Store. This action shows Google that your developer account is active and publishing apps.
Important Notes
Updating your content doesn't count as an app update. Google only sees a new app build as a valid way of showing your app is active.
Verify both your phone number and contact email in Play Console under Account details. Google requires this as well as the new build.
Need Help?
If you have questions or need assistance submitting your app build, just reach out via chat 💬 on your SupaPass Dashboard. We’re happy to help.
Frequently Asked Questions
Still have questions? Check the answers below, or start a chat with our team 💬
Why did Google send me this warning?
Why did Google send me this warning?
Google flags accounts over a year old that have never submitted an app, or whose apps have fewer than 1,000 combined lifetime installs, unverified contact details and no Play Console use in the last 180 days.
What exactly do I need to do?
What exactly do I need to do?
Verify your phone number and contact email in Play Console, and publish an app update by submitting a new Android build from your SupaPass dashboard. Google requires both.
How long do I have?
How long do I have?
Google's email gives you a deadline, and sends reminders 60, 30 and 7 days before it.
What happens if I miss the deadline?
What happens if I miss the deadline?
Google closes the account and does not refund the registration fee.
Does adding new content to my app count?
Does adding new content to my app count?
No. Google needs to see a published app update, so you'll need to submit a new Android build.
Can this happen again?
Can this happen again?
Yes. An account can become inactive again later, and Google will send a new notification if it does.


