After calling startService we are supposed to have a bit of time before turning
the service into a foreground service, but certain devices seem to be more
spartan and we've seen the following failure:
Caused by java.lang.IllegalStateException: Not allowed to start service Intent { act=JitsiMeetOngoingConferenceService:START cmp=org.jitsi.meet/.sdk.JitsiMeetOngoingConferenceService }: app is in background uid UidRecord{f6778d5 u0a220 CAC bg:+1m1s417ms idle change:idle procs:1 proclist:15604, seq(0,0,0)}
at android.app.ContextImpl.startServiceCommon + 1600(ContextImpl.java:1600)
at android.app.ContextImpl.startService + 1546(ContextImpl.java:1546)
at android.content.ContextWrapper.startService + 669(ContextWrapper.java:669)
at org.jitsi.meet.sdk.JitsiMeetOngoingConferenceService.launch + 50(JitsiMeetOngoingConferenceService.java:50)
Be expliocit and call startForegroundService, on supported platforms.
master
|
|
||
| 21 |
|
21 |
|
| 22 |
|
22 |
|
| 23 |
|
23 |
|
|
24 |
|
|
| 24 |
|
25 |
|
| 25 |
|
26 |
|
| 26 |
|
27 |
|
|
|
||
| 47 |
|
48 |
|
| 48 |
|
49 |
|
| 49 |
|
50 |
|
| 50 |
|
|
|
|
51 |
|
|
|
52 |
|
|
|
53 |
|
|
|
54 |
|
|
|
55 |
|
|
|
56 |
|
|
| 51 |
|
57 |
|
| 52 |
|
58 |
|
| 53 |
|
59 |
|