As of version 1.4.2 the signin command has been disabled on newer versions of macOS. This is an interim workaround to the crasher first identified in #107.
mas 1.4.2 was never released through Homebrew, so it must besownloaded and installed manually from the 1.4.2 release or built from source using Xcode.
😞 Situation
In macOS High Sierra (10.13) Apple removed the -[ISAccountService signInWithContext:replyBlock:] method from the StoreFoundation private Apple framework which this app relies on to authenticate users through the signin command. I have done a lot of digging and debugging but have not found another API that works to authenticate a user with the Mac App Store.
Users running older macOS versions (10.9-10.12) are unaffected.
👉🏻⌨️ Workaround
Sign into the Mac App Store GUI app manually. Once signed in MAS app, the mas command should work fine.
I know this is not an ideal scenario, especially for script automation. Hopefully, I'll find a real solution to this soon.
Please 👍 this issue if you are affected by it.
Related: #107, #129, #147, #155, #159, #160, #162
As of version 1.4.2 the
signincommand has been disabled on newer versions of macOS. This is an interim workaround to the crasher first identified in #107.😞 Situation
In macOS High Sierra (10.13) Apple removed the
-[ISAccountService signInWithContext:replyBlock:]method from the StoreFoundation private Apple framework which this app relies on to authenticate users through thesignincommand. I have done a lot of digging and debugging but have not found another API that works to authenticate a user with the Mac App Store.Users running older macOS versions (10.9-10.12) are unaffected.
👉🏻⌨️ Workaround
Sign into the Mac App Store GUI app manually. Once signed in MAS app, the mas command should work fine.
I know this is not an ideal scenario, especially for script automation. Hopefully, I'll find a real solution to this soon.
Please 👍 this issue if you are affected by it.
Related: #107, #129, #147, #155, #159, #160, #162