[Question]: Bug]: Android - Apps targeting Android 15 or later cannot use BOOT_COMPLETED broadcast receivers to launch certain foreground service types

[AndreiMisiukevich]

How can we help?

I am using TwilioSDK along with OneSignal.
I don't have own BOOT_COMPLETED broadcast receivers, but I use FCM token for communication between server and my app...

Any suggestions what I can do to mitigate that?

That's what I got from the Google review:

1 issue found
We found some common issues that are preventing your app from being sent for review. You must address these issues before you can send your changes for review.
Restricted foreground service types
Apps targeting Android 15 or later cannot use BOOT_COMPLETED broadcast receivers to launch certain foreground service types. Doing this will cause your app to crash for users on Android 15 and later. Your app starts restricted foreground service types using BOOT_COMPLETED broadcast receivers in the following places:
I6.a.v
To resolve this issue, make sure that BOOT_COMPLETED broadcast receivers do not start restricted foreground servi

and

com.ryanheise.audio_session.AndroidAudioManager$Singleton$$ExternalSyntheticApiModelOutline0 -> I6.a:

Code of Conduct

• I agree to follow this project's Code of Conduct

-- > OneSignal/OneSignal-Flutter-SDK#1045

[jkasten2]

This SDK doesn't create a foreground service, it use BOOT_COMPLETED but it only creates normal notifications from it.

The class you noted isn't from OneSignal, so you will need to investigate that library and confirm you have the correct class if that doesn't turn up anything.

com.ryanheise.audio_session.AndroidAudioManager$Singleton$$ExternalSyntheticApiModelOutline0 -> I6.a:

[AndreiMisiukevich]

@jkasten2, thanks for the response

What does this service do?

What are the consequences of removing this service from my app?

<receiver
    android:name="com.onesignal.notifications.receivers.BootUpReceiver"
    android:enabled="false"
    tools:node="remove" />

[jkasten2]

Notifications that haven't been interacted with (opened, swiped away, or dismiss all) will not be restored back to the notification shade when the device is rebooted. This can result in the end-user missing some notifications.

• Notifications are also restored when the app is opened again