Eventual consistency: `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): 13.0.1 (22A400)

mas Install Method

brew install mas (homebrew-core)

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

$ 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

[dalisoft]

@StefanLobbenmeier Maybe it's related to #458?

[StefanLobbenmeier]

Yeah sounds similar, I added a question there to verify

[rgoldberg]

This might be resolved when #560 is implemented. I haven't yet observed any differences from my test implementation of #560, but I have a few other test ideas to determine if there are any other differences. I will be working on other, more concrete issues before I can get back to this, so it might be a bit before I know if #560, or if anything similar, will work.