While Android 12 stability is improving with every release, it’s still in beta and some users last night received a reminder of that status via an absolute slew of system “Foreground Service BG-Launch Restricted” notifications that were generated by Gboard.
Some Android 12 Beta 3 users this morning woke up to several dozen or so system-level notifications titled Foreground Service BG-Launch Restricted.
Apps that target Android 12 (API level 31) — which was released with Beta 3 this week — “can no longer start foreground services while running in the background, except for a few special cases.” The foreground action in Gboard’s case is likely a download. .
If an app tries to start a foreground service while the app is running in the background, and the foreground service doesn’t satisfy one of the exceptional cases, the system throws a ForegroundServiceStartNotAllowedException.
It’s somewhat annoying to clear all these alerts, especially since you undoubtedly received other notifications over the course of the night to make “Clear all†not quite the right solution.
Quite a few Android 12 Beta users were affected by the problem with the last Gboard app update taking place earlier this week?