-
Notifications
You must be signed in to change notification settings - Fork 548
FileProvider iOS xcode26.0 b5
Alex Soto edited this page Aug 5, 2025
·
2 revisions
#FileProvider.framework
diff -ruN /Applications/Xcode_26.0.0-beta4.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderModifyItemOptions.h /Applications/Xcode_26.0.0-beta5.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderModifyItemOptions.h
--- /Applications/Xcode_26.0.0-beta4.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderModifyItemOptions.h 2025-07-11 05:04:02
+++ /Applications/Xcode_26.0.0-beta5.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderModifyItemOptions.h 2025-07-25 02:52:22
@@ -6,24 +6,29 @@
#import <FileProvider/NSFileProviderDefines.h>
+/// Options for modifying items.
typedef NS_OPTIONS(NSUInteger, NSFileProviderModifyItemOptions) {
- /**
- We're moving the item to a location where it may refer to an item that already exists. This may happen
- when two directories are being merged together. When this happens some items may be merged to the
- same directory and we end up in a situation where the merged contains may also exist.
-
- This is similar to NSFileProviderCreateItemMayAlreadyExist
- */
+ /// An option that indicates the changes may already exist in your remote storage.
+ ///
+ /// This option applies when moving the item to a location where it may refer to an item that already exists.
+ /// This situation may occur when merging two directories together.
NSFileProviderModifyItemMayAlreadyExist = 1 << 0,
- /**
- If the base version of the item trying to be uploaded doesn't match
- the version of the file on server, the call to modifyItem should fail with a
- NSFileProviderErrorLocalVersionConflictingWithServer error.
- */
+ /// An option to fail an upload in the event of a version conflict.
+ ///
+ /// If you adopt this option, and an uploaded item's base version doesn't match the version on the server, fail and return ``NSFileProviderError/localVersionConflictingWithServer`` (Swift) or ``NSFileProviderErrorCode/NSFileProviderErrorLocalVersionConflictingWithServer`` (Objective-C) in your implementation of `modifyItem`.
+ ///
+ /// To support the fail-on-conflict behavior in your file provider, indicate the support by adding the following key/value pair to the extension's Info pane.
+ ///
+ /// ```
+ /// <key>NSExtension</key>
+ /// <dict>
+ /// <key>NSExtensionFileProviderSupportsFailingUploadOnConflict</key>
+ /// <true/>
+ /// </dict>
+ /// ```
NSFileProviderModifyItemFailOnConflict FILEPROVIDER_API_AVAILABILITY_SYNC_CONTROLS = 1 << 1,
- /**
- The upload needs to be completed before the completionHandler gets called
- in order to let the calling application know when the version is on server.
- */
+ /// An option to require the upload to complete before calling the completion handler.
+ ///
+ /// This option allows the calling application to know when the uploaded version of the file is on the server.
NSFileProviderModifyItemIsImmediateUploadRequestByPresentingApplication FILEPROVIDER_API_AVAILABILITY_SYNC_CONTROLS = 1 << 2,
} FILEPROVIDER_API_AVAILABILITY_V3_IOS;