Here are some potential solutions to resolve this issue:
Check Device Policy: Since the device is in device owner mode, ensure that the device policy settings allow for the required permissions to persist after a reboot.
Auto-grant Permissions: Some enterprise mobility management (EMM) solutions, like Meraki, have options to automatically grant permissions to certain apps. Make sure these settings are correctly configured.
OEM Settings: Some OEMs might have additional settings or restrictions regarding permission management. Check if there are any Samsung-specific settings that might be causing this.
Update Meraki SM App: Ensure you are using the latest version of the Meraki SM app. Sometimes, app updates include bug fixes for issues like this.
Android 14 Compatibility: Since you are using Android 14, there might be compatibility issues with the Meraki SM app. Check for any known issues or updates from Meraki regarding Android 14 compatibility.
Re-provision Device: As a last resort, re-provisioning the device might help in resetting any configurations that might be causing the issue.
To provide more specific guidance, I would need additional details, such as:
- Whether this issue is occurring on multiple devices or just a single device.
- If there are any custom configurations or policies applied to the device that might affect permissions.
