I enable our Mac's Parental Controls app restrictions on my kids' accounts. I downloaded the new OS X launcher this morning, and it crashes immediately with a signature error on those accounts. If I disable the app restrictions (or run it under my account), it works fine.
This has been happing to me too. Rebooting has returned things to order. It happened again today and I started looking for a more permanent solution. My understanding right now is that Minecraft Launcher is getting auto-updated and its checksum is changing so Parental Controls rejects it. But there's still some weirdness going on because in looking at the allowed apps for my son's account, Minecraft Launcher appears twice.
I spent years as a Java programmer myself and all this indirection involved in launching Minecraft is ridiculous. Their standard test suite should include testing this under a restricted account.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I enable our Mac's Parental Controls app restrictions on my kids' accounts. I downloaded the new OS X launcher this morning, and it crashes immediately with a signature error on those accounts. If I disable the app restrictions (or run it under my account), it works fine.
Has anyone found a way to fix this?
This has been happing to me too. Rebooting has returned things to order. It happened again today and I started looking for a more permanent solution. My understanding right now is that Minecraft Launcher is getting auto-updated and its checksum is changing so Parental Controls rejects it. But there's still some weirdness going on because in looking at the allowed apps for my son's account, Minecraft Launcher appears twice.
I spent years as a Java programmer myself and all this indirection involved in launching Minecraft is ridiculous. Their standard test suite should include testing this under a restricted account.