Foreground Service (FGS) Helper
Generate compliant android:foregroundServiceType declarations, Manifest permissions, and reviewer-proof justification answers for Google Play Console. Clear Android 14 (API 34) and Android 15 (API 35) foreground service policy reviews on the first try.
100% client-side · Private by design · No account required
Strict Android 14 (API 34) & Android 15 (API 35) Policy Enforcement
Google Play will reject your APK/AAB upload if your app targets Android 14+ and declares a foreground service without specifyingandroid:foregroundServiceTypeand filling out the mandatory Play Console justification questionnaire. Use this tool to generate policy-proof answers and compliant code.
1Service Identification
2Foreground Service Type (Android 14+)
Choose the specific category matching your background operation:
3Play Console Justification Details
Play Console Declaration Form
Paste directly into Play Console > App content > Foreground Services
1. What core user-facing functionality requires this foreground service type?
In "My Application", the "Data Sync (Upload / Download / Backup)" foreground service is strictly used for: An Android app that lets users backup and synchronize their files and media to personal cloud storage. When this operation is active, users expect real-time feedback and uninterrupted execution until completion.
2. Describe the step-by-step user journey that triggers the foreground service:
The user taps "Start Full Backup" inside the Settings or Home screen. The app displays an ongoing progress dialog, and upon navigating away or locking the device, the foreground service displays a persistent notification with a progress percentage.
3. Why can this task NOT be handled by WorkManager or JobScheduler?
The operation is directly triggered by the active user and requires immediate, uninterrupted execution with real-time progress callbacks and cancelation controls in the notification drawer. WorkManager delays job execution under Doze mode and OS battery quotas, resulting in failed real-time transfers.
Reviewer Video / Demo Requirement: Notification Text Required: Must display a persistent, non-dismissible notification while running (Channel: "Ongoing Tasks / Service"). Example: "Syncing files with cloud storage... Tap to view progress.". Include cancel / pause action button if applicable.
Frequently asked questions
- Why did Google Play reject my Foreground Service permission?
- Google Play strictly enforces that foreground services can only be used for user-initiated tasks that cannot be handled by WorkManager or JobScheduler. If Google reviewers determine your sync, upload, or processing task can be deferred or run without a persistent notification, they will reject your declaration.
- When must I use WorkManager instead of a Foreground Service?
- Use WorkManager if the task does not require immediate user interaction, can be deferred until Wi-Fi/charging is connected, or does not need a real-time persistent notification. Use Foreground Service only when the user explicitly triggers an operation that must continue running uninterrupted with a real-time status notification.
- Can a single service declare multiple foregroundServiceTypes in Android 14+?
- Yes. In your AndroidManifest.xml, you can pipe multiple types together, for example: android:foregroundServiceType="location|dataSync". However, you must justify each type individually in the Google Play Console questionnaire.
- Is POST_NOTIFICATIONS required for Foreground Services on Android 13+?
- Yes. Android 13 (API 33) and higher requires the runtime android.permission.POST_NOTIFICATIONS permission. If this permission is not granted, the foreground service notification will not appear, which triggers a policy strike in Google Play.
- What is the timeout limit for shortService type?
- The shortService foregroundServiceType is strictly limited to 3 minutes (180 seconds). The Android OS will automatically terminate the service with an exception if it exceeds this threshold.