Crash because of the foreground service did not start in time #112

Activity

1. kevinguitar

   added

   bug

   needs triage

   on Jul 8, 2022
2. christosts

   self-assigned this

   on Jul 8, 2022
3. kvn-stgl commented on Jul 19, 2022

   

   kvn-stgl

   on Jul 19, 2022

   More actions

   I have the same issue in my app (at least I can see it in crashlytics).
   But in my case, the issue is a bit stranger: It only happens at Samsung Devices and only with Android 12. The other things are identical (we can not reproduce it manually and it happens around 70% in the background).
   Also, the crashlog is (almost) identical (Android 12):

   Fatal Exception: android.app.ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{4e97eb7 u0 ***}
          at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:2147)
          at android.app.ActivityThread.access$2900(ActivityThread.java:310)
          at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2376)
          at android.os.Handler.dispatchMessage(Handler.java:106)
          at android.os.Looper.loopOnce(Looper.java:226)
          at android.os.Looper.loop(Looper.java:313)
          at android.app.ActivityThread.main(ActivityThread.java:8669)
          at java.lang.reflect.Method.invoke(Method.java)
          at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
          at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)
   

   👍React with 👍8Reacted by Kostiantyn Prysiazny, OctoberCat, Mukesh Kumar Singh, Albert Kobiakov, Karandeep singh, prateek-nykaa, algrid and Tamim Attafi
4. christosts commented on Jul 21, 2022

   

   christosts

   on Jul 21, 2022

   Contributor

   More actions

   Some context:

   This error indicates that Context.startForegroundService() was called but Service.startForeground() was not called soon enough. The Android docs say that the second should be called within

   an amount of time comparable to the ANR interval

   so let's say that's 5 seconds. In beta01, Context.startForegroundService() is called when the library posts notifications itself and specifically in two cases:

   1. When the user taps on the play button of the notification. The play button's PendingIntent is built with PendingIntent.getForegroundService()
   2. When playback starts as a result of that. The library will call Context.startForegroundService() and immediately call Service.startForeground(). Notice that Context.startForegroundService() is called again here, because playback may have started from a BT headset button and not from the notification.

   If you don't let the library post notifications, e.g. you override MediaSessionService.onUpdateNotification(), then the above will not be triggered, in which case it's a matter of how your app is handling notifications and the service lifecycle. @kevinguitar shared in #111 that they use the library notifications, but I'm mentioning this for @kvn-stgl.

   If the library is posting notifications, then my investigation starting point would be if the user tapped play on the notification (1) but for some reason the player did not start playback within 5 seconds, so that the control flow reaches (2) after 5 seconds or never. This could happen if the app's main thread was busy executing other code for 5 seconds between tapping the play icon and starting playback. Or, the app has logic such that even when the play button is pressed on the notification, playback does not start, in which case (2) does not happen.

   Is there a case that anything of the above is happening in your app?
5. christosts

   added

   need more info

   and removed

   needs triage

   on Jul 21, 2022
6. kvn-stgl commented on Jul 29, 2022

   

   kvn-stgl

   on Jul 29, 2022

   More actions

   Hi @christosts, thanks for your explanation.

   We don't override the the MediaSessionService.onUpdateNotification method in our implementation. Here you can look at our implementation to get a bit more information about it: https://gist.github.com/kvn-stgl/ca019f18b9b8eab556b53b0d48c01641

   I don't think there is a valid way in our app where the playback doesn't start within 5 seconds (except the internet connection is down and the exoplayer can not load the next media item from the web but I think this shouldn't be a problem here).

   But I looked at the crashlog again and the crash is always direct at the beginning. So the app starts and 5 seconds later it will crash. So maybe there is some ANR at our app start which prevents foreground service. I will look a bit deeper into it.
7. XuQK commented on Aug 1, 2022

   

   XuQK

   on Aug 1, 2022

   More actions

   I have the same problem, it crash 10 times in a row, about ten seconds apart, the Crashlytics tell me they are all in the background. This information may be helpful.

   👍React with 👍1Reacted by Panu Puro
8. christosts commented on Aug 2, 2022

   

   christosts

   on Aug 2, 2022

   Contributor

   More actions

   I spotted a bug that occurs after the player has finished playback. The notification still shows a pause button (which does nothing) and the MediaSessionService remains in the foreground.

   I don't think this is the root cause for the exceptions you are seeing reported, but I'm going to link the commit to this issue anyway since I spotted it while investigating this issue. Thank you for reports and for helping us.

   👍React with 👍2Reacted by Kevin Chiu and Panu Puro
9. icbaker

   removed

   need more info

   on Aug 5, 2022
10. dpreussler commented on Sep 26, 2022

    

    dpreussler

    on Sep 26, 2022

    Last edited by dpreussler

    More actions

    We have the same issue on WearOS, all Android 11:
    Galaxy Watch5 Pro
    Galaxy Watch4 Classic
    Galaxy Watch4

    Dont have much more info but its early in the application start
11. yschimke commented on Sep 26, 2022

    

    yschimke

    on Sep 26, 2022

    Contributor

    More actions

    Is this related #167?
12. christosts commented on Oct 3, 2022

    

    christosts

    on Oct 3, 2022

    Contributor

    More actions

    Is this related #167?

    Yes. I am going to close this issue, as #167 provided a fix, more on this comment. The fix will be included in the next release, if you see the issue persisting, please report here or at #167.
13. christosts

    closed this as completedon Oct 3, 2022
14. androidx

    locked and limited conversation to collaborators on Mar 3, 2023