FileProvider iOS xcode16.0 b3

#FileProvider.framework

diff -ruN /Applications/Xcode_16.0.0-beta2.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderDomain.h /Applications/Xcode_16.0.0-beta3.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderDomain.h
--- /Applications/Xcode_16.0.0-beta2.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderDomain.h	2024-06-14 16:37:14
+++ /Applications/Xcode_16.0.0-beta3.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderDomain.h	2024-06-29 08:50:55
@@ -239,7 +239,10 @@
 
 /** Whether the domain supports syncing the trash.
 
- The system supports syncing a trash folder to the extension.
+ The system supports syncing a trash folder (NSFileProviderTrashContainerItemIdentifier) to the extension.
+ On iOS, this is surfaced to the user as "Recently Deleted" in the Files app. On macOS, this is surfaced
+ to the user as the Trash in Finder.
+
  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
diff -ruN /Applications/Xcode_16.0.0-beta2.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderManager.h /Applications/Xcode_16.0.0-beta3.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderManager.h
--- /Applications/Xcode_16.0.0-beta2.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderManager.h	2024-06-14 18:35:22
+++ /Applications/Xcode_16.0.0-beta3.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderManager.h	2024-06-28 23:34:14
@@ -250,11 +250,12 @@
 /**
  Calling this method will cause the system to cancel throttling on every item which has been throttled due to the given error.
 
- This call supports 4 types of errors:
+ This call supports the following errors:
  - NSFileProviderErrorNotAuthenticated
  - NSFileProviderErrorInsufficientQuota
  - NSFileProviderErrorServerUnreachable
  - NSFileProviderErrorCannotSynchronize
+ - NSFileProviderErrorExcludedFromSync
  */
 - (void)signalErrorResolved:(NSError *)error completionHandler:(void(^)(NSError *_Nullable error))completionHandler
 FILEPROVIDER_API_AVAILABILITY_V3_IOS;
diff -ruN /Applications/Xcode_16.0.0-beta2.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderReplicatedExtension.h /Applications/Xcode_16.0.0-beta3.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderReplicatedExtension.h
--- /Applications/Xcode_16.0.0-beta2.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderReplicatedExtension.h	2024-06-14 16:32:03
+++ /Applications/Xcode_16.0.0-beta3.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderReplicatedExtension.h	2024-06-28 23:34:14
@@ -547,12 +547,12 @@
  collision, by renaming one of the colliding items. When the collision is resolved,
  the system will call createItemBasedOnTemplate again.
 
- The extension can also report the NSFileProviderErrorNotAuthenticated,
- NSFileProviderErrorServerUnreachable, NSFileProviderErrorInsufficientQuota
- or NSFileProviderErrorCannotSynchronize in case the modification cannot be applied
- because of the current state of the system / domain. In that case, the system will
- present an appropriate error message and back off until the next time it is signalled.
- The provider can signal the error resolution by calling signalErrorResolved:completionHandler:.
+ The extension can also report NSFileProviderErrorNotAuthenticated,
+ NSFileProviderErrorCannotSynchronize, or NSFileProviderErrorExcludedFromSync,
+ in case the modification cannot be applied because of the current state of the
+ system / domain. In that case, the system will present an appropriate error message
+ and back off until the next time it is signalled. The provider can signal the error
+ resolution by calling signalErrorResolved:completionHandler:.
 
  Any other error, including crashes of the extension process, will be considered to be transient
  and will cause the creation to be retried.
@@ -724,12 +724,12 @@
  the colliding items. When the collision is resolved, the system will call
  modifyItem again.
 
- The extension can also report the NSFileProviderErrorNotAuthenticated,
- NSFileProviderErrorServerUnreachable, NSFileProviderErrorInsufficientQuota
- or NSFileProviderErrorCannotSynchronize in case the modification cannot be applied
- because of the current state of the system / domain. In that case, the system will
- present an appropriate error message and back off until the next time it is signalled.
- The provider can signal the error resolution by calling signalErrorResolved:completionHandler:.
+ The extension can also report NSFileProviderErrorNotAuthenticated,
+ NSFileProviderErrorCannotSynchronize, or NSFileProviderErrorExcludedFromSync,
+ in case the modification cannot be applied because of the current state of the
+ system / domain. In that case, the system will present an appropriate error message
+ and back off until the next time it is signalled. The provider can signal the error
+ resolution by calling signalErrorResolved:completionHandler:.
 
  Any other error, including crashes of the extension process, will be considered to be transient
  and will cause the modification to be retried.