Open phatblat opened 6 years ago
Things worked fine on 12.0 (32A344) which shipped on my M1 Max but once updated to 12.0.1 (21A559) is the same "not logged in" state
Same on MacBook Air M1 12.0.1 (21A559).
Still the same on 2019 Intel MacBook macOS 12.0.1 (21A559); not logged in state reported by mas although the App Store GUI shows me logged in.
After my upgrade to 12.0.1 it all broke again. Sigh.
Things worked fine on 12.0 (32A344) which shipped on my M1 Max but once updated to 12.0.1 (21A559) is the same "not logged in" state
2016 MBP here, GUI sign in workaround failing after update to 12.01 (21A559)
Unable to sign in with mas signin
and also mas
doesn't recognize signing in through App Store app.
mid-2017 MBP macOS Monterey 12.0.1 mas 1.8.3
For those reporting failures on macOS Monterey, you may be interested in https://github.com/mas-cli/mas/issues/417 instead of this issue, which dates back to High Sierra.
For those reporting failures on macOS Monterey, you may be interested in #417 instead of this issue, which dates back to High Sierra.
Thanks!
Any update on this??
So, is there anyone who can tell me how to avoid this error π
The 'signin' command has been disabled on this macOS version. Please sign into the Mac App Store app manually.
macOS Monterey 12.0.1 mbp 19
With lastest mas update works on Monterey
it workedπ MBP 2021 14inch M1 Pro macOS Monterey 12.2.1 mas 1.8.6
doesn't work for me on ventura 13.2 MBP Pro 2023 M2 mas 1.8.6
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.π 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 thesignin
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