Missing UI after update to MacOS Sonoma 14.6.1

effdee

WorkingHours version: 2.10.26 (Pro)
OS + version: MacOS Sonoma 14.6.1
Device model: MacBook Pro M1

After updating to MacOS Sonoma 14.6.1 WorkingHours won't display a window anymore. It worked fine right before the update.

Starting the application results in the application name "WorkingHours" being shown in the menu bar. Apart from that, however, there are no other menu items, no tray icon, and no window. There is a dock icon; clicking "Show All Windows" results in an empty desktop reporting "No Available Windows". De- and reinstalling the applicatoin does not solve the issue.

WorkingHours displays an UI normally when ran as user "root".

I'd like to get the window back. Any idea on how to proceed here?

effdee

After happily removing (ir)relevant files and directories from ~/Library/Containers/mac.partl.workinghours/ the window is back again. I lost my data in the process but this was expected and accepted.

Maybe there's a more graceful way to get the window back.

effdee

Looks like the MacOS update is just a red herring. This problem seems to be caused by database inconsistencies (or the way tags are handled): doing a "delete from {Tags,WorkUnitTags,ProjectTags}" via sqlite3 makes the window reappear.

timo

Is it possible you tampered with the SQLite database? It's possible that an error is thrown during app initialization because the database is in a corrupt state. This doesn't necessarily cause the app to crash, but prevents the window to be shown. Can you send me the database file via mail so I can have have a closer look?

effdee

No, I didn't touch the data.db before the problem showed up. In fact I didn't even know it existed until things were broken and I started debugging the issue.

And to clarify: the App doesn't crash. It simply displays no window. It's actually running and then has to be kill(1)ed.

I have a copy of an original data.db as written by WorkingHours that triggers the error. Problem is that I can't sent it as-is. However, I can sent you a copy with anonymized descriptions and details if that's OK for your.

timo

effdee Yes, you can send me a copy and I can analyze it.
It's also quite possible that macOS broke the database file during the update - I remember something similar happened to another user when he was using TimeMachine.
With the latest update that is currently rolling out, WorkingHours also tries to handle this issue (e.g. when there is a tag relation in the database between a work unit and a tag, but either the referenced tag or work unit isn't present in the database, WorkingHours will simply remove the tag relation from the database)