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.
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
To accurately display version information, macOS apps need to have the
CFBundleVersion
andCFBundleShortVersionString
tags inInfo.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
: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.