Hi everyone,
We are testing Apple's native MDM migration flow. When we accidentally push an expired/past timestamp for the mdm_migration_deadline, identical test devices behave inconsistently:
• Device 1: Immediately triggers the migration flow.
• Device 2: Automatically shifts the on-screen countdown timer to exactly 30 minutes in the future.
• Device 3 (Flight Mode): Bypasses the lockout while offline, but acts erratically once reconnected.
What is the hardcoded framework fallback when a device parses an already-expired deadline? Has anyone else seen the OS dynamically generate this 30-minute grace window?
Thanks!