-
Notifications
You must be signed in to change notification settings - Fork 273
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
Some apps are always shown as outdated even though they're already the latest version (CFBundleShortVersionString vs. CFBundleVersion) #384
Comments
I also get this for Not sure if these should go in separate issues as application specific or if it's a general |
@lougreenwood I don't know either and at least in the case of Ninja Cookie the short version is just 0.7, so perhaps that the confusion. |
Yep, I get the same, even immediately after installing the app. ↪️ mas search "ninja cookie"
1535219336 Ninja Cookie (0.7.1)
↪️ mas info 1535219336
Ninja Cookie 0.7.1 [0.0]
By: Theo GOUDOUT
Released: 2021-05-14
Minimum OS: 10.14
Size: 4 MB
From: https://apps.apple.com/us/app/ninja-cookie/id1535219336?mt=12&uo=4
↪️ mas purchase 1535219336
==> Downloading Ninja Cookie
==> Installed Ninja Cookie
↪️ mas outdated
1535219336 Ninja Cookie (0.7 -> 0.7.1) |
Sorry. There have been a handful of annoying issues like this since we fixed the Noticed that both the version numbers in the <key>CFBundleShortVersionString</key>
<string>0.7</string>
<key>CFBundleVersion</key>
<string>0.7.1</string> |
Great that you can reproduce @phatblat. I think that the issue can have two fold fixes…
|
I recently fixed the case where the bundle version is newer than the App Store version. This is the opposite case. We don't have a way to get the bundle version from the App Store without downloading the app again every time we want to check for the latest release. We could heuristically parse both |
I'm still seeing this myself with |
It seems this plan isn't going to work, as As things are today, using only
However, using the greater of
Unfortunately, more reports of the problem aren't helping us reach a solution. We understand the cause of the problem, but we need a viable proposal for how to address it in order to move forward. Perhaps there's some investigation to be done into the private CommerceKit and StoreFoundation that might shed some light on this sort of versioning discrepancy? Maybe some magic to |
I have the same issues with:
Running e.g. |
I get a current version of 1Blocker reported as outdated: I would like to highlight this, as I didn't see this mentioned yet: I'm on 12.0.1 on Apple Silicon, so also some apps from the iOS store are installable, but not 1Blocker. |
I've summarized this in the Known Issues section of the README. Additional reports of apps with mismatched app bundle versions are unfortunately not helpful at this point. Pull requests are welcome! |
Out of interest (and yes I have my own persistent list of apps that are always getting updated), I also use CleanMy Mac and it's updater list generally has the correct versions for the same two apps, could be worth asking them how they get updated version lists? |
I had this issue with Zentuner, where it would upgrade every time $ mas outdated
1550640624 ZenTuner (0.2.0 -> 0.2.2) The workaround was to edit ...
<key>CFBundleShortVersionString</key>
<string>0.2.0</string>
... and and the value to |
See Feature Request #468 $ mas outdated $ mas-versions 1550640624 |
Your Environment
mas version
: 1.8.2system_profiler SPSoftwareDataType -detailLevel mini
): 11.3.1 (20E241)mas Install Method
brew install mas
(homebrew-core).pkg
installer from releasesDescribe the Bug
Ninja Cookie gets updated from 0.7 to 0.7.1, but if I run
mas upgrade
it updates again becausemas outdated
still show it as outdated. On other words, just seem that or mas is not able to read the version of the app properly, or the app doesn't states its version properly. I think it's the latter one.To Reproduce
Steps to reproduce the behavior:
mas outdated
ormas upgrade
Expected Behavior
Detect the version properly?
Actual Behavior
Upgrade, upgrade, upgrade
Additional Context
Perhaps it would be great to have a pin command or ignore this version or something.
The text was updated successfully, but these errors were encountered: