You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If run on macOS, Cmd-Q doesn't quit the app. Eventually it gets terminated in the bg by the OS:
2022-12-23 14:41:12.997720+0000 ElementX[79926:3533289] [BackgroundTask] Background Task 71 ("SuspendApp: EAD5BC66-AC64-4E7E-82F1-5060591B698C"), was created over 30 seconds ago. In applications running in the background, this creates a risk of termination. Remember to call UIApplication.endBackgroundTask(_:) for your task in a timely manner to avoid this.
2022-12-23 14:41:13.014946+0000 ElementX[79926:3533289] [Lifecycle] Background tasks took too long to complete. Moving to next phase of termination.
2022-12-23 14:41:13.019732+0000 ElementX[79926:3533289] AppCoordinator.isSuspended():30 didSet to: true
The text was updated successfully, but these errors were encountered:
I'm going to close this issue in favour of #438 regarding the background task.
Its worth pointing out though that running iOS apps on Apple Silicon Macs have a different lifecycle to macOS apps. Quitting the app does the equivalent of backgrounding it on iOS as the app isn't aware of the normal macOS app lifecycle. This would be one of the advantages of switching to Catalyst for the Mac app I guess.
If run on macOS, Cmd-Q doesn't quit the app. Eventually it gets terminated in the bg by the OS:
The text was updated successfully, but these errors were encountered: