In addition to an issue we previously reported in which "hiding" Jamf Trust results in broken device connectivity due to ODCF, we have identified two related issues. We are working directly with Apple to investigate and validate potential recovery scenarios.
1. Jamf Trust App Updates May Cause Connectivity Loss
An intermittent issue may cause the Jamf Trust app update to hang and result in a loss of internet connectivity.
Conditions to trigger the issue (all must apply):
-
Device is running iOS 26.1 and is configured with ODCF vectoring.
-
The Jamf Trust app is being updated.
-
The device is on an unstable or poor network connection (though this may not always be required).
Outcome:
-
The app installation process hangs indefinitely
-
The device loses internet connectivity, which is not restored even after a reboot
-
Note: This issue occurs intermittently. In most cases, the update succeeds even when all conditions are met.
2. Zero Trust Network Access (ZTNA) Functionality Is Also Affected by “Hiding” Jamf
The original “hiding” issue also impacts devices configured for ZTNA.
Conditions to trigger the issue (all must apply):
-
The device is running iOS 26.1 and is configured with ZTNA vectoring.
-
The Jamf Trust app is hidden via MDM, Screentime, or Kiosk/Single App mode (same conditions as the original issue reported on 11/17)
Outcome:
-
ZTNA continues to function normally until the device is rebooted or VPN is manually disabled in device settings.
-
Once disabled or rebooted, ZTNA cannot be re-enabled by the user.
-
Unlike the ODCF issue, the device retains network connectivity but cannot access resources protected by ZTNA.
-
When Jamf Trust is "unhidden," the VPN does not start automatically.
Note: The behavior can be inconsistent. In some instances, the VPN disconnects immediately when Jamf Trust is hidden and reconnects when it is unhidden.
For additional questions and needs, please log in to Jamf Account with your Jamf ID and click Contact Support in the upper right-hand corner to get help. To reference the original issue that was discovered, see this this announcement.
