It didn't happen for the first few days after I installed Monterey (presumably because it didn't try to update). That made me think the issue might not be purely due to the OS upgrade, which threw off some of my debugging efforts.
It only happened on one out of 2 computers I upgraded to Monterey.
The mode of failure was pretty inscrutable, and I didn't find anything useful by trying to research the stack trace.
After a few weeks of trying to debug it myself, I was glad to to find this in the bug tracker!
The --skipUpdate argument works well for now (thanks for the details, Yoshimasa Niwa!), but it would definitely be nice to see this fixed (especially so I don't have to tell my friends caveats about upgrading their OS).
> A critical security issue has been found that affects Minecraft. If you have the game running, please shut down all running instances of the game and Launcher and restart - your Launcher will automatically download the fix.
For those of us who have been using --skipUpdate as a workaround, is there any safe way for us to run Minecraft?
I'm glad to see MCL-17399 is resolved, but after removing the workaround for that I'm unfortunately I'm still seeing this issue where `Minecraft Launcher` stops responding, such that trying to open `Minecraft.app` silently fails until I force quit the launcher.
Lucas Garron
MCL-17399
I've also been running into this issue.
It was really confusing for me because:
After a few weeks of trying to debug it myself, I was glad to to find this in the bug tracker!
The --skipUpdate argument works well for now (thanks for the details, Yoshimasa Niwa!), but it would definitely be nice to see this fixed (especially so I don't have to tell my friends caveats about upgrading their OS).
I just saw this on Twitter: https://twitter.com/slicedlime/status/1469150993527017483
> A critical security issue has been found that affects Minecraft. If you have the game running, please shut down all running instances of the game and Launcher and restart - your Launcher will automatically download the fix.
For those of us who have been using --skipUpdate as a workaround, is there any safe way for us to run Minecraft?
I'm glad to see
MCL-17399is resolved, but after removing the workaround for that I'm unfortunately I'm still seeing this issue where `Minecraft Launcher` stops responding, such that trying to open `Minecraft.app` silently fails until I force quit the launcher.