Skip to content
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

"Missing argument for Apple ID" error on macOS Mojave 10.14 #171

Closed
ghost opened this issue Sep 26, 2018 · 5 comments
Closed

"Missing argument for Apple ID" error on macOS Mojave 10.14 #171

ghost opened this issue Sep 26, 2018 · 5 comments

Comments

@ghost
Copy link

ghost commented Sep 26, 2018

After clean installation of macOS Mojave I noticed that mas is not working properly.

$ mas install 408981434
Error: Not signed in
$ mas signin
Missing argument for Apple ID

Of course I am logged in App Store but it seems that mas is not detecting it.

@rasmusbe
Copy link

Thanks for the issue report but this is already reported in #164

@TCB13
Copy link

TCB13 commented Sep 26, 2018

if I do mas signin [email protected] it asks for password, but crashes.

April:~ TCB13$ mas signin [email protected]
==> Signing in to Apple ID: [email protected]
Password: 
2018-09-26 19:29:24.456 mas[12447:1577786] -[__NSXPCInterfaceProxy_ISAccountService signInWithContext:replyBlock:]: unrecognized selector sent to instance 0x7f92a3616490
2018-09-26 19:29:24.458 mas[12447:1577786] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSXPCInterfaceProxy_ISAccountService signInWithContext:replyBlock:]: unrecognized selector sent to instance 0x7f92a3616490'

Why?

@borisschapira
Copy link

Hi! First of all, thanks for all your work on this project.
Just so you know, I've got the same issue than @TCB13 and the workaround in #164 (connect first through the GUI) doesn't seem to work. If I can do anything to help debug this further, count me in.

@phatblat
Copy link
Member

Please try again using mas 1.4.3. The signin command is disabled to avoid the crash but it should fix that error where it still thinks you aren’t signed in, provided that you sign in using the GUI app.

@borisschapira
Copy link

Thank you @phatblat!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants