Dumb question as someone new to iPad-apps-running-on-Apple-Silicon dev, is this a bug or am I doing something wrong here? Lots of users are reporting a crash in Apollo now, and it seems tied to this line of code when run on Apple Silicon.
Well, if you can prevent it from being installed on macOS systems before Monterey Id have expected Apple to have thought about this.
Can you not specify a minimum macOS version in the store/plist, if you allow it to run on Apple Silicon Macs?
Probably a bug, was able to reproduce this in a sample project as well. File a feedback, please?
Thanks, was curious what the right check was
Ah missed that, but either way it seems like the property is not available in the version thats crashing. (Also happens when APIs are added midway through the beta cycle). The process info check is probably a safe bet.
Oh-em-g. I had this *exact* bug today. Still wondering what the right solution is! Im running Big Sur, I thought maybe if I run it on Monterey the env will be iOS 15 somehow, and it will execute properly?
To be clear this fixes it, but should I be boxing all next-OS calls in it so that people on previous versions of macOS don`t encounter it? i think that confirms the theory, honestly. in objective c you could use respondsToSelector: to dynamically check if that function resolves
Have you tried on Monterey?
Its marked as Mac Catalyst 15.0+ which means its only available on Monterrey or higher. Since that SDK is not in Xcode 13 RC youre best of using a if targetEnvironment(macCatalyst) to prevent this line from compiling for Catalyst.
Should this line of code be running at all based on your availability check? Monterrey isnt out yet.
I know ran into some sort of crash on Apple Silicon Macs with Overcasts most recent update. Curious if this is related and if so what the fix was.
I wonder if iOS 15 apps dont run on macOS without Monterey?
