[Solved] 'metal' added to 'Required Device Capabilities' in info.plist

Hello!

After updating to Unity 2019.3.5f1, the latest XCode builds have the flag "metal" in the "Required Device Capabilities" dictionary in info.plist together with armv7, which causes the ipa to be rejected by Apple.

How can I control which flags are added from Unity? Is there a flag / option that forces Unity to add the flag in the info.plist?

Thank you for your help

 

Removing "Auto Graphic API" and setting BOTH

• Metal
• OpenGL 2 (Deprecated)

solved the issue apparently

 

It works for me as well and I hope there aren't any side-effects.
I have spent the last hours trying to solve this and there are no information to be found. So vague.
It's like fumbling in the dark trying to grab a needle with boxing gloves.
Thank you!

 

@mylastggColto

Would you mind sharing the rejection message and reason Apple gave? Although it makes sense that all Metal devices are arm64 capable, but they are also armv7 capable (according to https://developer.apple.com/support/required-device-capabilities/). I'm very curious why Apple is very stringent on this.

 

@Neonlyte

I'm attaching a screenshot of the warning, Xcode won't let me copy and paste.

Btw this happens ONLY if you already have live builds. Apple does not want you to change the required device capabilities of existing apps, they claim you should pick them at first and be able to support them for the rest of the app's life (https://developer.apple.com/library/archive/qa/qa1623/_index.html).

Important: Because you can't add UIRequiredDeviceCapabilities restrictions after an app is in the store, be sure to plan ahead by choosing requirements you will be comfortable supporting indefinitely going forward.

Our previous build only had armv7 as a requirement and Apple is not happy that now I am also adding metal on top of that.

This is usually no problem, but when Unity changes the output of the info.plist from one version to another under the hood, this can happen.

 

Oh that just made me sick, Apple themselves does not have a good track record on app support cycle (but I don't have evidence that they violated this rule themselves).

Thank you for sharing this, I am just planning rewriting my project with new technologies and dropping support for all the non-metal devices. I guess the way to go is to just bump the min-iOS version to iOS 11.

 

https://developer.apple.com/library/archive/qa/qa1623/_index.html

Just to extend on this topic. It seems that Apple are happy with developer bumping the min iOS version, but does not allow requirements to be changed to match the devices that can run that minimum version of iOS. Sounds to me like a legacy issue of how they process the apps

 

This works for me. Thanks!!