The files existed but didn't work—a glitch, now corrected.
For a brief moment, Apple's developer portal appeared to offer a reprieve to owners of older iPad Pro models — restore images for hardware the company had already excluded from iPadOS 27 quietly appeared, then quietly vanished. No installation succeeded, no explanation followed. It was less a promise than a ghost: the residue of old infrastructure momentarily surfacing before being swept back beneath the official record.
- Restore images for unsupported iPad Pro models appeared on Apple's developer downloads page during the first iPadOS 27 beta release, contradicting the official compatibility list.
- Attempts to actually install the files on excluded hardware failed, suggesting the listings were phantom artifacts rather than any real expansion of support.
- The discrepancy raised urgent questions — especially given Apple's recent watchOS 27 reversal, where devices initially excluded were later found to work — fueling speculation that the compatibility list might be revised.
- Apple removed the links without comment, leaving no clarification as to whether this was a portal error or a sign of something unresolved in the beta pipeline.
- The most credible explanation points to legacy grouping logic in Apple's distribution systems carrying forward outdated device categories — old scaffolding outlasting its purpose.
Apple's developer portal briefly listed restore images for iPad Pro models explicitly excluded from iPadOS 27 — specifically the 11-inch 1st and 2nd generations and the 12.9-inch 3rd and 4th generations — before quietly removing them with no explanation. The files appeared during the first beta release, complete with filenames referencing the unsupported hardware, creating an immediate and visible contradiction with Apple's published compatibility list.
The practical test came quickly: a 3rd-generation 12.9-inch iPad Pro refused the installation. The restore image simply wouldn't take, suggesting the files were either incomplete or never meant to be there at all. The episode invited comparison to Apple's recent watchOS 27 situation, where devices initially left off the compatibility list were later found to install successfully — but no such resolution followed here.
Apple did not respond to questions about the discrepancy. The links disappeared, the official list held firm, and silence filled the space where an explanation might have been. Observers pointed to legacy code as the most plausible culprit: older iPad Pro models had historically been bundled together in Apple's build and distribution systems, and that grouping may have carried forward automatically into the beta pipeline, generating files for hardware the new OS no longer supports.
For owners of those older iPad Pros, the episode offered a flicker of possibility that closed as quickly as it opened. The glitch was corrected. iPadOS 27 remains out of reach.
Apple's developer website briefly offered something it shouldn't have: restore images for iPad Pro models that the company had explicitly excluded from iPadOS 27 support. The files appeared on the downloads page for the first beta release, listed under a category for "11-inch iPad Pro (1st and 2nd generations), 12.9-inch iPad Pro (3rd and 4th generations)." The problem was immediate and obvious. Apple's official compatibility announcement had drawn a clear line: iPad Pro models from the M4 generation forward, plus the 12.9-inch 4th generation and 11-inch 2nd generation and later. The older models in the developer downloads didn't make that cut.
When Apple announced iPadOS 27, the company published a straightforward list of which devices would run the new operating system. The M4 iPad Pros and newer were in. The 12.9-inch 3rd generation and the 11-inch 1st generation were not. Yet there on the developer site sat restore image files bearing those exact model numbers, complete with filenames that referenced the unsupported hardware. It was a contradiction that didn't require much digging to spot.
The practical question came next: could these files actually work? A test installation on a 3rd-generation 12.9-inch iPad Pro provided the answer. The installation failed. The restore image wouldn't take. Whatever Apple had listed, it wasn't functional for those older machines. This suggested the files were either incomplete, corrupted, or simply shouldn't have been there at all.
Apple received questions about what had happened. Was this a mistake in the developer portal? Had the official compatibility list been drawn too narrowly, the way Apple had recently done with watchOS 27 and the Apple Watch Series 9—where the company initially said Series 9 wasn't supported, only to have users report successful installations within days? The company did not respond to inquiries. But it did act. Within a short window, Apple removed the restore image links from its developer downloads page. The official compatibility list remained unchanged. No explanation accompanied the removal.
The most likely explanation, according to observers, points to a mundane source of error: legacy code. iPad Pro models had been grouped together in previous iPadOS releases, bundled as a single category in Apple's build and distribution systems. When engineers prepared the iPadOS 27 beta, that same grouping may have carried forward automatically, creating restore images for a broader set of devices than the current compatibility requirements actually supported. It's the kind of mistake that happens when old infrastructure meets new constraints—not malice, not deception, just the friction between what the system was built to do and what it's supposed to do now.
Unlike the watchOS situation, where the discrepancy resolved itself through user reports and eventual clarification, this incident simply closed. The files vanished. Apple said nothing. For users of those older iPad Pro models, the message was clear enough: iPadOS 27 isn't coming for you, and no, that brief window where it looked like it might was not an opening. It was a glitch, now corrected.
Notable Quotes
Apple has not responded to inquiries about whether the restore link was listed by mistake or the compatibility list was incomplete— 9to5Mac reporting
The Hearth Conversation Another angle on the story
So Apple listed files for iPad Pros that don't officially support the new OS. How does that even happen at a company that size?
It's almost certainly not carelessness in the traditional sense. These are probably old code paths—iPad Pro models grouped together in the build system from years back. When they set up the new beta, that grouping just carried forward.
But someone had to notice before it went live, right?
You'd think so. But the developer portal is a massive system with thousands of files. It's possible the discrepancy slipped through, or the person reviewing it didn't catch that specific grouping.
And when they tested it, the installation failed?
Right. So it wasn't even functional. The files existed but didn't work. That's actually what made it clear this was an accident, not a deliberate compatibility decision.
Why not just explain that to users?
That's the question nobody got answered. Apple removed the files and said nothing. Maybe they figured the silence was cleaner than admitting the mistake. Or maybe they're still investigating what went wrong internally.
Does this mean those iPad Pros are definitely stuck on the old OS?
Based on what we know, yes. The official list hasn't changed, and Apple removed the beta files. Unless something shifts, those models won't get iPadOS 27.