Fatal exception. Bad notification for startForeground.

This exception occurs in SDK 27 (Android 8.1) but not in lower SDK versions.

Fatal Exception: android.app.RemoteServiceException: Bad notification for startForeground: java.lang.RuntimeException: invalid channel for service notification: Notification(channel=null pri=0 contentView=null vibrate=null sound=null defaults=0x0 flags=0x42 color=0x00000000 groupKey=com.clamber vis=PRIVATE)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1768)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loop(Looper.java:164)
       at android.app.ActivityThread.main(ActivityThread.java:6494)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)

Turning off notifications prevents the exception from occurring.

    const options = {
      // ...
      notification: {
        // Required to prevent 
        enabled: false,
      },
    };

The issue appears to be fairly common and widely document for other libraries. I believe this is the same issue on SO.

I don’t have a reproduction available but I believe there is one in an issue on this other upload library

[peterent]

Using APK 28. After searching and searching I finally found this thread. I turned notification off. Now the app doesn’t crash. Instead, it throws this error: “Android Oreo requires a notification configuration for the service to run. https://developer.android.com/reference/android/content/Context.html#startForegroundService(android.content.Intent)”

[dtuite]

Ready for review.