To accurately display version information, macOS apps need to have the CFBundleVersion and CFBundleShortVersionString tags in Info.plist.
Therm has them, but they’re set to unknown (literally that string, CFBundleGetInfoString is the same).
If versions aren’t 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 "Set :CFBundleVersion string ${app_version}" "${app_path}/Contents/Info.plist"
/usr/libexec/PlistBuddy -c "Set :CFBundleShortVersionString string ${app_version}" "${app_path}/Contents/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.
To accurately display version information, macOS apps need to have the
CFBundleVersion
andCFBundleShortVersionString
tags inInfo.plist
.Therm has them, but they’re set to
unknown
(literally that string,CFBundleGetInfoString
is the same).If versions aren’t 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.