How to fix: Your app is static and does not contain app-specific functionalities

Posted on 12. April 2026 by Jan Bunk


This Google Play rejection reason can have different causes. The screenshot attached to the rejection will show you which one it is.

Check the rejection screenshot first

The screenshot attached to the app rejection email contains important information to diagnose the cause of the rejection.

Instead of in the e-mail, you can also find the screenshot in the policy center of the Google Play Console.

A screenshot of the view issue button in the policy center.

You'll be able to see the screenshot showing the issue on the detail page. This is the best clue for figuring out the exact rejection reason.

A screenshot of the issue screenshot in the policy center.

The app was disabled

The most common cause of this rejection is that your webtoapp.design subscription expired during the review. In that case, the reviewer sees the app disabled dialog instead of being able to use the app normally.

The app rejection screenshot from Google will look similar to the one below:

A screenshot of the app disabled dialog shown in the app.

To resolve this, open your app dashboard and reactivate your app there.

A screenshot of the app reactivation dialog in the dashboard.

Submitting the app for review again

If this was the last or only app rejection reason, please follow these steps to submit your app for review again:

Go to the publishing overview in the Google Play Console.

Submit the changes for review using the button at the top right.

A screenshot of the button to send the app for review.