What it means
If your app targets Android 14 or higher, you'll need to declare your app's foreground service types in the Play Console's app content page (Policy > App content).
Android Developers, foreground service types are required
The declaration covers every type in the merged manifest, including types declared by services that come from libraries. The store check lists each service and its types so you know what to declare, or what to remove.
Deadline
No new date recorded by the store check: the declaration applies to every app that targets API 34 or higher and declares a foreground service type.
How to fix it
1. List the types the build declares
Take the list from the store check report, or from the Merged Manifest tab in Android Studio (android:foregroundServiceType on each <service>).
2. Remove the types you do not use
<service
android:name="com.example.sdk.SyncService"
android:foregroundServiceType="dataSync"
tools:replace="android:foregroundServiceType" />3. Fill in the declaration
In Play Console, open Policy, then App content, then the foreground service permissions declaration. For each type, describe the user-visible task, the impact if the system deferred it, and link a video that shows the feature.
Check before you submit
Upload the APK, AAB or split-APK set (XAPK, APKS, APKM) on the store check page. It runs PLAY-FGS-DECLARATION against the dates on this page, then deletes the file: nothing about the app is kept. The same engine runs offline in the Narvy CLI, and exits with code 1 when a blocker is found, so it can gate a CI job.
narvy store-check app-release.aabFAQ
A library declares the type, not my code. Do I still declare it?
Yes, the declaration is about what the uploaded build contains. If the feature is unused, removing the service or the type from the merged manifest is cleaner than declaring it.
Is this the same as the foregroundServiceType crash?
No. The crash is a platform rule checked at runtime; this is a Play Console policy declaration. Both apply to apps targeting API 34+.