CVPixelBufferAttributes.AllocateWithIOSurface and MetalCompatibility are unavailable on macOS

[jeremy-visionaid]

Apple platform

macOS

Framework version

net10.0-*

Affected platform version

10.0.102

Description

CVPixelBufferAttributes.AllocateWithIOSurface and MetalCompatibility are not exposed on the macOS TFM, but they are available upstream:

https://developer.apple.com/documentation/corevideo/kcvpixelbuffermetalcompatibilitykey?language=objc
https://developer.apple.com/documentation/corevideo/kcvpixelbufferiosurfacepropertieskey?language=objc

Steps to Reproduce

N/A

Did you find any workaround?

        CVPixelBufferAttributes attributes = new();
        attributes.Dictionary.SetValueForKey(NSNumber.FromBoolean(true), new NSString(CVPixelBuffer.MetalCompatibilityKey));
        attributes.Dictionary.SetValueForKey(NSNumber.FromBoolean(true), new NSString(CVPixelBuffer.IOSurfacePropertiesKey));

Relevant log output

No response

[jeremy-visionaid]

On behalf of @tuanchien

[jeremy-visionaid]

@rolfbjarne Looks to me like MetalCompatibilityKey should be:

		[iOS(8, 0), MacCatalyst (13, 1), Mac(10, 11), TV(9, 0)]
		[Field ("kCVPixelBufferMetalCompatibilityKey")]
		NSString MetalCompatibilityKey { get; }

		[SupportedOSPlatform ("ios")]
		[SupportedOSPlatform ("maccatalyst")]
		[SupportedOSPlatform ("macos")]
		[SupportedOSPlatform ("tvos")]
		public bool? MetalCompatibility {
			set {
				SetBooleanValue (CVPixelBuffer.MetalCompatibilityKey, value);
			}
			get {
				return GetBoolValue (CVPixelBuffer.MetalCompatibilityKey);
			}
		}

I'd put in a PR, but I'm not sure about why the MONOMAC guard is there

[rolfbjarne]

Looks like AllocateWithIOSurface's macOS exclusion is due to a merge conflict that was incorrectly resolved over a decade ago.

MetalCompatility is probably because it was introduced on iOS first (and thus excluded from macOS), and then we just never updated the code when it was added to macOS.

In any case a fix is in progress.