v8.1.0 crash while backup: General - Api Clients / Roles AND macOS - Patch Management

[PeterPlanlos]

If selected General - Api Clients / Roles
or macOS - Patch Management

the application "quit unexpectedly"

Just while "export only" so no migration just saving backup to disk from jamf cloud.

please fix, thanks a lot!

[BIG-RAT]

Give v8.1.1 a go, worked fine for me.

[PeterPlanlos]

Thanks for updating but it dont work for me. :(
I feel its even got worse.

still
macOS - Patch Management -> starts then after some -> the application "quit unexpectedly"
macOS - Applications -> dont start + hang for ever
macOS - Disk Encryptions -> dont start + hang for ever

General - Api Clients / Roles -> only work if selected separately(both are working when selected separately). if select one of both together with something other -> the application "quit unexpectedly"

thanks in advance that you take care. I would love to get a fully working version because I use this as backup for my Jamf cloud instance

Best regards

[BIG-RAT]

2 steps forward, 3 steps back...
Let me know if v8.2.0 improves things.

[dev-yeet]

this seems to be happening for jamf pro users and groups as well if exporting. it seems to export the very first one (user or group), and then immediately crashes. i can view all the users or groups in the app no problem, but once I try to export is when it crashes.

[BIG-RAT]

@dev-yeet - having the issue with v8.2.0? I'm unable to reproduce the error (yet?) myself.
Export only or replicate and export?
Raw and/or trimmed?
Can you share the log?

[PeterPlanlos]

Hi it still crash for me macOS / Patch Management
all the other stuff is running through flawless for me.

Tried: General and macOS tab.
only macOS / Patch Management seems affected for me.

Tested now again explicit only General / Users & Jamf Groups & Jamf Users & Smart User Group & Static User Groups =>
no issue run smooth through. I use export only not trimmed if this matters.

Best regards and thanks for working on it!!

[dev-yeet]

20250929_125551 [Credentials.itemLookup] lookup error occurred for JPMA-redacted.jamfcloud.com: -25300
20250929_125551 [Credentials.itemLookup] lookup error occurred for JPMA-redacted.jamfcloud.com: -25300
20250929_125551 [Credentials.itemLookup] lookup error occurred for JPMA-redacted.jamfcloud.com: -25300
20250929_125556 [Credentials.itemLookup] lookup error occurred for JPMA-redacted.jamfcloud.com: -25300
20250929_125603 [go] Using username/password to generate token for source: redacted.jamfcloud.com.
20250929_125603 [JamfPro.getToken] Token for source server is 15 hours old. Expires in 15 minutes
20250929_125603 [JamfPro.getToken] Attempting to retrieve token from https://redacted.jamfcloud.com/api/v1/auth/token
20250929_125603 [JamfPro.getToken] using username/password to generate token for source server
20250929_125603 [JamfPro.getToken] new token created for source: https://redacted.jamfcloud.com
20250929_125604 [JamfPro.getToken] getVersion: source Jamf Pro Version: 11.20.1-t1757338337687
20250929_125604 [JamfPro.getToken] getVersion: https://redacted.jamfcloud.com set to use Bearer Token
20250929_125604 [updateServerArray] set current source server: https://redacted.jamfcloud.com
20250929_125604 [go] Using username/password to generate token for destination: keycard.jamfcloud.com.
20250929_125604 ----------- Starting Export Only -----------

20250929_125604 [ViewController.readNodes] successfully set access permissions to /Users/johnnybrown/dev/replicator/Client Configuration Templates/jamf-pro-users-and-groups/
20250929_125604 [getSourceEndpoints] nodesToMigrate: ["jamfusers"]
20250929_125604 [Json.getRecord] get endpoint: jamfusers from server: https://redacted.jamfcloud.com
20250929_125604 [Json.getRecord] GET status code: 200
20250929_125604 [Json.getRecord] retrieved jamfusers
20250929_125637 [go] Using username/password to generate token for source: redacted.jamfcloud.com.
20250929_125637 [JamfPro.getToken] Token for source server is 33 seconds old. Expires in 15 minutes
20250929_125637 [JamfPro.getToken] Attempting to retrieve token from https://redacted.jamfcloud.com/api/v1/auth/token
20250929_125637 [JamfPro.getToken] using username/password to generate token for source server
20250929_125637 [JamfPro.getToken] new token created for source: https://redacted.jamfcloud.com
20250929_125637 [JamfPro.getToken] getVersion: source Jamf Pro Version: 11.20.1-t1757338337687
20250929_125637 [JamfPro.getToken] getVersion: https://redacted.jamfcloud.com set to use Bearer Token
20250929_125637 [JamfPro.renewToken] Source server token renews in 15 minutes
20250929_125637 [updateServerArray] set current source server: https://redacted.jamfcloud.com
20250929_125637 [go] Using username/password to generate token for destination: keycard.jamfcloud.com.
20250929_125637 ----------- Starting Export Only -----------

20250929_125637 [startMigrating] call selectiveMigrationDelegate for selectedEndpoint: accounts/userid
20250929_125637 [Json.getRecord] get endpoint: jamfusers/10 from server: https://redacted.jamfcloud.com
20250929_125638 [Json.getRecord] GET status code: 404
20250929_125638 [Json.getRecord] error getting jamfusers//10, HTTP Status Code: 404
20250929_125638 [ViewController.startSelectiveMigration] update redacted_user accounts/userid dependency
20250929_125639 [getById] Exporting raw XML for accounts/userid - redacted_user

for what it's worth, the user exported actually is userid 10

i was doing raw only, but i also tried with trimmed for logs above and there's no difference.

[BIG-RAT]

Interesting, I get a similar 404 response but the record exports

20251002_101506 [startMigrating] call selectiveMigrationDelegate for selectedEndpoint: accounts/userid
20251002_101506 [Json.getRecord] get endpoint: jamfusers/25 from server: https://SourceServer
20251002_101507 [Json.getRecord] GET status code: 404
20251002_101507 [Json.getRecord] error getting jamfusers//25, HTTP Status Code: 404

[hotrodmac]

8.6.0 Crashes on Patch Management titles. We don't use sites in our instance, and looking at the logs it dies when trying to get site information.

20260302_090215 [- debug -] [readSettings(thePath:)] settingsPath: /Users/redacted/Library/Containers/com.jamf.jamf-migrator/Data/Library/Application Support/Replicator/settings.plist
20260302_090215 [- debug -] [ViewController.startMigrating] migrating/removing 1 sections
20260302_090215 [- debug -] [ViewController.startMigrating] Starting to process patch-software-title-configurations
20260302_090215 [- debug -] [ViewController.startMigrating] getting endpoint: patch-software-title-configurations
20260302_090215 [- debug -] [ViewController.readNodes] enter search for patch-software-title-configurations
20260302_090215 [- debug -] [ViewController.readNodes] getting endpoint: patch-software-title-configurations
20260302_090215 [- debug -] [ViewController.readNodes] Bookmark Access Failed for /Users/redacted/Library/Containers/com.jamf.jamf-migrator/Data/Downloads/Replicator/
20260302_090215 [- debug -] [ViewController.readNodes] /Users/redacted/Library/Containers/com.jamf.jamf-migrator/Data/Downloads/Replicator/ is writable
20260302_090215 [- debug -] [getSourceEndpoints] nodesToMigrate: ["patch-software-title-configurations"]
20260302_090215 [- debug -] [ViewController.getSourceEndpoints] Getting patch-software-title-configurations
20260302_090219 [- debug -] [Jpapi.get] response statusCode: 200
20260302_090219 [- debug -] [getEndpoints] found 31 patch objects on the source server
20260302_090219 [- debug -] [ViewController.getSourceEndpoints] Found total of 31 patch-software-title-configurations to process
20260302_090219 [- debug -] [ExistingObjects.capi] enter - destination endpoint: patch-software-title-configurations
20260302_090219 [- debug -] [ExistingObjects.capi] exit - save only enabled, endpoint: patch-software-title-configurations not needed.
20260302_090219 [- debug -] [getEndpoints] fetch patch management dependencies from source server
20260302_090219 [- debug -] [getEndpoints] fetching category records from source server
20260302_090219 [- debug -] [getAllDelegate] lastPage: false, whichPage: 0, whichServer: source server, theEndpoint: categories.
20260302_090220 [- debug -] [Jpapi.pagedGet] response statusCode: 200
20260302_090220 [- debug -] [Jpapi.getAll] total records fetched 44 objects
20260302_090220 [- debug -] [getEndpoints] fetching site records from source server
20260302_090220 [- debug -] [Jpapi.action] attempting GET on https://SourceServer/api/v1/sites
20260302_090220 [- debug -] [Jpapi.action] Data retrieved from https://SourceServer/api/v1/sites.
20260302_090220 [- debug -] [getEndpoints] fetching policy-details records from source server
20260302_090220 [- debug -] [getAllDelegate] lastPage: false, whichPage: 0, whichServer: source server, theEndpoint: policy-details.
20260302_090221 [- debug -] [Jpapi.pagedGet] response statusCode: 200
20260302_090221 [- debug -] [Jpapi.getAll] total records fetched 16 objects
20260302_090221 [- debug -] [getAllDelegate] lastPage: false, whichPage: 0, whichServer: source server, theEndpoint: packages.
20260302_090222 [- debug -] [Jpapi.pagedGet] response statusCode: 200
20260302_090222 [- debug -] [Jpapi.getAll] total records fetched 268 objects
20260302_090222 [- debug -] [getEndpoints] fetching category records from dest server
20260302_090222 [- debug -] [getAllDelegate] lastPage: false, whichPage: 0, whichServer: dest server, theEndpoint: categories.
20260302_090222 [- debug -] [getEndpoints] fetching site records from dest server
20260302_090222 [- debug -] [Jpapi.action] attempting GET on /api/v1/sites
20260302_090222 [- debug -] [Jpapi.action] GET response error.  Verify url and port.

[BIG-RAT]

I'm curious, does the account you're using have permissions to read sites?

[hotrodmac]

It does. That was one of the first things I checked. On Mar 2, 2026, at 17:32, Leslie Helou ***@***.***> wrote:BIG-RAT left a comment (jamf/Replicator#123) I'm curious, does the account you're using have permissions to read sites? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[BIG-RAT]

What version of Jamf Pro are you using. If it's not the most current (or close to it) I'm wondering if the endpoint doesn't exist in the Pro API, only classic.

[hotrodmac]

I’ve double-checked that my api client has permissions to read sites. I’ve tested on both 11.21 and 11.25 versions of Jamf pro with the same behavior. Looking at the Swagger API docs for both versions, unless I’m missing something, it appears they have the same patch and sites endpoints in the Pro API. On Mar 3, 2026, at 08:06, Leslie Helou ***@***.***> wrote:BIG-RAT left a comment (jamf/Replicator#123) What version of Jamf Pro are you using. If it's not the most current (or close to it) I'm wondering if the endpoint doesn't exist in the Pro API, only classic. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[BIG-RAT]

Haven't been able to replicate the issue yet. Wonder if you could run the following, checks /api/v1/sites using an API client.
It's not to pretty but I'd be interested in the results (barring the token).

#!/bin/zsh

jamfUrl="https://<your.jamfPro.instance>"
tokenURL="$jamfUrl/api/v1/auth/token"

endpoint="/api/v1/sites"

: <<'COMMENT_BLOCK'
## using username / password
echo -n "Enter Jamf Admin name: "
read user

echo -n "Enter password for $user: "
stty -echo
read pass
stty echo
echo 

## fetch token
response=$(curl -s -w "\n%{http_code}" -u "$user:$pass" $tokenURL -X POST)
COMMENT_BLOCK

echo -n "Enter API client: "
read cliendId

echo -n "Enter ssecret for $cliendId: "
stty -echo
read clientSecret
stty echo
echo 

## fetch token
response=tokenRequest=$(curl -s -w "\n%{http_code}" \
--request POST "${jamfUrl}/api/oauth/token" \
--header "Content-Type: application/x-www-form-urlencoded" \
--header 'accept: application/json' \
--data-urlencode "client_id=$cliendId" \
--data-urlencode "grant_type=client_credentials" \
--data-urlencode "client_secret=$clientSecret"
)

http_code=$(tail -n1 <<< "$response") 	# status code --> last line
echo "token: status code: $http_code"
content=$(sed '$ d' <<< "$response")	# get all but last line
echo "token content: $content"

## if using username / password
#bearerToken=$(echo "${content}" | jq -r .token)

## if using client / secret
json="${content#tokenRequest=}"
bearerToken=$(jq -r '.access_token' <<< "$json")
echo 

## get endpoint
response=$(curl -s -w "\n%{http_code}" -X 'GET' \
"${jamfUrl}${endpoint}" \
-H 'accept: application/json' \
-H "Authorization: Bearer $bearerToken")

http_code=$(tail -n1 <<< "$response")
echo "$endpoint status code: $http_code"
content=$(sed '$ d' <<< "$response")
echo "$endpoint: $content"
echo 

## invalicate token
response=$(curl -s -w "\n%{http_code}" -X 'POST' \
"${jamfUrl}/api/auth/invalidateToken" \
-H 'accept: application/json' \
-H "Authorization: Bearer $bearerToken")

http_code=$(tail -n1 <<< "$response")
echo "invalidate status code: $http_code"
content=$(sed '$ d' <<< "$response")
echo "invalidate content: $content"

[hotrodmac]

Looks like I get the same output on both systems:On my 11.21 system I get:token: status code: 200token content: tokenRequest={“access_token”:”[token value]”,”scope”:”[api role ids]”,”token_type”:”Bearer”,”expires_in”:499}/api/v1/sites status code: 200/api/v1/sites: [ ]invalidate status code: 204invalidate content: On my 11.25 system I get:token: status code: 200token content: tokenRequest={“access_token”:”[token value]”,”scope”:”[api role ids]”,”token_type”:”Bearer”,”expires_in”:499}api/v1/sites status code: 200api/v1/sites: [ ]invalidate status code: 204invalidate content:On Mar 3, 2026, at 20:39, Leslie Helou ***@***.***> wrote:BIG-RAT left a comment (jamf/Replicator#123) Haven't been able to replicate the issue yet. Wonder if you could run the following, checks /api/v1/sites using an API client. It's not to pretty but I'd be interested in the results (barring the token). #!/bin/zsh jamfUrl="https://<your.jamfPro.instance>" tokenURL="$jamfUrl/api/v1/auth/token" endpoint="/api/v1/sites" : <<'COMMENT_BLOCK' ## using username / password echo -n "Enter Jamf Admin name: " read user echo -n "Enter password for $user: " stty -echo read pass stty echo echo ## fetch token response=$(curl -s -w "\n%{http_code}" -u "$user:$pass" $tokenURL -X POST) COMMENT_BLOCK echo -n "Enter API client: " read cliendId echo -n "Enter ssecret for $cliendId: " stty -echo read clientSecret stty echo echo ## fetch token response=tokenRequest=$(curl -s -w "\n%{http_code}" \ --request POST "${jamfUrl}/api/oauth/token" \ --header "Content-Type: application/x-www-form-urlencoded" \ --header 'accept: application/json' \ --data-urlencode "client_id=$cliendId" \ --data-urlencode "grant_type=client_credentials" \ --data-urlencode "client_secret=$clientSecret" ) http_code=$(tail -n1 <<< "$response") # status code --> last line echo "token: status code: $http_code" content=$(sed '$ d' <<< "$response") # get all but last line echo "token content: $content" ## if using username / password #bearerToken=$(echo "${content}" | jq -r .token) ## if using client / secret json="${content#tokenRequest=}" bearerToken=$(jq -r '.access_token' <<< "$json") echo ## get endpoint response=$(curl -s -w "\n%{http_code}" -X 'GET' \ "${jamfUrl}${endpoint}" \ -H 'accept: application/json' \ -H "Authorization: Bearer $bearerToken") http_code=$(tail -n1 <<< "$response") echo "$endpoint status code: $http_code" content=$(sed '$ d' <<< "$response") echo "$endpoint: $content" echo ## invalicate token response=$(curl -s -w "\n%{http_code}" -X 'POST' \ "${jamfUrl}/api/auth/invalidateToken" \ -H 'accept: application/json' \ -H "Authorization: Bearer $bearerToken") http_code=$(tail -n1 <<< "$response") echo "invalidate status code: $http_code" content=$(sed '$ d' <<< "$response") echo "invalidate content: $content" —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>