My WatchOS sometimes just freeze and then I got this error message: "<BLSBacklightSceneUpdateAction: 0x18e539c0; info: <BSSettings: 0x18e70f40> {\n (1) = No;\n (2) = No;\n (3) = Yes;\n}; responder: <_BSActionResponder: 0xc0084f00; active: YES; waiting: YES> clientInvalidated = NO;\nclientEncoded = NO;\nclientResponded = NO;\nreply = <BSMachPortSendOnceRight: 0xc008ca60; usable: NO; (496:aa9f:send-once xpcCode) from (34:59d07:send-once take)>;\nannulled = NO;>" Does anyone have this issue? What is the reason and any solution for this? Thanks!

I have a app that has both mobile and watch versions. Recently some testers report that the watch app could not be launched if the put the app in the background and then resume. And if they kill the app and try to launch again, there is no any response when tapping the app icon. I managed to export some system logs, and this info in the screenshot looks suspicious. Does anyone have the same issue? Recently the app has been transferred to another developer account, not sure if it is related, this TestFlight version was rebuilt with the new team

I have a app that has both mobile and watch versions. Recently some testers report that the watch app could not be launched if the put the app in the background and then resume. And if they kill the app and try to launch again, there is no any response when tapping the app icon. I managed to export some system logs by installing a sysdiagnose profile, and this info looks suspicious