startForeground fail after updating to Android 8.1: solution in Kotlin

Foreground service crashed after the update? You are not alone

Imagine: you launch your app, it should run in the background, displaying an important notification. Everything worked perfectly on Android 7.0, users are happy. But then an update to Android 8.1 comes out — and the app crashes with a mysterious error startForeground fail. Sound familiar? If you've encountered this problem, you know how unsettling it is. On Stack Overflow, this question has gathered thousands of views, meaning it has affected many developers. In this article, we will break down why this happens, how to fix the error in Kotlin, and, most importantly, how to avoid it in the future.

What is startForeground and why is it needed?

In Android, a foreground service is a service that performs actions noticeable to the user. For example, playing music, recording a GPS track, or downloading a file. Unlike a regular service, a foreground service must display a persistent notification in the status bar. This is done by calling startForeground(), which takes a notification ID and the Notification object itself.

Starting from Android 8.0 (API 26), Google introduced strict restrictions on background services. Now, if you try to start a foreground service without a properly configured notification, the system will throw a ForegroundServiceStartNotAllowedException or simply ignore the call. In Android 8.1, these restrictions became even stricter, and the startForeground fail error became widespread.

Why does startForeground fail occur in Android 8.1?

The main reason is the absence or incorrect configuration of a notification channel. Before Android 8.0, notifications could be created without channels. After the update, Google required developers to create at least one channel for each type of notification. If you call startForeground() with a notification that has no channel, the system simply doesn't know how to display it and throws an error.

The second reason is timing violation. You must call startForeground() within the first 5 seconds after starting the service. If you don't, the service will be killed, and the app may crash.

The third reason is attempting to start the service from the background. Starting from Android 8.0, launching a foreground service from a background context (e.g., from a BroadcastReceiver or another service) is prohibited. The only exception is if the app is in the foreground.

How to fix: step-by-step guide in Kotlin

Let's rewrite your service so it works on Android 8.1 and above. We'll use Kotlin — a modern and concise language.

Step 1: Create a notification channel

The channel must be created before you show the notification. The best place is in the onCreate() method of your service or in the Application class. Here's an example:

class MyForegroundService : Service() {\n    companion object {\n        const val CHANNEL_ID = "my_foreground_channel"\n        const val NOTIFICATION_ID = 1\n    }\n\n    override fun onCreate() {\n        super.onCreate()\n        createNotificationChannel()\n    }\n\n    private fun createNotificationChannel() {\n        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {\n            val channel = NotificationChannel(\n                CHANNEL_ID,\n                "Foreground Service Channel",\n                NotificationManager.IMPORTANCE_LOW\n            ).apply {\n                description = "Channel for foreground service notifications"\n            }\n            val notificationManager = getSystemService(Context.NOTIFICATION_SERVICE) as NotificationManager\n            notificationManager.createNotificationChannel(channel)\n        }\n    }\n}

Note: we check the SDK version. On older devices, channels are not needed, and