Android says startForeground isn't being called even though it's the first line of onCreate()

Question

I have a service that tracks the state of a delivery to the user.

It has an onCreate method like this:

    override fun onCreate() {
        super.onCreate()
        job = Job()

        // We must always start foreground as otherwise we can get crashes
        startForeground(
            NOTIFICATION_ID,
            createNotification(deliveryTrackerUseCase.statusData.value)
        )

        deliveryTrackerListener.setListeningIfNecessary(true)
        wakeLock =
            powerManager.newWakeLock(PowerManager.PARTIAL_WAKE_LOCK, "DeliveryTrackerService::lock")


        combine(
            deliveryTrackerUseCase.statusData,
            orderUpdatesRepository.orderUpdatesEnabled
        ) { trackerStatus, updatesEnabled ->
            if (updatesEnabled) {
                notificationManager.notify(NOTIFICATION_ID, createNotification(trackerStatus))
            }
        }.launchIn(coroutineScope)
    }

However I'm still seeing the following crash in firebase crashlytics:

Fatal Exception: android.app.RemoteServiceException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{4f65483 u0 com.example.engine.DeliveryTrackerService}
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2389)
       at android.os.Handler.dispatchMessage(Handler.java:110)
       at android.os.Looper.loop(Looper.java:219)
       at android.app.ActivityThread.main(ActivityThread.java:8393)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:513)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1055)

What on earth do I have to do to stop this crashing? This used to set the notification inside the coroutine scope, but I've moved it to be at the top of the onCreate function to avoid this issue, but we're still seeing crashes.

EDIT: this only seems to be on Huawei devices, so perhaps that's something to do with it.

https://stackoverflow.com/questions/44425584/context-startforegroundservice-did-not-then-call-service-startforeground Have you checked the link that has the same error and the solution methods are shared? — Arda Kazancı, Aug 13 '21 at 08:16

score 2 · Answer 1 · answered Aug 13 '21 at 08:19

2

it's not sync,it may be because your app do too much work on main thread,and let the oncreat call too slow. this error happen after call startForegroundService 5s(or other seconds).

it's easy to check the reason,if this error happen 100%,it's your code error. if it's happen low percent,it's about machine state.

answered Aug 13 '21 at 08:19

Silence

126
4

I've never seen it happen, it just is visible in our crash reporting for a significant number of users. – James Riordan Aug 16 '21 at 08:18
so it not because your code has any error，just because of the performance of different devices. the only way is put startForegroundService as soon as quickly – Silence Aug 18 '21 at 02:33
Yeah and I have it on pretty much the first line, so I don't know what else I can do. – James Riordan Aug 18 '21 at 13:15
nothing.or not do too much things when you start the service – Silence Aug 20 '21 at 02:30
Yeah my point was I'm already doing that. – James Riordan Aug 20 '21 at 07:35
I think that's all you can do – Silence Aug 23 '21 at 02:34

Android says startForeground isn't being called even though it's the first line of onCreate()

1 Answers1