I am also experiencing precisely the same problem after installing the offical Xcode 10 release. I read in a forum post that this was related to Intel 4000 chip set.
Device ‘iPad Pro (12.9-inch) (2nd generation)’ not in list of available simulators
I was hoping someone would know what to do with this error I am receiving after running fastlane snapshot I do have the iPad Pro (12.9-inch) (both generations) in the simulator list but somehow it isn’t picked up when calling fastlane snapshot.
How iPad Apps Adapt to the New 11″ and 12.9″ iPads Pro
This is the latest in a series of articles explaining how iOS and Watch apps appear when run on hardware that didn’t exist when they were designed and built. On 30th October 2018, Apple announced two new iPads with Face ID, edge-to-edge LCD screens and no home button. Older apps running on the new hardware effectively see two new screen resolutions that don’t match any previous or new devices. As a reference, here’s how an Xcode 10.0 / iOS 12.0 app appears on the 10.5″ and 1st/2nd generation 12.9″ iPad Pro devices at their native resolution:
The 9.7″ and 10.5″ iPads Pro show a compact-width Slide Over app with a width of 320 points (640 pixels) in both landscape and portrait. Apps that were built with Xcode 10.0 or earlier (i.e. targeting iOS 12.0 or earlier) are unaware of the existence of the new 11″ iPad Pro screen size or a 12.9″ iPad Pro with a Home Indicator (instead of a Home Button).
In order to maintain a 4:3 aspect ratio, the app is also inset on the left and right edges. Instead of scaling to fit, older apps that do support multitasking (which effectively declares them as somewhat adaptive) appear in a Compatibility Mode with a screen size that doesn’t match earlier devices or the full size of the new devices.
The status bar and Home Indicator are still outside of the screen area that the app occupies. As we will see later, this is actually due to an increase in height of the status bar from 20 to 24 points (40 to 48 pixels) on these devices.
This happens even though the status bar is not actually part of the app’s screen area in this special compatibility mode! Again, the status bar and Home Indicator are not part of the app’s screen, resulting in a height that is unlike any previous device:
A 50:50 split on the 11″ iPad still gives two regular-width apps, but the actual widths are different (to fill the wider screen): Old apps running on the new 12.9″ iPad also have reduced height to account for the status bar and Home Indicator. When built with Xcode 10.1 (i.e. linked against iOS 12.1), apps get access to the full 11″ and 12.9″ screen sizes of the new devices. The status bar is the same height as in compatibility mode (24 points) but is now part of the app’s screen area.
The toolbar (and tab bar) are 20 points taller to leave space for the Home Indicator: In one of its new developer videos, Apple warn that both apps in split screen will be forced into compatibility mode if either of them have not been updated to support the new devices.
In a deviation from the norm, Apple have designed the new 11″ and 12.9″ iPads Pro to behave in an almost backwardly-compatible manner for multitasking-capable apps that were built with Xcode 10.0 or earlier. Even apps that use auto layout and have launch storyboards will be shown in this compatibility mode.
Apps that do not support multitasking ( UIRequiresFullScreen is set to YES in the Info.plist ) will retain their 10.9″ or 10.5″ effective resolution and be inset to avoid the status bar and Home Indiciator.
Apple have been warning developers not to make assumptions about bar sizes for several years. Their existing Xcode 10.0 builds will work (at a slightly unusual and never-before-seen resolution) on the newer devices. Rebuilding with Xcode 10.1 will take advantage of the full screen size of the new iPads and avoid the Home Indicator.
On the other hand, apps which aren’t adaptive, assume bar heights or screen sizes, are possibly going to have some layout problems. In a change from previous years and devices, running existing multitasking-capable apps on the new iPads will result in different behaviour. My earlier article iPad Navigation Bar and Toolbar Height Changes in iOS 12 explains the process in the Wait, What Did You Say?
I have also written about External Display Support on iOS and Working with Multiple Versions of Xcode.
If you work with a lot of Xcode projects you might like my Mac Menu Bar utility XcLauncher.
Apple says you can build apps on an iPad now, but devs say the reality is trickier
We didn’t get many of those dream features, but we did get something of a surprise: Apple announced Swift Playgrounds 4, the newest version of its Swift Playgrounds sandbox, a program Apple SVP Craig Federighi claimed will bring “a whole new dimension of productivity to iPad.” It was a quick announcement that was easy to miss in the flurry of new tools that crossed the stage. Tucker Haas, co-founder and CEO of the finance app Quo, who has built over a dozen iOS applications, feels similarly: “When I was first learning to program iOS apps over 10 years ago, it was a daunting task full of hurdles just to get the development environment set up,” he tells me.
As Verge writer Paul Miller argued back in 2018, such a program would give new coders who got their footing through Swift Playgrounds a way to graduate into “true application developers” without having to buy a new device.
“Swift Playgrounds is great for experimenting and debugging code, but it is missing many of the features … required to make fuller-fledged apps,” Haas explains.
He says the program is “perfect for developing small utility applications, such as a to-do list, but currently incapable of building the next Angry Birds.” And for some developers, the convenience of the iPad’s form factor is outweighed by the limitations of its software — which persist, despite the new power of its chips.
All this stuff is still more convenient on the desktop.” And of course, plenty of programs developers use on Macs, like code analyzers, debugging tools, and system profilers, aren’t yet available for iPadOS. Many people I spoke to were excited by the real-time preview function, which can help users visualize their code as they’re writing it and present it to clients and collaborators in a more accessible format.
Wagner plans to use it to “iterate on features in isolation — that is, write components on iPad and bring them into larger Xcode projects.” “I could see myself writing an app on the side,” says Cory Bohon, another MartianCraft engineer who uses a Mac for work, but an iPad Pro as his personal device. “I treat the new feature as an important first step towards bringing Xcode to the iPad,” says Vira Tkachenko, CTO of MacPaw. It looks inevitable with the M1 processors on Macs, and Apple is gradually laying the groundwork for merging macOS and iOS.” Tkachenko tells me she “can’t wait to see real Xcode on iPad.”
After all, the iPad has hardware that makes up for the MacBook Air’s greatest weaknesses, and plenty of Big Sur’s features would take good advantage of its touchscreen capability.
AARAV
He holds a Master of Science in Chemistry from the Indian Institute of Technology, Bombay.
[Xcode 11] Missing iPad Pro (12.9-inch) (2nd generation) on iOS 13
It is quite critical as Apple still requires Screenshots specific to the iPad Pro (12.9-inch) (2nd generation) and downgrading to the previous stack is not an option because of external dependencies.
Be First to Comment