NinjaOne Apple MDM: Troubleshooting Apps and Books Sync Issues

Issue

I added a new application (app) via Apple Business Manager (ABM), but it is not syncing to NinjaOne.

Environment

• NinjaOne Apple Mobile Device Management (MDM)
• Apple iOS

Cause

When a newly added app in ABM fails to appear in the Apps and Books in NinjaOne (via the linked content token), it generally indicates a sync failure or misconfiguration. 

Resolution

The steps below outline how to isolate and diagnose your issues efficiently.

Error Visibility: Does a Sync Error Occur?

In theory, NinjaOne should surface a sync error or failure message when the content token fails to pull updated app data from ABM. However, in practice, not all sync failures produce actionable errors; some issues may go undetected by NinjaOne.

Key Consideration

A lack of a visible error does not confirm a successful sync. If a new app doesn't appear, treat it as a potential silent sync failure or a per-app sync anomaly.

Step-by-Step Troubleshooting Workflow

1. Validate ABM app configuration:
   1. Ensure the app is assigned to the correct location in ABM that corresponds to the content token in NinjaOne.
   2. Verify that licenses are actually assigned to that location for the app in question.
   3. Confirm the app supports platforms compatible with NinjaOne MDM (iOS, iPadOS, macOS). Apps that are not supported on these platforms will not appear in NinjaOne.
2. Test token sync behavior to isolate whether the issue is token-wide or app-specific:
   1. In ABM, add or remove a different app or modify license quantities for an existing app within the same content token's Location.
   2. Trigger a manual sync in NinjaOne for the content token.
   3. Observe if the change reflects in NinjaOne.

If the unrelated app or license change syncs, this indicates the token is syncing correctly. The issue is specific to the one app.

If the unrelated changes also don't sync, this indicates the entire content token may be failing, even if no sync error is shown.