Restricted foreground service types

[mdmohsin7]

A production version of your app crashes because it uses BOOT_COMPLETED broadcast receivers to start a restricted foreground service type. Apps targeting Android 15 or later cannot use BOOT_COMPLETED broadcast receivers to launch certain foreground service types.

To fix this issue, make sure that your app's code and your SDKs don't use a BOOT_COMPLETED broadcast receiver to launch restricted foreground service types, and publish an update to your app

[beastoin]

Investigation

Checked the codebase for Android 15 foreground service type compliance:

Foreground services declared:

Service	Type	Location
ForegroundService (flutter_foreground_task)	connectedDevice|location	AndroidManifest.xml:77-81
BackgroundService (flutter_background_service)	microphone	AndroidManifest.xml:82-85

BOOT_COMPLETED status:

• Permission RECEIVE_BOOT_COMPLETED is declared (manifest:35) but no <receiver> component exists to handle it
• Both services have autoRunOnBoot: false / autoStartOnBoot: false explicitly set (foreground.dart:134, services.dart:175)

Target SDK: 35 (Android 15) — build.gradle:95

Assessment: The app appears already compliant — no boot receiver launches restricted foreground service types. The RECEIVE_BOOT_COMPLETED permission is declared but unused (dead permission).

Questions:

1. @mdmohsin7 — is this from an actual Google Play Console warning/rejection? If so, can you share the exact error message? The warning screenshot mentions "BOOT_COMPLETED broadcast receivers to start a restricted foreground service type" but I can't find this pattern in the code.
2. Could this be triggered by a dependency (flutter_foreground_task or flutter_background_service) registering a boot receiver internally? Worth checking their manifests via aapt dump xmltree app-release.apk AndroidManifest.xml on the built APK.

Suggested next step: Build a release APK and dump the merged manifest to check if any dependency adds a BOOT_COMPLETED receiver that we don't see in the source manifest.