-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
signin
disabled on macOS 10.13+
#164
Comments
This impacts me quite a bit as I rely on mas to automate updates on my Mac labs. I'm happy to help look for solutions as I am able. Does anyone have a list of Apple API resources as a start? |
See mas-cli/mas#164 for more details
Can we open the App Store GUI on 10.13+? |
@SConaway the |
@b3cramer docs for all of Apple's public frameworks is available online, but no docs or developer support is available for private frameworks. If you are interested in perusing these private frameworks, you can use the aging class-dump command to generate headers from the binaries on your mac. I've done this for some versions of macOS in my macOSPrivateFrameworks repo. |
I'll prolly do that tomorrow of 10.14. I'll make a PR to you with them. |
See mas-cli/mas#164 for more details
Well, the signin command isn’t disabled on Mojave and it’s still crashing the same for me. |
With Mojave |
Workaround described does not work in Mojave... |
Reinstate when mas-cli/mas#164 gets fixed.
@jpartain89 @robfletcher @franklouwers What version of mas were you using? Note that this change was introduced in 1.4.2 which has not been released through Homebrew. |
I just tried 1.4.2 and it works.
There is another problem with 1.4.1 (don't think it was mentioned before) which makes 1.4.1 completely broken on Mojave
|
@phatblat I'm using 1.4.1 from Homebrew Is 1.4.2 coming to homebrew or is there a reason it's being held back? Happy to install it another way if so. I use |
@robfletcher the PR for mas version |
Any update on this?? need a fix for this issue. |
FWIW, on macOS 12.0 (arm64) after signing into the App Store with the GUI, I was able to use |
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. |
2016 MBP here, GUI sign in workaround failing after update to 12.01 (21A559) |
Unable to sign in with mid-2017 MBP |
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 😭
macOS Monterey 12.0.1 |
With lastest mas update works on Monterey |
it worked👍 |
for those subcommands are no longer supported by `mas` on the recent versions of macOS - mas-cli/mas#164 - mas-cli/mas#417 - https://github.com/mas-cli/mas#%EF%B8%8F-known-issues
doesn't work for me on ventura 13.2 |
signin
disabled on macOS 10.13+
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
The text was updated successfully, but these errors were encountered: