`outdated` & `upgrade` fail on Catalina

[misc-activities]

I just installed mas on my macOS Catalina installation. I have signed into the app store from the Mac App Store. When I run mas list, I can see all the installed apps. There is an update available for Xcode which I want to try installing using mas. However, when I run mas outdated, it doesn't show the available update. I ran mas reset and then ran mas outdated again but that didn't work as well.

[hernancorigliano]

I have the same issue but not only with Xcode, but all pending updates. There is no output from mas outdated.

Looks like CKUpdateController.shared().availableUpdates() is always returning an empty list.

[Luminus]

I'm experiencing the same situation.

• mas outdated has no output even though I have apps that need to be updated
• Similarly, mas upgrade returns Everything is up-to-date, which is not true
• Trying to update individual apps by running mas upgrade XXXXXXXX where XXXXXXXX is the relevant ID returns Warning: Nothing found to upgrade

[andrewcrook]

Doesn’t seem to work on Catalina I have never got it to work fully.
I can only get list, install and remove to work.
At least I can install all my applications scripted on Big Sur
the question is do all the Mas features work on Big Sur or is it going to be like Catalina?

[Yelles]

same for me, updates are available in AppStore, but when I run mas outdated it doesn't show the available update... same for mas upgrade/install
(i'm on catalina)

[drewauff]

Outdated switch dead on Catalina.

[ke11]

not working on Catalina after the recent security patch

[brian163]

I may be seeing something similar on Mojave. I came here to see if I could figure out why the App Store app is telling me there is an update for BlackMagic Speed Disk (425264550) but mas (which I usually run to avoid the aggravation with the GUI I've had in the past) just told me everything was up to date.

When I do a manual list of everything installed:
mas list | grep Disk
425264550 Disk Speed Test (3.2)

When I tell mas to search the store:
mas search "Disk Speed Test" | grep Disk
425264550 Blackmagic Disk Speed Test (3.3)

When I just run mas outdated, nothing is returned. And mas upgrade does nothing.

Obviously there is a difference between the names but I wouldn't think that would cause mas to mismatch since the app ID are the same?

UPDATE: Interestingly (?), I decided to try a forced reinstall:
mas install 425264550 --force
==> Installed Blackmagic Disk Speed Test

only to find once again the resulting name in the listing didn't match after the "update":
mas list | grep Disk
425264550 Disk Speed Test (3.3)

I don't know where the "Blackmagic" reference keeps disappearing to. Maybe it's blackmagic ??? ..... ;-)

[Stanzilla]

Also not working on BigSur

[andrewcrook]

Apple has changed the way the AppStore works this may mean mas might not ever fully work with it.

[benftrex]

Not working for me on Catalina and Bigsur.
As others have pointed, only "mas list" works. Outdated and upgrade don't, and never have for me since Catalina.

[duhd1993]

I have the same issue but not only with Xcode, but all pending updates. There is no output from mas outdated.

Looks like CKUpdateController.shared().availableUpdates() is always returning an empty list.

If mas info and mas list works, isn't it an easy fix to use the info to decide if an upgrade is needed? This might be clumsy and slower but at least it works.

[rgoldberg]

If mas info and mas list works, isn't it an easy fix to use the info to decide if an upgrade is needed

I just verified that mas info shows the current version of the app in the store while mas list shows the version of the app installed on my machine, so this should work.

I'd be willing to work on fixing this, but I haven't used Xcode, Mac APIs, Swift, or Objective-C before (I mainly code in Java & Kotlin).

I forked the repo, cloned the fork, and opened the project in Xcode 12.3 (12C33) on macOS 11.1 on Intel.

I received the following 8 errors & 1 warning when I build.

If someone can help me fix the build problems, I'll continue working on a PR for this issue.

~/Code/fork/mas/mas/main.swift:9:8:
No such module 'Commandant'

~/Code/fork/mas/MasKit/Commands/Account.swift:9:8:
No such module 'Commandant'

SwiftLint not installed, download from https://github.com/realm/SwiftLint

~/Code/fork/mas/Carthage/Build/Mac/Commandant.framework:
No such file or directory

~/Library/Developer/Xcode/DerivedData/mas-gwgogfusotbawbfpkrdgrxttzbny/Build/Intermediates.noindex/mas-cli.build/Debug/MasKit.build/module.modulemap:9:12:
Header 'MasKit-Swift.h' not found

~/Code/fork/mas/MasKitTests/Commands/AccountCommandSpec.swift:9:18:
Could not build Objective-C module 'MasKit'

~/Code/fork/mas/Carthage/Build/Mac/Quick.framework:
No such file or directory

~/Code/fork/mas/Carthage/Build/Mac/Nimble.framework:
No such file or directory

~/Code/fork/mas/Carthage/Build/Mac/Commandant.framework:
No such file or directory

[duhd1993]

If mas info and mas list works, isn't it an easy fix to use the info to decide if an upgrade is needed

I just verified that mas info shows the current version of the app in the store while mas list shows the version of the app installed on my machine, so this should work.

I'd be willing to work on fixing this, but I haven't used Xcode, Mac APIs, Swift, or Objective-C before (I mainly code in Java & Kotlin).

I forked the repo, cloned the fork, and opened the project in Xcode 12.3 (12C33) on macOS 11.1 on Intel.

I received the following 8 errors & 1 warning when I built.

If someone can help me fix the build problems, I'll continue working on a PR for this issue.

~/Code/fork/mas/mas/main.swift:9:8:
No such module 'Commandant'

~/Code/fork/mas/MasKit/Commands/Account.swift:9:8:
No such module 'Commandant'

SwiftLint not installed, download from https://github.com/realm/SwiftLint

~/Code/fork/mas/Carthage/Build/Mac/Commandant.framework:
No such file or directory

~/Library/Developer/Xcode/DerivedData/mas-gwgogfusotbawbfpkrdgrxttzbny/Build/Intermediates.noindex/mas-cli.build/Debug/MasKit.build/module.modulemap:9:12:
Header 'MasKit-Swift.h' not found

~/Code/fork/mas/MasKitTests/Commands/AccountCommandSpec.swift:9:18:
Could not build Objective-C module 'MasKit'

~/Code/fork/mas/Carthage/Build/Mac/Quick.framework:
No such file or directory

~/Code/fork/mas/Carthage/Build/Mac/Nimble.framework:
No such file or directory

~/Code/fork/mas/Carthage/Build/Mac/Commandant.framework:
No such file or directory

Looks like you are just missing some package, for example, https://github.com/Carthage/Commandant

[rgoldberg]

A git repo for Commandant already exists under ./Carthage/Checkouts/Commandant in the mas repo.

So the files should be there, it's just that the build doesn't know where they are.

Are there build setup instructions for mas?

I didn't see any in the readme or contributing docs.

I'm used to the build system (Gradle, for my projects) automatically downloading listed dependencies and producing the correct classpath for the compiler.

Do Apple ecosystem builds really require manual setup these days?

[duhd1993]

A git repo for Commandant already exists under ./Carthage/Checkouts/Commandant in the mas repo.

So the files should be there, it's just that the build doesn't know where they are.

Are there build setup instructions for mas?

I didn't see any in the readme or contributing docs.

I'm used to the build system (Gradle, for my projects) automatically downloading listed dependencies and producing the correct classpath for the compiler.

Do Apple ecosystem builds really require manual setup these days?

Try the build script maybe. https://github.com/mas-cli/mas/blob/master/script/build