Open mykyta-bondarenko opened 5 years ago
Looks like it behave like SupportedVideoFormats
(in PR#5348), i.e. in .NET both the static calls are, by default, identical.
We have been hit by this many times, we really need to bring generator support for this... manual inlining is not optimal by any means :/
I just tested this with the iPhone 5S in the simulator and I can confirm that: ARConfiguration.isSupported returns true ARWorldTrackingConfiguration.isSupported returns false when they should both be false. The documentation states: "Important
All ARKit configurations require an iOS device with an A9 or later processor." It appears that some devices(5S) have partial ARKit support and that could be what you are seeing here?
https://github.com/SerialForBreakfast/ARKitARConfigTest
This is also the case for ARFaceTrackingConfiguration
and all the other configurations that inherits from ARConfiguration (https://developer.apple.com/documentation/arkit/configuration_objects).
Native they implement their own IsSupported
but does not expose it in the interface, hence Xamarin fails to generate link to each configuration type.
Steps to Reproduce
AppDelegate.cs
filesExpected Behavior
The output is the same for both
Actual Behavior
The output is different
Environment
Build Logs
Example Project
https://github.com/xamarin/xamarin-macios/files/2860457/TestAR.zip