New Free Tool:iPhone Duo Foldable Simulator & Live PWA Readiness Audit.

Test your site live
Kerweb. Agence Capacitor
Back to Blog
Store Compliance
5 min read read

Google Play Foreground Services (FGS) Rejection: Background Permissions

Julien Kermarec
September 29, 2026

Foreground Service Restrictions on Android 14+

On Android 14 and Android 16, any app initiating a background service with startForeground() must declare at least one specific Foreground Service Type in its AndroidManifest.xml.

Failing to declare this results in submission rejection on Google Play Console or immediate SecurityException crashes on modern devices.

Common Foreground Service Types

  1. location: For continuous GPS tracking (navigation, delivery).
  2. dataSync: For background data sync or large uploads.
  3. mediaPlayback: For audio and podcast streaming.
  4. phoneCall or connectedDevice: For VoIP and Bluetooth hardware bridges.

Compliant Manifest Declaration

<manifest xmlns:android="http://schemas.android.com/apk/res/android">
    <uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
    <uses-permission android:name="android.permission.FOREGROUND_SERVICE_LOCATION" />

    <application>
        <service
            android:name="com.kerweb.plugin.LocationService"
            android:foregroundServiceType="location"
            android:exported="false" />
    </application>
</manifest>

During Play Console submission, submit a video demonstration proving the background feature is essential and visible to the user via a persistent notification.

FGS
Foreground Service
Google Play
Android
Is your mobile application stuck or rejected on app stores?
Julien Kermarec (certified Ionic Developer Expert) and the Kerweb team intervene within 24-48h to resolve policy rejections, fix native manifests and secure your release.
Resolve Store Rejection