upgrade sometimes doesn't see upgrades until after outdated has been run

[StefanLobbenmeier]

Your Environment

• mas version: 1.8.6
• macOS version (system_profiler SPSoftwareDataType -detailLevel mini): macOS 13.0.1 (22A400)

mas Install Method

• brew install mas (homebrew-core)
• [] mas-cli/tap
• [] .pkg installer from releases
• [] Built from source
  • Fork/branch: ? (e.g. mas-cli/main)
  • Xcode version: 10.?

Describe the Bug

When I run mas ugprade, it says that there is nothing to upgrade. I first have to run mas outdated and then run upgrade again so it is able to find the upgrades. It would make more sense if mas upgrade would also check for updates itself, e.g. like brew does

To Reproduce

1. wait for an update to appear in the app store
2. run mas upgrade

Expected Behavior

mas upgrade also checks for updates

Actual Behavior

mas upgrade is unaware of updates

Screenshots, Terminal Output

If applicable, add screenshots to help explain your problem.

~/❯ mas upgrade                                                                                                                                                                                                                                                                  
Warning: Nothing found to upgrade
~/❯ mas outdated                                                                                                                                                                                                                                                                 
497799835 Xcode (14.1 -> 14.2)
~/❯ mas upgrade                                                                                                                                                                                                                                                                  
Upgrading 1 outdated application:
Xcode (14.1)
==> Downloading Xcode
------------------------------------------------------------ 0.0% Waiting

Additional Context

Add any other context about the problem here.
Did it work in a previous version?

[dalisoft]

@StefanLobbenmeier Maybe it's related to #458?

[StefanLobbenmeier]

Yeah sounds similar, I added a question there to verify