Will ManagdWALplus work on new iPad hardware and OS versions?
The Short Answer: Yes.
ManagdWALplus is built using Apple’s most fundamental and stable programming APIs, ensuring a high degree of compatibility with new iPad hardware and future iPadOS versions.
Our Policy and Caveats
We are committed to updating the app for all major and minor iPadOS releases. However, compatibility with brand-new hardware or a major new OS version (e.g., iPadOS 19.0) may not be available on Day 1 of its public release, as adapting the app requires dedicated development and quality assurance time.
Caveat: When Apple Changes the Rules
In rare instances (which have occurred before), Apple restricts or removes core programming functions that our app relies on, often for security or privacy reasons.
When this happens, we are forced to develop a workaround. Depending on the complexity of the change, this process typically takes 4 to 8 weeks to fully develop, test, and release a stable update. These issues typically arise during major OS updates (X.0 releases). While we have always found solutions, we cannot offer a 100% guarantee that compatibility issues will never temporarily arise following a significant OS change.
How You Can Help
Your cooperation is highly valued. By singling out the most important OS versions for your fleet, you help us focus our development and quality assurance resources where they matter most to you. We greatly appreciate any testing and issue reports you provide.
Key Takeaway and Advice
- Maintain Strict Version Control: Please keep your iPad fleet under strict iPadOS version management.
- Report Issues: No matter how much we test internally, you may find unexpected issues. Please do not hesitate to contact the Helpdesk at Royal Cloud Solutions with any testing reports or inqueries.
- Read Release Notes Carefully: Newer versions may require you to adapt your XML scripts and the use of the app. Release notes – Royal Cloud Solutions
Example of an Adaptation: A recent case involved Apple removing the function that allowed the app to automatically find the device’s name for privacy reasons. To adapt, we were required to update the XML setup (transferred from your EMM/UEM) to include a dedicated field where the device ID is explicitly provided, please see: Setting alternative device name. This ensures the device can continue to report essential health and state information.