yatli / fvim

Cross platform Neovim front-end UI, built with F# + Avalonia
MIT License
1.33k stars 29 forks source link

macOS app has stuck version information #204

Open vitorgalvao opened 3 years ago

vitorgalvao commented 3 years ago

To accurately display version information, macOS apps need to have the CFBundleVersion and CFBundleShortVersionString tags in Info.plist.

In fvim, the former is unset and the latter is at a fixed 0.01.

If they’re not set during the build process, they can be added after it’s done by directly editing the Info.plist:

# Change these values
app_path='/PATH/TO/APP/HERE'
app_version='VERSION NUMBER HERE'

# Keep these as they are
/usr/libexec/PlistBuddy -c "Add :CFBundleVersion string ${app_version}" "${app_path}/Contents/Info.plist" # Add the missing value
/usr/libexec/PlistBuddy -c "Add :CFBundleShortVersionString string ${app_version}" "${app_path}/Contents/Info.plist" # Update the existing value

That would use the same version number for both fields. Technically they should be different, but that’s a secondary concern. An accurate version number is important for macOS to know which app to open in ambiguous situations; for users who expect the information available via the Finder; and for interoperability with other apps.

core-code commented 1 year ago

i can confirm the issue - still stuck at 0.01

Screenshot 2023-05-11 at 17 32 28
suschizu commented 1 year ago

I can confirm it too - the macOS version information has never changed in the last 2 years … it's not possible to receive any update information for this app