-
Notifications
You must be signed in to change notification settings - Fork 274
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
purchase
doesn't work on macOS 10.15+
#289
Comments
I can reproduce this on macOS 11.2.3 on an M1 MacBookPro. |
purchase
doesn't work on macOS 10.15+
@mas-cli/contributors It looks like I think that I think that, instead of reenabling To ensure that people don't spend more than they expect on an app, we could require user to specify a maximum cost they're willing to pay (like |
`purchase` seems to work on macOS 12+. Resolve mas-cli#289 Signed-off-by: Ross Goldberg <484615+rgoldberg@users.noreply.github.com>
Your Environment
mas version
: 1.7.0macOS version (
system_profiler SPSoftwareDataType -detailLevel mini
):System Software Overview:
mas Install Method
brew install mas
(homebrew-core)Describe the Bug
It seems that purchasing isn't working in Catalina. It's a brand new Macbook Pro 2020 with a fresh install of Homebrew and mas.
Every time I try to purchase an app, specifically apps that aren't free, after using TouchID to buy the app, I get a "Purchase of this item is not currently available" error from the App Store and the download fails. This has happened for multiple apps, most recently Tweetbot 3.3.3 (
mas purchase 1384080005
).I can manually go to the app store and purchase it, but get this error when using mas.
I was able to download and install XCode and Microsoft ToDo (both free apps), but any app that is not free does not work.
To Reproduce
Steps to reproduce the behavior:
mas purchase 1384080005
in terminalExpected Behavior
I would expect the App Store to ask me for TouchID or Password to confirm the purchase, and then begin to download.
Actual Behavior
See screenshot below for error.
Screenshots, Terminal Output
The text was updated successfully, but these errors were encountered: