jamf/Setup-Manager
1
0
Fork 0
mirror of https://github.com/jamf/Setup-Manager.git synced 2026-02-03 14:13:24 +00:00
Code Issues 37 Actions Packages Projects Releases Wiki Activity

[BUG]: Setup Manager 1.4 | "Setup Manager only supports Jamf solutions" not shown in UI when running in debug mode #7

New Issue
Closed
opened 2026-01-19 18:31:13 +00:00 by michael · 1 comment
michael commented 2026-01-19 18:31:13 +00:00
Owner
Copy Link

Originally created by @philipross on GitHub.

Issue summary:

Debug mode not allowing Setup Manager to run in User space, and not showing messaging about only supporting Jamf solutions in UI.

Workarounds:

Either deploy the simulateMDM key in your Setup Manager profile, or run Setup Manager as root with sudo.

Issue details:

When running Setup Manager in DEBUG mode, the UI does not render the Setup Manager only supports Jamf Solutions messaging if Setup Manager is run in the user space.

In the same scenario, running Setup Manager as root via sudo "/Applications/Utilities/Setup Manager.app/Contents/MacOS/Setup Manager" - the UI works as expected, and the carousel of actions is shown.

Looking in the Setup Manager logs, there's an error linked to the user space run attempt of MDM detected as unknown, whereas it's correctly detecing the MDM when run as root.

The issue appears to be that the error messaging is not loading correctly when run in debug mode in user space.
When running the same scenario using Setup Manager 1.3, I do indeed get the messaging about only supporting Jamf solutions.

Originally created by @philipross on GitHub. ## Issue summary: Debug mode not allowing Setup Manager to run in User space, and not showing messaging about only supporting Jamf solutions in UI. ## Workarounds: Either deploy the `simulateMDM` key in your Setup Manager profile, or run Setup Manager as root with sudo. ## Issue details: When running Setup Manager in `DEBUG` mode, the UI does not render the `Setup Manager only supports Jamf Solutions` messaging if Setup Manager is run in the user space. In the same scenario, running Setup Manager as root via `sudo "/Applications/Utilities/Setup Manager.app/Contents/MacOS/Setup Manager"` - the UI works as expected, and the carousel of actions is shown. Looking in the Setup Manager logs, there's an error linked to the user space run attempt of `MDM detected as unknown`, whereas it's correctly detecing the MDM when run as root. The issue appears to be that the error messaging is not loading correctly when run in debug mode in user space. When running the same scenario using Setup Manager 1.3, I do indeed get the messaging about only supporting Jamf solutions.
michael added the bug label 2026-01-19 18:31:13 +00:00
michael commented 2026-01-19 18:31:13 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

please test with 1.4.1 release

@scriptingosx commented on GitHub: please test with [1.4.1 release](https://github.com/jamf/Setup-Manager/releases/tag/v1.4.1)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
duplicate
enhancement
enhancement
question
Support
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
michael
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#7
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?