Skip to content

FileProvider macOS xcode13.1 rc

Alex Soto edited this page Oct 26, 2021 · 4 revisions

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

diff -ruN /Applications/Xcode_13.0.0-beta5.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderEnumerating.h /Applications/Xcode_13.1.0-rc.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderEnumerating.h
--- /Applications/Xcode_13.0.0-beta5.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderEnumerating.h	2021-08-05 00:17:19.000000000 -0400
+++ /Applications/Xcode_13.1.0-rc.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderEnumerating.h	2021-09-10 01:07:36.000000000 -0400
@@ -84,10 +84,9 @@
 - (void)didDeleteItemsWithIdentifiers:(NSArray <NSFileProviderItemIdentifier> *)deletedItemIdentifiers;
 
 /**
- Call the following method every so often while sending changes, particularly
- while enumerating changes to NSFileProviderWorkingSetContainerItemIdentifier.
- If the device reboots during an enumeration, it would later resume starting
- at the latest known sync anchor.
+ This method is used to complete a batch of changes. Follow the advice
+ in -[NSFileProviderChangeObserver suggestedBatchSize] to determine when to
+ call this method.
 
  It is expected that the sync anchor passed here be different than the sync
  anchor that the enumeration started at, unless the client was already up to
@@ -123,8 +122,12 @@
  it split the list of changes into several batches. If the enumerator does not have suggestedBatchSize ready to
  enumerator, the enumerator should finish immediately and not wait for more incoming changes to enumerate.
 
- By taking into account the suggested size, the enumeration will guarantee the best user experience possible. The
- system enforces a maximum of 100 times the suggested size.
+ By taking into account the suggested size, the enumeration will guarantee the best user experience possible. Large
+ batches can cause performance issues. And when the device reboots, enumerations will resume from the latest
+ known sync anchor. Telling the system about the latest sync anchor more frequently will reduce the number
+ of re-enumerations on system reboot.
+
+ The system enforces a maximum of 100 times the suggested size.
  */
 @property (nonatomic, readonly) NSInteger suggestedBatchSize FILEPROVIDER_API_AVAILABILITY_V3;
 
Clone this wiki locally