Closed Bubu closed 1 year ago
Might fix itself with the next upstream merge, when we switch to upstreams UnifiedPush implementation :thinking:
Still happening, just got another crash like this. Edit: Wait not, true, it's a different exception, but happening in a related circumstances:
09-15 21:04:17.380 3384 8271 E AndroidRuntime: FATAL EXCEPTION: pool-8-thread-1
09-15 21:04:17.380 3384 8271 E AndroidRuntime: Process: de.spiritcroc.riotx.testing.foss, PID: 3384
09-15 21:04:17.380 3384 8271 E AndroidRuntime: android.app.BackgroundServiceStartNotAllowedException: Not allowed to start service Intent { act=im.vector.app.core.services.CallService.ACTION_CALL_TERMINATED cmp=de.spiritcroc.riotx.testing.foss/im.vector.app.core.services.CallAndroidService (has extras) }: app is in background uid UidRecord{e1f0fa7 u0a454 TRNB bg:+1m38s247ms idle change:procadj procs:0 seq(785123,766682)}
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1908)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at android.app.ContextImpl.startService(ContextImpl.java:1864)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at android.content.ContextWrapper.startService(ContextWrapper.java:817)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at im.vector.app.features.call.webrtc.WebRtcCallManager.onCallEnded(WebRtcCallManager.kt:16)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at im.vector.app.features.call.webrtc.WebRtcCallManager.access$onCallEnded(WebRtcCallManager.kt:1)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at im.vector.app.features.call.webrtc.WebRtcCallManager$createWebRtcCall$webRtcCall$4.invoke(WebRtcCallManager.kt:2)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at im.vector.app.features.call.webrtc.WebRtcCallManager$createWebRtcCall$webRtcCall$4.invoke(WebRtcCallManager.kt:1)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at im.vector.app.features.call.webrtc.WebRtcCall$terminate$2.invokeSuspend(WebRtcCall.kt:18)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at im.vector.app.features.call.webrtc.WebRtcCall$terminate$2.invoke(Unknown Source:8)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at im.vector.app.features.call.webrtc.WebRtcCall$terminate$2.invoke(Unknown Source:4)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:1)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at kotlinx.coroutines.BuildersKt.withContext(Unknown Source:10)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at im.vector.app.features.call.webrtc.WebRtcCall.terminate(WebRtcCall.kt:1)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at im.vector.app.features.call.webrtc.WebRtcCall.access$terminate(WebRtcCall.kt:1)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at im.vector.app.features.call.webrtc.WebRtcCall$endCall$1.invokeSuspend(WebRtcCall.kt:8)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:3)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:18)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: at java.lang.Thread.run(Thread.java:1012)
09-15 21:04:17.380 3384 8271 E AndroidRuntime: Suppressed: kotlinx.coroutines.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@ae7f8b6, java.util.concurrent.Executors$FinalizableDelegatedExecutorService@55089b7]
Still need to try to reproduce the original exception though.
Didn't manage to reproduce yet. I guess push should be same to upstream now though, if I don't miss anything :thinking:
This issue is stale because it has been open 150 days with no activity. Remove stale label or comment or this will be closed in 14 days.
Describe the bug Crash when receiving call (in background) via unifiedpush.
To Reproduce Steps to reproduce the behavior: (might not work 100% of the time?)
Expected behavior No crash, schildi starts ringing
Smartphone (please complete the following information):
Additional context
Upstream relevance
Add any other context about the problem here.
Logcat crash log:
Have also sent a rageshake yesterday night.