Why this matters
Aviation device management has many moving parts — Apple hardware, iPad model, iOS versions, MDM platforms, and the apps running on top. We want to help you keep it all running smoothly, so this guide shares our best advice on managing your devices and the Reader App reliably.
Some of this is outside of Web Manuals' control, especially when Apple releases a new major iOS update. We work quickly to test and confirm compatibility — but there will always be a short window while we catch up. A disciplined update process on your end is the best protection, and that is what this guide is here to support.
Compatibility
The Reader App depends on a specific relationship between the app version, iOS, and the iPad model running it. Older iPad models have a maximum supported iOS version and may not be able to run the latest Reader App — even if everything else is up to date.
As a general rule, if your iPad cannot support an iOS version within 2-3 major versions of the current compatible iOS, it is time to consider upgrading the device.
- Refer to the list of devices available via Apple’s website.
- For specific cut-off versions, refer to the compatibility article in the Help Centre.
The core principle: never update iOS or the Reader App in isolation without checking compatibility first — and confirm your iPad model supports the iOS version you intend to update to.
The core principle: never update iOS or the Reader App in isolation without checking compatibility first — and confirm your iPad model supports the iOS version you intend to update to.
MDM users — Control your updates
We recommend disabling the Reader App set to auto-update. Auto-update means any new app version goes live on all devices the moment it hits the App Store, regardless of whether compatibility has been confirmed.
Instead:
- Disable auto-update via your MDM platform
- Hold a stable app version across your fleet until you are ready to update
- Test on one device before pushing to all devices
- Update one variable at a time — either iOS or the app, not both simultaneously
Not on MDM (e.g. ABM, Jamf Pro, ScaleFusion, Hexnode) yet? If you manage a fleet of devices, speak to your IT administrator about whether MDM is the right fit. It is the most reliable way to maintain version consistency across all devices.
Before you update iOS
- Check the Help Centre for the latest major iOS compatibility report.
- Confirm the iOS version you plan to update to has been validated against the current Reader App version.
- If no compatibility report is available yet, hold the update and contact Web Manuals Support before proceeding.
- Test on a single device first before rolling out to your full fleet.
Stay on a consistent version across your fleet
When all devices run the same Reader App and iOS version, your team gets a predictable, stable experience — documents load the same way for everyone, issues are easier to isolate, and Support can diagnose problems faster.
Version fragmentation happens when different crew members or pilots run different versions of the app or iOS on their devices. This creates inconsistent behaviour, makes troubleshooting harder, and can mean some users cannot access documents that others can.
- Keep all devices on the same Reader App version at all times
- Keep all devices on the same iOS version at all times
- When contacting Support about an issue, ask the user to Export their Device Log (Profile settings → Application Settings → Export Device Logs) and send it to them as an attachment. This speeds up diagnosis significantly.
After any update — Run this check
- Open the Reader App and confirm it loads online without error
- Open a published document and confirm pages load correctly
- Verify that all your Operationally Critical Documents are can be downloaded
- If your operation relies on offline access, confirm documents are available without a network connection
- Confirm acknowledgement and review functions are working as expected
- If anything is not working, export the device log and contact Support before rolling out to the rest of the fleet
SSO best practices for the Reader App
If your organisation uses Single Sign-On (SSO) via Microsoft Entra ID (Azure AD), there are a few things to be aware of before your crew takes devices offline mid-flight.
How it works offline
SSO requires an internet connection to authenticate. Once logged in, a token is stored on the device that keeps the session active — this is what allows the app to work offline. If that token expires while offline and there is no connection to renew it, the pilot will be prompted to enter their passcode to continue accessing the app.
This token expiry is controlled by your organisation's Microsoft Entra ID configuration, not by Web Manuals. Speak to your IT administrator if you need to adjust how long sessions stay active.
Best practices
Always log in to the Reader App on Wi-Fi before boarding. Download or update any required documents while connected, then switch to offline mode for the flight. Server connection points may be unavailable while airborne, so everything your crew needs should be cached before departure.
Every pilot must set up their personal passcode in the Reader App before going offline. This is the fallback login method when SSO cannot reach the authentication server. Go to Profile settings in the app to set this up.
If a pilot has never set a passcode and their token expires mid-flight, they will not be able to log in. Make passcode setup a mandatory step during device onboarding.
IT admins — check your Entra ID session token and refresh token lifetime settings. The longer the refresh token remains active, the less likely pilots are to be interrupted by re-authentication prompts during or between flights.
A note on security
SSO token lifetimes are a balance between security and usability. Your IT administrator or Microsoft Entra ID configuration controls this — Web Manuals recommends coordinating with your IT team to find a session length that works for your flight roster without compromising your security policy.