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.
What to check, in order
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.
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.
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 our reading of Google’s examples, which also describe one use case as not for regular system or server-initiated tasks. We move that kind of task to WorkManager or a user-initiated data transfer job, as Android recommends, and drop the foreground service.
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.
Related: Google Play Data safety form rejected · Google Play 12 testers for 14 days · Google Play permission changes for 2027 · Google Play Photo and Video Permissions