Originally posted by martinmacecek-rearc February 28, 2024
Got a problem with the desktop app on Mac (0.9.0-arm64): after installation and signing in through Github, the Workshop seems to start, but remains in this state:
I also cannot seem to be able to fully quit the application, which may be related to the workshop startup problem. I recorded this behavior:
https://github.com/noop-inc/documentation/assets/156843182/9319e6f6-8ee2-4e24-bd7a-2a7048165df0
Now, when i force quit through Activity Monitor, I get this error on initial startup:
After that I am back to the workshop not successfully starting and the app being unable to quit without using force.
So, I went ahead and uninstalled the app and reinstalled, but i am immediately presented with the above error message again, which then, upon confirmation, brings me to the main screen, but the workshop again unable to start.
Any ideas of what to do to furhter troubleshoot/resolve this? I am not sure if I did something wrong or if this is truly a bug.
Discussed in https://github.com/orgs/noop-inc/discussions/130
Originally posted by martinmacecek-rearc February 28, 2024
Got a problem with the desktop app on Mac (0.9.0-arm64): after installation and signing in through Github, the Workshop seems to start, but remains in this state:
I also cannot seem to be able to fully quit the application, which may be related to the workshop startup problem. I recorded this behavior:
https://github.com/noop-inc/documentation/assets/156843182/9319e6f6-8ee2-4e24-bd7a-2a7048165df0
Now, when i force quit through Activity Monitor, I get this error on initial startup:
After that I am back to the workshop not successfully starting and the app being unable to quit without using force.
So, I went ahead and uninstalled the app and reinstalled, but i am immediately presented with the above error message again, which then, upon confirmation, brings me to the main screen, but the workshop again unable to start.
Any ideas of what to do to furhter troubleshoot/resolve this? I am not sure if I did something wrong or if this is truly a bug.