You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
yes, they are different. They needed to change to support new features.
v1.1 has been deployed and ran successfully with this LaunchDaemon on literally thousands of devices across many organizations. We would need more than "it fails to run" to figure out what is wrong with your deployment. log would be helpful.
Are you certain it installs? there was a bug in Jamf Pro 11.11.x where packages wouldn't get the md5 hash and then not install during prestage?
For support questions, I generally recommend joining the #jamf-setup-manager channel in the MacAdmins Slack. (Free signup here.)
Hi, thanks for the reply. Yes.. the app installs ok. instance is latest JAMF cloud.. there are no logs.. the log file is created, but it's empty. By fails to run, I mean with the beta.. this launches as expected.. and runs through the config profile settings, with 496.. the pkg installs.. but it does not launch.. the only difference here is the pkg that is installed.. if I add the beta to prestage it works.. if I add 496.. it doesn't run..
Bit more info after discussion on MacAdmins Slack. Problem occurs on Intel VM (in VMware Fusion Pro) with macOS 15.x. I thought I understood what but then could recreate the issue on my Intel VM with macOS 15.2.
Testing will occur on physical devices to further isolate the issue.
I have beta 455 working fine.
deploying 1.1 - 496 and it fails to run, its installed ok.
I note that the launch deamon plists that are installed are different..
455
496
The text was updated successfully, but these errors were encountered: