Skip to content
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

macOS app has missing version information #223

Closed
vitorgalvao opened this issue Oct 22, 2021 · 3 comments
Closed

macOS app has missing version information #223

vitorgalvao opened this issue Oct 22, 2021 · 3 comments

Comments

@vitorgalvao
Copy link

Describe the bug

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

In XaoS, the keys are missing.

To Reproduce

Inspect XaoS.app/Contents/Info.plist and verify the keys are missing.

Expected behavior

App should have versions.

Screenshots

N/A

Desktop (please complete the following information):

  • OS: macOS
  • Browser: N/A
  • Version: Any

Smartphone (please complete the following information):

N/A

Additional context

Alternatively to setting versions 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"
/usr/libexec/PlistBuddy -c "Add :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.

@core-code
Copy link

i can reproduce the issue. any fix forthcoming?

@kanurag94
Copy link
Member

@vitorgalvao Thanks for reporting. I was also able to reproduce the issue. I'll try to fix this in next minor release

@kanurag94
Copy link
Member

Closing since this will be tracked on #210
Kindly reopen if this is still an issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants