iPad physical device won't open any maui app. (Maui Net8 P7)

[SamuelJames101]

Description

Expected Behavior
The app loads, I see the splash screen, I then see the hello world with the click me button.

Actual Behavior
On my physical device (iPad air 3rd gen 14.6) the app won't open.
https://github.com/dotnet/maui/assets/44027336/808b6375-e251-4cb1-8e51-bb87050f4836
On a simulator (iPad 10th gen 16.4) the app opens but you can't see the splash screen. (I know this issue is fixed by xamarin/xamarin-macios#18777)

Screen.Recording.2023-09-08.at.11.27.33.mov

Additional Info
xCode : 14.3.1
VS for mac : 17.6.3

Steps to Reproduce

1. Create a new Net 8 Preview 7 app
2. Run the app

Link to public reproduction project repository

I just created a brand new project

Version with bug

8.0.0-preview.7.8842

Is this a regression from previous behavior?

Yes, this used to work in .NET MAUI

Last version that worked well

Unknown/Other

Affected platforms

iOS

Affected platform versions

iPad air 3rd Gen OS: 14.6

Did you find any workaround?

No response

Relevant log output

No response

[SamuelJames101]

Re-tested on the release candidate 1 and this issue is still happening. @samhouts is there any update on this as I can't do anything with iPad currently

[mattleibow]

I am looking at this now, but I just wanted to confirm some numbers:

• On my physical device (iPad air 3rd gen 14.6) the app won't open.
• On a simulator (iPad 10th gen 16.4) the app opens

Is the first 14.6 a typo and is the same as the sim with 16.4, or is it a different OS version? If they really are different numbers, does the 14.6 simulator work?

Also, is this a device attached to a Windows machine and using Hot Restart, attached to the mac and using the pair to mac, or using a mac directly?

[mattleibow]

I think it is fixed by this: #17907

[mattleibow]

Seems to be fixed based on the packages from CI after that fix went in. The issue is that there was an iOS 13+ API being used which would crash on older devices - I tested on my iOS 11 iPad and that seems to be the only one. We missed it because ironically the analyzers that we use to detect this stopped working and then all iOS APIs were reported :(

Very, very unfortunate.

[SamuelJames101]

I can confirm this is fixed!