Skip to content

Google Play policy issue

Google Play rejected my app over foreground service permissions. What do I fix?

Play Console is holding your update over foreground service permissions, or the app, now targeting Android 14, crashes when a foreground service starts. Both come from the same change: apps that target Android 14 must say which type of foreground service they run, in the manifest and in Play Console. Here’s what Google and Android ask for, in their own words, or hand it over at a fixed price.

Rather hand it over? App Fix Ticket: One reproducible bug in an existing mobile or web app, diagnosed and fixed.

Full refund if Simon can’t take it on once he sees your project, or if you cancel before work starts. Refund terms.

Short answer

If your app targets Android 14 or later, declare every foreground service type it uses on the App content page in Play Console, with a description, the effect of delays or interruptions on users, the use case, and a link to a video of a user triggering the feature. In the manifest, give each service its type and the matching permission. If a task fits no type, Android recommends WorkManager or a user-initiated data transfer job instead.

Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.

What to check, in order

  1. 01

    The Play Console declaration is missing or thin

    “you’ll need to declare any foreground service types that you use in a new declaration on the App content page (Monitor and improve > App content) in Play Console.” Google Play, Declaring your foreground service information in Google Play Console

    For each type, Google asks you to describe the feature that uses it, say what happens to users if the system delays or interrupts the task, pick the use case, and link a video. Fill in every type the app declares in its manifest, including ones a plugin added.

  2. 02

    The video doesn’t show a user starting it

    “The video should demonstrate the steps the user needs to take in your app in order to trigger the feature.” Google Play, Declaring your foreground service information in Google Play Console

    Record the feature inside the app, from the tap that starts it. Google’s table adds rules per use case: a backup video can’t show a fully automatic or background backup, and a connected device video must show the in-app setup, not system settings.

  3. 03

    The task isn’t one a foreground service is for

    “we strongly recommend that you migrate your logic to use WorkManager or user-initiated data transfer jobs.” Android Developers, Foreground service types are required

    Google’s examples are user-initiated, such as choosing a specific photo to back up rather than a daily automatic backup. Work the app starts on its own, like a periodic sync, looks like a poor fit for the declaration in Simon’s reading of Google’s examples, which also describe one use case as not for regular system or server-initiated tasks. Simon moves that kind of task to WorkManager or a user-initiated data transfer job, as Android recommends, and drops the foreground service.

  4. 04

    An app targeting Android 14 crashes when the service starts

    “If an app that targets Android 14 doesn't define types for a given service in the manifest, then the system will raise MissingForegroundServiceTypeException upon calling startForeground() for that service.” Android Developers, Foreground service types are required

    Add android:foregroundServiceType to the service in the manifest, and declare the foreground service permission for that type. Android throws a SecurityException if the permission is missing, or if the type’s runtime requirements aren’t met when you call startForeground(), which might crash the app.

Checked against the vendor’s docs on : Google Play Help: Understanding foreground service and full-screen intent requirements; Android Developers: Foreground service types are required.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

“Very responsive, attentive to fixing bugs, and completed the project as needed! Thank you!”
A buyer in the United States, July 2022. Shopify on Fiverr
All 127 Fiverr reviews

Related: Google Play Data safety form rejected · Google Play 12 testers for 14 days · Google Play permission changes for 2027 · Google Play AccessibilityService API

Questions

More on this launch

What should the video show?

Google says it should demonstrate the steps a user takes in your app to trigger the feature. Its table adds rules for some use cases, such as showing a user starting a backup, not an automatic one.

Play Console also asks about full-screen intent. Is that the same?

No, that is a separate declaration for the USE_FULL_SCREEN_INTENT permission. For Android 14, Google says only apps whose core functionality is setting an alarm or receiving phone or video calls are granted it automatically; other apps need the user to grant it.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.

Something else?

Describe it and get a written quote

Describe the app and where it is in the launch. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.