Jorge Martin Espinosa
4725148919
Try handling ForegroundServiceStartNotAllowedException better ( #6483 )
...
* Try handling `ForegroundServiceStartNotAllowedException` better
The docs mention starting a foreground service when the app is on background is allowed when FCM receives a high priority notification, so we don't do it if the priority is not high.
Also, we handle the case where starting the foreground service fails so it doesn't crash the app.
2026-03-30 18:44:08 +02:00
..
2025-11-10 11:05:05 +01:00
2026-03-23 16:00:04 +01:00
2026-03-23 18:07:00 +01:00
2026-03-24 13:53:42 +01:00
2026-03-24 16:04:35 +00:00
2026-03-16 14:41:07 +00:00
2025-11-10 11:05:05 +01:00
2026-03-24 10:15:25 +01:00
2025-12-10 15:58:41 +01:00
2026-03-25 14:28:15 +01:00
2026-03-16 14:41:07 +00:00
2025-11-10 11:05:05 +01:00
2026-03-24 10:17:24 +01:00
2026-03-12 12:48:55 +01:00
2025-12-05 09:45:23 +01:00
2025-11-10 11:05:05 +01:00
2026-03-24 15:46:45 +01:00
2026-02-27 09:52:17 +01:00
2026-03-25 15:27:36 +01:00
2025-11-12 19:05:39 +01:00
2025-12-30 21:29:18 +01:00
2026-02-18 16:51:44 +00:00
2026-03-30 11:26:16 +02:00
2025-11-18 15:18:27 +01:00
2025-11-10 11:05:05 +01:00
2026-03-03 13:39:43 +01:00
2025-11-10 11:05:05 +01:00
2025-11-10 11:05:05 +01:00
2026-03-30 18:44:08 +02:00
2026-03-30 18:44:08 +02:00
2025-11-10 11:05:05 +01:00
2025-12-16 16:14:04 +01:00
2025-11-12 19:05:39 +01:00
2026-01-30 15:33:51 +01:00
2026-03-13 18:53:08 +01:00
2025-11-10 11:05:05 +01:00
2026-03-27 10:17:01 +01:00
2026-03-16 00:42:32 +00:00
2025-11-10 11:05:05 +01:00
2026-03-24 11:13:40 +01:00
2026-03-23 18:11:55 +01:00
2025-11-10 11:05:05 +01:00
2026-02-27 09:52:17 +01:00
2025-11-27 09:30:22 +01:00
2026-02-11 11:57:01 +01:00
2026-03-03 15:14:36 +00:00