mas-cli / mas-cli/mas

`account` doesn't work on macOS 12+

Open
#417 77 comments 32 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug investigation
Dominant language
Swift
Stars
12.4k
Forks
299
Avg merge
1d 2h
Merged PRs (30d)
1

Description

Your Environment

  • mas version: 1.8.3
  • macOS version (system_profiler SPSoftwareDataType -detailLevel mini): 12.0 (21A5522h)
mas Install Method

brew install mas (homebrew-core)

Describe the Bug

mas account says I'm not signed in, although I am:

Not signed in
Error: Not signed in

To Reproduce

  1. Run mas account
  2. Make sure App Store has a signed in Apple ID
  3. Run mas account again

Expected Behavior

Getting no error and being able to use other mas commands that depend on being signed in.

Actual Behavior

Not signed in
Error: Not signed in

Screenshots, Terminal Output

$ mas account
Not signed in
Error: Not signed in

Additional Context

It stopped working around 2 weeks ago I guess? Maybe it worked with the previous version?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the mas account entry point on macOS 12 with mas 1.8.3 and trace the authentication path used when the App Store has a signed-in Apple ID. Done means mas account recognizes the account without errors and dependent mas commands work; no source file or test is named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, swift
Domain
authentication, cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.