Unable to open devices & services, app crashes

As the title suggests based on the last 2 updates ive not been able to get to the devices and integrations page. Not problem via web browser so supsect a problem with the android app. Ive tried clearing cache and an app reinstall.

Here is a link to a screen recording: HASS - Album on Imgur

Anyone else experiencing this?

Core: 2024.12.1
Supervisor : 2024.11.4
Operating System: 14.0
Frontend: 20241127.6

Android app: 2024.10.3-full

Hey there! Yes same issue here. It happened a few weeks or so ago on my phone and went away. Then it started happening again yesterday. Unable to find anything that resolves the problem. HA had an update yesterday, so I can only assume that is the cause. However, I have no idea why specifically the only issue is when selecting Devices and Integrations in the companion app. And that this has been an issue twice for me recently.

I have a Z Flip 5.

Core 2024.12.1
Supervisor 2024.11.4
Operating System 14.0
Frontend 20241127.6

App version 2024.10.3-full

Same here, every time Devices & Services are touched, the app crashes.
Core 2024.12.1
Supervisor 2024.11.4
Operating System 14.0
Frontend 20241127.6
App 2024.10.3-full

Hi, experience same prob since yesterday 6.12.2024 on android app.

Rest of the app works fine. But a press on Devices and the app shuts down.

I run the German version of the app.

  • Core2024.12.1
  • Supervisor2024.11.4
  • Operating System14.0
  • Frontend20241127.6

I have so far no resolution to this problembut assume itā€™s a app bug.

Has anybody the knowhow to check on that?

Hi :wave: Android dev here

This is a known issue with the app and fixed in version 2024.12.1-full, which has been submitted earlier this week but weā€™re waiting on Google to approve it.

As a workaround for now: remove the ā€œNearby devicesā€ permission for the app or join the app beta to get the version with fix now.

1 Like

Just ran the updated app and same issue happening

can you confirm the app version number?

2024.12.1-full

Should add- using Green and power cycled that before opening updated app

can you check settings > companion app > troubleshooting > show and share logs to see if there is a Recent crash tab? that would be helpful for us to solve as it as we are yet to reproduce the issue. If the crash is not there and you are familiar with logcat it would be helpful to get the new traceback.

what is using ā€œgreenā€?

Sorry HA Green. Was able to grab this
08 21:22:17.173 28057 28097 D WM-GreedyScheduler: Cancelling work ID 5a2252f4-ac25-46e1-88d8-1840daf843df
12-08 21:22:17.182 28057 28097 D WM-SystemJobScheduler: Scheduling work ID f195d149-f613-430b-a961-822dfa1a06c4Job ID 64800
12-08 21:22:17.190 28057 28097 D WM-GreedyScheduler: Starting tracking for f195d149-f613-430b-a961-822dfa1a06c4
12-08 21:22:17.192 28057 28097 D WM-StopWorkRunnable: StopWorkRunnable for 5a2252f4-ac25-46e1-88d8-1840daf843df; Processor.stopWork = false
12-08 21:22:17.194 28057 28097 D WM-Processor: Processor cancelling 7dbe4d2b-eaf5-451f-aa50-c8ae5fe83c22
12-08 21:22:17.194 28057 28097 D WM-Processor: WorkerWrapper could not be found for 7dbe4d2b-eaf5-451f-aa50-c8ae5fe83c22
12-08 21:22:17.195 28057 28097 D WM-GreedyScheduler: Cancelling work ID 7dbe4d2b-eaf5-451f-aa50-c8ae5fe83c22
12-08 21:22:17.197 28057 28097 D WM-SystemJobScheduler: Scheduling work ID dd09ab84-1051-4bb1-b97a-52e1ad39b8d0Job ID 64801
12-08 21:22:17.224 28057 28097 D WM-GreedyScheduler: Starting work for dd09ab84-1051-4bb1-b97a-52e1ad39b8d0
12-08 21:22:17.224 28057 28097 D WM-GreedyScheduler: Starting tracking for f195d149-f613-430b-a961-822dfa1a06c4
12-08 21:22:17.225 28057 28097 D WM-Processor: Processor: processing WorkGenerationalId(workSpecId=dd09ab84-1051-4bb1-b97a-52e1ad39b8d0, generation=0)
12-08 21:22:17.227 28057 28097 D WM-GreedyScheduler: Constraints met: Scheduling work ID WorkGenerationalId(workSpecId=f195d149-f613-430b-a961-822dfa1a06c4, generation=0)
12-08 21:22:17.227 28057 28097 D WM-Processor: Processor: processing WorkGenerationalId(workSpecId=f195d149-f613-430b-a961-822dfa1a06c4, generation=0)
12-08 21:22:17.231 28057 28057 I InsetsSourceConsumer: applyRequestedVisibilityToControl: visible=true, type=statusBars, host=io.homeassistant.companion.android/io.homeassistant.companion.android.webview.WebViewActivity
12-08 21:22:17.232 28057 28057 I InsetsSourceConsumer: applyRequestedVisibilityToControl: visible=true, type=navigationBars, host=io.homeassistant.companion.android/io.homeassistant.companion.android.webview.WebViewActivity
12-08 21:22:17.235 28057 28057 I BLASTBufferQueue_Java: update, w= 1218 h= 1308 mName = ViewRootImpl@b3ea009[WebViewActivity] mNativeObject= 0xb400006fd09f9590 sc.mNativeObject= 0xb400006f209ccfd0 format= -3 caller= android.view.ViewRootImpl.updateBlastSurfaceIfNeeded:3017 android.view.ViewRootImpl.relayoutWindow:10131 android.view.ViewRootImpl.performTraversals:4110 android.view.ViewRootImpl.doTraversal:3288 android.view.ViewRootImpl$TraversalRunnable.run:11344 android.view.Choreographer$CallbackRecord.run:1689
12-08 21:22:17.235 28057 28057 I ViewRootImpl@b3ea009[WebViewActivity]: Relayout returned: old=(27,610,1053,1726) new=(27,610,1053,1726) relayoutAsync=false req=(1026,1116)0 dur=3 res=0x400 s={true 0xb400007000a5e280} ch=false seqId=0
12-08 21:22:17.235 28057 28057 I ViewRootImpl@b3ea009[WebViewActivity]: registerCallbackForPendingTransactions
12-08 21:22:17.236 28057 28057 I SurfaceView@edfcca6: onWindowVisibilityChanged(0) false android.view.SurfaceView{edfcca6 G.Eā€¦ ā€¦I. 0,0-0,0} of ViewRootImpl@9e2a5bf[WebViewActivity]
12-08 21:22:17.236 28057 28057 D SurfaceView@edfcca6: 249547942 updateSurface: has no frame
12-08 21:22:17.237 28057 28123 I ViewRootImpl@b3ea009[WebViewActivity]: mWNT: t=0xb400006e809df890 mBlastBufferQueue=0xb400006fd09f9590 fn= 2 mRenderHdrSdrRatio=1.0 caller= android.view.ViewRootImpl$6.onFrameDraw:5635 android.view.ViewRootImpl$2.onFrameDraw:2146 android.view.ThreadedRenderer$1.onFrameDraw:792
12-08 21:22:17.243 28057 28057 I BLASTBufferQueue_Java: new BLASTBufferQueue, mName= ViewRootImpl@9e2a5bf[WebViewActivity] mNativeObject= 0xb400006fd09f98b0 sc.mNativeObject= 0xb400006f209c9b50 caller= android.view.ViewRootImpl.updateBlastSurfaceIfNeeded:3028 android.view.ViewRootImpl.relayoutWindow:10131 android.view.ViewRootImpl.performTraversals:4110 android.view.ViewRootImpl.doTraversal:3288 android.view.ViewRootImpl$TraversalRunnable.run:11344 android.view.Choreographer$CallbackRecord.run:1689 android.view.Choreographer$CallbackRecord.run:1698 android.view.Choreographer.doCallbacks:1153 android.view.Choreographer.doFrame:1079 android.view.Choreographer$FrameDisplayEventReceiver.run:1646
12-08 21:22:17.243 28057 28057 I BLASTBufferQueue_Java: update, w= 1080 h= 2400 mName = ViewRootImpl@9e2a5bf[WebViewActivity] mNativeObject= 0xb400006fd09f98b0 sc.mNativeObject= 0xb400006f209c9b50 format= -3 caller= android.graphics.BLASTBufferQueue.:89 android.view.ViewRootImpl.updateBlastSurfaceIfNeeded:3028 android.view.ViewRootImpl.relayoutWindow:10131 android.view.ViewRootImpl.performTraversals:4110 android.view.ViewRootImpl.doTraversal:3288 android.view.ViewRootImpl$TraversalRunnable.run:11344
12-08 21:22:17.243 28057 28057 I ViewRootImpl@9e2a5bf[WebViewActivity]: Relayout returned: old=(0,0,1080,2400) new=(0,0,1080,2400) relayoutAsync=false req=(1080,2400)0 dur=6 res=0x403 s={true 0xb400007000a4f410} ch=true seqId=0
12-08 21:22:17.244 28057 28057 D ViewRootImpl@9e2a5bf[WebViewActivity]: mThreadedRenderer.initialize() mSurface={isValid=true 0xb400007000a4f410} hwInitialized=true
12-08 21:22:17.244 28057 28057 I SurfaceView@edfcca6: windowStopped(false) false android.view.SurfaceView{edfcca6 G.Eā€¦ ā€¦I. 0,0-0,0} of ViewRootImpl@9e2a5bf[WebViewActivity]
12-08 21:22:17.244 28057 28057 D SurfaceView@edfcca6: 249547942 updateSurface: has no frame
12-08 21:22:17.244 28057 28057 D ViewRootImpl@9e2a5bf[WebViewActivity]: reportNextDraw android.view.ViewRootImpl.performTraversals:4718 android.view.ViewRootImpl.doTraversal:3288 android.view.ViewRootImpl$TraversalRunnable.run:11344 android.view.Choreographer$CallbackRecord.run:1689 android.view.Choreographer$CallbackRecord.run:1698
12-08 21:22:17.244 28057 28057 D SurfaceView@edfcca6: 249547942 updateSurface: has no frame
12-08 21:22:17.244 28057 28057 I ViewRootImpl@9e2a5bf[WebViewActivity]: Setup new sync=wmsSync-ViewRootImpl@9e2a5bf[WebViewActivity]#14
12-08 21:22:17.244 28057 28057 I ViewRootImpl@9e2a5bf[WebViewActivity]: Creating new active sync group ViewRootImpl@9e2a5bf[WebViewActivity]#15
12-08 21:22:17.245 28057 28057 I ViewRootImpl@9e2a5bf[WebViewActivity]: registerCallbacksForSync syncBuffer=false
12-08 21:22:17.245 28057 28124 I ViewRootImpl@9e2a5bf[WebViewActivity]: Received frameDrawingCallback syncResult=0 frameNum=1.
12-08 21:22:17.245 28057 28124 I ViewRootImpl@9e2a5bf[WebViewActivity]: mWNT: t=0xb400006e809e00d0 mBlastBufferQueue=0xb400006fd09f98b0 fn= 1 mRenderHdrSdrRatio=1.0 caller= android.view.ViewRootImpl$8.onFrameDraw:13841 android.view.ThreadedRenderer$1.onFrameDraw:792
12-08 21:22:17.245 28057 28124 I ViewRootImpl@9e2a5bf[WebViewActivity]: Setting up sync and frameCommitCallback
12-08 21:22:17.249 28057 28103 I BLASTBufferQueue: ViewRootImpl@9e2a5bf[WebViewActivity]#6 onFrameAvailable the first frame is available
12-08 21:22:17.249 28057 28103 I ViewRootImpl@9e2a5bf[WebViewActivity]: Received frameCommittedCallback lastAttemptedDrawFrameNum=1 didProduceBuffer=true
12-08 21:22:17.250 28057 28057 I ViewRootImpl@9e2a5bf[WebViewActivity]: reportDrawFinished seqId=0
12-08 21:22:17.252 28057 28057 I WM-SystemFgDispatcher: Stopping foreground service
12-08 21:22:17.252 28057 28057 D WM-SystemFgService: Shutting down.
12-08 21:22:17.270 28057 28057 D WM-SystemJobService: onStopJob for WorkGenerationalId(workSpecId=5a2252f4-ac25-46e1-88d8-1840daf843df, generation=0)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: Work [ id=5a2252f4-ac25-46e1-88d8-1840daf843df, tags={ io.homeassistant.companion.android.sensors.SensorWorker } ] was cancelled
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: androidx.work.impl.WorkerStoppedException
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.WorkerWrapper.interrupt(WorkerWrapper.kt:348)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.Processor.interrupt(Processor.java:439)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.Processor.stopAndCancelWork(Processor.java:280)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.CancelWorkRunnable.cancel(CancelWorkRunnable.kt:33)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.CancelWorkRunnable.forNameInline$lambda$0(CancelWorkRunnable.kt:127)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.CancelWorkRunnable.$r8$lambda$gmz-7SyxTGDd6CwHjvOsJ11-hcc(Unknown Source:0)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.CancelWorkRunnable$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.room.RoomDatabase.runInTransaction(RoomDatabase.kt:585)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.CancelWorkRunnable.forNameInline(CancelWorkRunnable.kt:123)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.EnqueueRunnable.enqueueWorkWithPrerequisites(EnqueueRunnable.java:249)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.EnqueueRunnable.enqueueContinuation(EnqueueRunnable.java:136)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.EnqueueRunnable.processContinuation(EnqueueRunnable.java:129)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.EnqueueRunnable.addToDatabase(EnqueueRunnable.java:93)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.EnqueueRunnable.enqueue(EnqueueRunnable.java:74)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.WorkContinuationImpl.lambda$enqueue$0$androidx-work-impl-WorkContinuationImpl(WorkContinuationImpl.java:201)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.WorkContinuationImpl$$ExternalSyntheticLambda0.invoke(D8$$SyntheticClass:0)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.OperationKt.launchOperation$lambda$2$lambda$1(Operation.kt:50)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.OperationKt.$r8$lambda$XKAkIiEN7OgIvwuLUZRQpJhjmyE(Unknown Source:0)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.OperationKt$$ExternalSyntheticLambda1.run(D8$$SyntheticClass:0)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.SerialExecutorImpl$Task.run(SerialExecutorImpl.java:96)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at java.lang.Thread.run(Thread.java:1012)
12-08 21:22:17.271 28057 28099 D WM-WorkerWrapper: Status for 5a2252f4-ac25-46e1-88d8-1840daf843df is null ; not doing any work
12-08 21:22:17.272 28057 28099 D WM-StopWorkRunnable: StopWorkRunnable for 5a2252f4-ac25-46e1-88d8-1840daf843df; Processor.stopWork = false
12-08 21:22:17.275 28057 28057 D WM-SystemJobService: onStartJob for WorkGenerationalId(workSpecId=f195d149-f613-430b-a961-822dfa1a06c4, generation=0)
12-08 21:22:17.275 28057 28057 D WM-WorkerWrapper: Starting work for io.homeassistant.companion.android.websocket.WebsocketManager
12-08 21:22:17.275 28057 28057 D WM-WorkerWrapper: Starting work for io.homeassistant.companion.android.sensors.SensorWorker
12-08 21:22:17.276 28057 28057 D WM-SystemJobService: onStartJob for WorkGenerationalId(workSpecId=dd09ab84-1051-4bb1-b97a-52e1ad39b8d0, generation=0)
12-08 21:22:17.276 28057 28098 D WM-Processor: Work WorkGenerationalId(workSpecId=f195d149-f613-430b-a961-822dfa1a06c4, generation=0) is already enqueued for processing
12-08 21:22:17.276 28057 28098 D WM-Processor: Work WorkGenerationalId(workSpecId=dd09ab84-1051-4bb1-b97a-52e1ad39b8d0, generation=0) is already enqueued for processing
12-08 21:22:17.279 28057 28057 D SurfaceView@edfcca6: 249547942 updateSurface: has no frame
12-08 21:22:17.279 28057 28139 D ServerConnectionInfo: localUrl is: false, usesInternalSsid is: false, usesWifi is: true
12-08 21:22:17.279 28057 28057 D WM-Processor: Processor 5a2252f4-ac25-46e1-88d8-1840daf843df executed; reschedule = false
12-08 21:22:17.279 28057 28057 D WM-GreedyScheduler: Stopping tracking for WorkGenerationalId(workSpecId=5a2252f4-ac25-46e1-88d8-1840daf843df, generation=0)
12-08 21:22:17.279 28057 28057 D WM-SystemJobService: 5a2252f4-ac25-46e1-88d8-1840daf843df executed on JobScheduler
12-08 21:22:17.281 28057 28099 I WM-Processor: Moving WorkSpec (f195d149-f613-430b-a961-822dfa1a06c4) to the foreground
12-08 21:22:17.295 28057 28057 I WM-SystemFgDispatcher: Started foreground service Intent { act=ACTION_START_FOREGROUND cmp=io.homeassistant.companion.android/androidx.work.impl.foreground.SystemForegroundService (has extras) }
12-08 21:22:17.295 28057 28057 D WM-SystemFgDispatcher: Notifying with (id:42, workSpecId: f195d149-f613-430b-a961-822dfa1a06c4, notificationType :1)
12-08 21:22:17.300 28057 28090 D SensorWorker: Updating all Sensors in foreground.
12-08 21:22:17.301 28057 28099 D WM-GreedyScheduler: Cancelling work ID 5a2252f4-ac25-46e1-88d8-1840daf843df
12-08 21:22:17.301 28057 28057 D WM-SystemFgDispatcher: Notifying with (id:42, workSpecId: f195d149-f613-430b-a961-822dfa1a06c4, notificationType :1)
12-08 21:22:17.301 28057 28057 I NotificationManager: io.homeassistant.companion.android: notify(42, null, Notification(channel=Sensor Worker shortcut=null contentView=null vibrate=null sound=null defaults=0x0 flags=0x0 color=0x00000000 vis=PRIVATE semFlags=0x0 semPriority=0 semMissedCount=0)) as user
12-08 21:22:17.302 28057 28090 D ServerConnectionInfo: localUrl is: false, usesInternalSsid is: false, usesWifi is: true
12-08 21:22:17.303 28057 28099 I WM-WorkerWrapper: Worker result SUCCESS for Work [ id=dd09ab84-1051-4bb1-b97a-52e1ad39b8d0, tags={ io.homeassistant.companion.android.websocket.WebsocketManager } ]
12-08 21:22:17.304 28057 28057 D WM-Processor: Processor dd09ab84-1051-4bb1-b97a-52e1ad39b8d0 executed; reschedule = false
12-08 21:22:17.304 28057 28057 D WM-SystemJobService: dd09ab84-1051-4bb1-b97a-52e1ad39b8d0 executed on JobScheduler
12-08 21:22:17.307 28057 28099 D WM-GreedyScheduler: Cancelling work ID dd09ab84-1051-4bb1-b97a-52e1ad39b8d0
12-08 21:22:17.307 28057 28099 D WM-SystemJobScheduler: Scheduling work ID dd09ab84-1051-4bb1-b97a-52e1ad39b8d0Job ID 64801
12-08 21:22:17.308 28057 28057 I ViewRootImpl@b3ea009[WebViewActivity]: handleWindowFocusChanged: 1 0 call from android.view.ViewRootImpl.-$$Nest$mhandleWindowFocusChanged:0
12-08 21:22:17.308 28057 28057 D ViewRootImpl@b3ea009[WebViewActivity]: mThreadedRenderer.initializeIfNeeded()#2 mSurface={isValid=true 0xb400007000a5e280}
12-08 21:22:17.308 28057 28057 I ImeFocusController: onPreWindowFocus: skipped, hasWindowFocus=true mHasImeFocus=false
12-08 21:22:17.309 28057 28057 I ImeFocusController: onPostWindowFocus: skipped, hasWindowFocus=true mHasImeFocus=false
12-08 21:22:17.410 28057 28090 D ServerConnectionInfo: localUrl is: false, usesInternalSsid is: false, usesWifi is: true
12-08 21:22:17.410 28057 28090 D ServerConnectionInfo: localUrl is: false, usesInternalSsid is: false, usesWifi is: true
12-08 21:22:19.683 28057 28057 I ViewRootImpl@b3ea009[WebViewActivity]: ViewPostIme pointer 0
12-08 21:22:19.761 28057 28057 I ViewRootImpl@b3ea009[WebViewActivity]: ViewPostIme pointer 1
12-08 21:22:19.780 28057 28057 I WindowManager: WindowManagerGlobal#removeView, ty=2, view=DecorView@d960d10[WebViewActivity], caller=android.view.WindowManagerGlobal.removeView:628 android.view.WindowManagerImpl.removeViewImmediate:208 android.app.Dialog.dismissDialog:801
12-08 21:22:19.780 28057 28057 W WindowOnBackDispatcher: sendCancelIfRunning: isInProgress=falsecallback=android.app.Dialog$$ExternalSyntheticLambda4@c36ea3c
12-08 21:22:19.784 28057 28103 D OpenGLRenderer: endAllActiveAnimators on 0xb400006e50ac2d90 (RippleDrawable) with handle 0xb400007070a047e0
12-08 21:22:19.784 28057 28057 I ViewRootImpl@b3ea009[WebViewActivity]: dispatchDetachedFromWindow
12-08 21:22:19.791 28057 28057 D InputTransport: Input channel destroyed: ā€˜80f5f85ā€™, fd=130
12-08 21:22:19.792 28057 28057 E AccessibilityInteractionController: mViewRootImpl is invalid

Thanks for supporting. Ive joined the beta but not pushing update yet

Seems to be the integrations page that is causing the crash. I was able to get to the devices page via the settings of a device on my dashboard but going to integations then crashes it.

@alexandernesbitt did you update yet? the version in beta will be released to everyone soon, the faster we get feedback the faster we can fix the issue if it is still there. We no longer see issues in play console about this so pretty confident it is fixed and possible a separate issue is impacted the other user tough to tell as the logs are not complete and dont contain the actual crash.

Is none of this relevant? Its got Android and Cancelled and Shutting Down all over it

onFrameAvailable the first frame is available
12-08 21:22:17.249 28057 28103 I ViewRootImpl@9e2a5bf[WebViewActivity]: Received frameCommittedCallback lastAttemptedDrawFrameNum=1 didProduceBuffer=true
12-08 21:22:17.250 28057 28057 I ViewRootImpl@9e2a5bf[WebViewActivity]: reportDrawFinished seqId=0
12-08 21:22:17.252 28057 28057 I WM-SystemFgDispatcher: Stopping foreground service
12-08 21:22:17.252 28057 28057 D WM-SystemFgService: Shutting down.
12-08 21:22:17.270 28057 28057 D WM-SystemJobService: onStopJob for WorkGenerationalId(workSpecId=5a2252f4-ac25-46e1-88d8-1840daf843df, generation=0)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: Work [ id=5a2252f4-ac25-46e1-88d8-1840daf843df, tags={ io.homeassistant.companion.android.sensors.SensorWorker } ] was cancelled
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: androidx.work.impl.WorkerStoppedException
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.WorkerWrapper.interrupt(WorkerWrapper.kt:348)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.Processor.interrupt(Processor.java:439)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.Processor.stopAndCancelWork(Processor.java:280)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.CancelWorkRunnable.cancel(CancelWorkRunnable.kt:33)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.CancelWorkRunnable.forNameInline$lambda$0(CancelWorkRunnable.kt:127)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.CancelWorkRunnable.$r8$lambda$gmz-7SyxTGDd6CwHjvOsJ11-hcc(Unknown Source:0)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.CancelWorkRunnable$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.room.RoomDatabase.runInTransaction(RoomDatabase.kt:585)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.CancelWorkRunnable.forNameInline(CancelWorkRunnable.kt:123)
12-08 21:22:17.271 28057 28099 I WM-WorkerWrapper: at androidx.work.impl.utils.EnqueueRunnable.enqueueWorkWithPrerequisites(EnqueueRunnable.java:249)

No itā€™s not relevant and safe to ignore.

This log suggests that the Android companion app for Home Assistant is experiencing a problem related to background tasks, specifically involving WorkManager. Hereā€™s a breakdown of whatā€™s happening and potential solutions:


Key Observations from the Log:

  1. onFrameAvailable and reportDrawFinished Logs:

These messages indicate that the appā€™s UI thread is processing frames, likely related to rendering updates in the WebView (possibly the Home Assistant frontend).

  1. WorkManager Issue:

The following lines show the appā€™s WorkManager stopped a task:

WM-SystemFgService: Shutting down.
Work [ id=5a2252f4-ac25-46e1-88d8-1840daf843df, tags={ io.homeassistant.companion.android.sensors.SensorWorker } ] was cancelled

AI fail?

the cancellation is safe to ignore it happens when jobs are replaced or other reasons. Neither of which is the actual crash that we are asking for. The crash is not going to be visible in the app logs. You may need to use logcat to get the actual traceback required.

our sensor worker also has nothing to do with the WebView

For me, upgrading the App to 2024.12.2-full did the trick. The app doesnā€™t crash any more.
Thanks!

1 Like

Yes, sorry didnt get notification of your reply. All was resolved with app update. Thanknyou.