FileProvider macOS xcode16.0 b2

#FileProvider.framework https://github.com/xamarin/xamarin-macios/pull/20890

diff -ruN /Applications/Xcode_16.0.0-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderDomain.h /Applications/Xcode_16.0.0-beta2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderDomain.h
--- /Applications/Xcode_16.0.0-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderDomain.h	2024-05-30 10:38:20
+++ /Applications/Xcode_16.0.0-beta2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderDomain.h	2024-06-14 16:37:14
@@ -235,18 +237,19 @@
  */
 @property (nonatomic, readonly, nullable) NSData *backingStoreIdentity FILEPROVIDER_API_AVAILABILITY_V4_0_IOS;
 
-/** If the domain supports syncing the trash.
+/** Whether the domain supports syncing the trash.
 
- This property only applies for extensions that implement NSFileProviderReplicatedExtension.
+ The system supports syncing a trash folder to the extension.
+ If the domain is configured with supportsSyncingTrash=YES, the system will reparent trashed
+ files (which were located in the extension's domain) to NSFileProviderTrashContainerItemIdentifier.
+ If the domain is configured with supportsSyncingTrash=NO, the system will decide how to handle
+ the trashing operation (not guaranteed by API contract).
 
- Defaults to YES. Set this to NO to indicate that the domain cannot sync the trash.
- If this property is set to YES the system will move the trashed item to the domain trash.
- If this property is set to NO and the trashed item does not have the NSFileProviderItemCapabilitiesAllowsTrashing capability, the system will offer to permanently delete the item.
- If this property is set to NO and the trashed item does have the NSFileProviderItemCapabilitiesAllowsTrashing capability, then the system will behave differently based on whether the item
- is recursively materialized. If the item is fully materialized, it will be moved to the user's home trash and the operation will look like a delete to the extension.
- If the item is not fully materialized, the system will offer to permanently delete the item.
+ This property is only applicable for NSFileProviderReplicatedExtension-based domains.
+
+ This property defaults to YES.
  */
-@property (readwrite, assign) BOOL supportsSyncingTrash FILEPROVIDER_API_AVAILABILITY_V5_0;
+@property (readwrite, assign) BOOL supportsSyncingTrash API_AVAILABLE(macos(13.0), ios(18.0)) API_UNAVAILABLE(watchos, tvos) API_UNAVAILABLE(macCatalyst);
 
 @property (nonatomic, readonly, nullable) NSUUID *volumeUUID FILEPROVIDER_API_AVAILABILITY_EXTERNAL_VOLUME;