Description
Occasionally you might see that Jamf Now lists the incorrect version for a Custom Mac app you uploaded. For example, the values in the screenshot are not the correct versions.
This happens because Jamf Now pulls the version number from the info.plist in the .pkg file; however, if one is not included in the package, Jamf Now will assign the package a version of 1.0 or 1.0.[xxxxxx].
Manually Adjusting the Package Version with Composer
Using Jamf Composer, we can manually adjust the version information on the info.plist.
Drag and drop the package into the Sources column on the left in Composer.
Click the > button next to the package name in the Source column.
Click the > button next to Settings and click the info.plist.
Enter in the version numbers in the IF Major version and IF Minor version fields. Ignore Bundle Version and Version fields.
Click File in the menu bar and click Save.
Click Composer in the menu bar and click Preferences. Ensure the box for Sign with is checked and a valid certificate from an Apple Developer Program account is selected.
For more information, see Building and Signing Packages in the Jamf Now documentation.
Click Build as PKG.
Upload the new package to Jamf Now following the steps below.
Click Apps and click + Add an App.
Click Upload Your App.
Drag and drop the .pkg file or click browse to upload the .pkg file.
Give the app a name and click Done.
The numerical values entered in the Major and Minor version fields now will be presented in the Version field under the package name.
Add the app to a blueprint to deploy.