我在让我的应用显示为 iOS 11 文件应用中的位置时遇到了一些问题。我添加了一个 NSFileproviderExtension
。但是,当我运行它时,我只能选择 safari 和其他一些应用程序。当我选择 safari,然后关闭 safari,打开文件时,它确实显示了我的扩展名,但是当我单击任何内容时它崩溃了。关于最好的方法的任何想法?有什么好的教程吗?
@interface FileProviderExtension ()
@property (nonatomic, readonly, strong) NSFileManager *fileManager;
@end
@implementation FileProviderExtension
- (instancetype)init {
if (self = [super init]) {
_fileManager = [[NSFileManager alloc] init];
}
return self;
}
- (nullable NSFileProviderItem)itemForIdentifierNSFileProviderItemIdentifier)identifier errorNSError * _Nullable *)error {
// resolve the given identifier to a record in the model
// TODO: implement the actual lookup
NSFileProviderItem item = nil;
return item;
}
- (nullable NSURL *)URLForItemWithPersistentIdentifierNSFileProviderItemIdentifier)identifier {
// resolve the given identifier to a file on disk
NSFileProviderItem item = [self itemForIdentifier:identifier error:NULL];
if (!item) {
return nil;
}
// in this implementation, all paths are structured as <base storage directory>/<item identifier>/<item file name>
NSFileProviderManager *manager = [NSFileProviderManager defaultManager];
NSURL *perItemDirectory = [manager.documentStorageURL URLByAppendingPathComponent:identifier isDirectory:YES];
return [perItemDirectory URLByAppendingPathComponent:item.filename isDirectory:NO];
}
- (nullable NSFileProviderItemIdentifier)persistentIdentifierForItemAtURLNSURL *)url {
// resolve the given URL to a persistent identifier using a database
NSArray <NSString *> *pathComponents = [url pathComponents];
// exploit the fact that the path structure has been defined as
// <base storage directory>/<item identifier>/<item file name> above
NSParameterAssert(pathComponents.count > 2);
return pathComponents[pathComponents.count - 2];
}
- (void)startProvidingItemAtURLNSURL *)url completionHandlervoid (^)(NSError *))completionHandler {
// Should ensure that the actual file is in the position returned by URLForItemWithIdentifier:, then call the completion handler
/* TODO:
This is one of the main entry points of the file provider. We need to check whether the file already exists on disk,
whether we know of a more recent version of the file, and implement a policy for these cases. Pseudocode:
if (!fileOnDisk) {
downloadRemoteFile();
callCompletion(downloadErrorOrNil);
} else if (fileIsCurrent) {
callCompletion(nil);
} else {
if (localFileHasChanges) {
// in this case, a version of the file is on disk, but we know of a more recent version
// we need to implement a strategy to resolve this conflict
moveLocalFileAside();
scheduleUploadOfLocalFile();
downloadRemoteFile();
callCompletion(downloadErrorOrNil);
} else {
downloadRemoteFile();
callCompletion(downloadErrorOrNil);
}
}
*/
completionHandler([NSError errorWithDomain:NSCocoaErrorDomain code:NSFeatureUnsupportedError userInfo{}]);
}
- (void)itemChangedAtURLNSURL *)url {
// Called at some point after the file has changed; the provider may then trigger an upload
/* TODO:
- mark file at <url> as needing an update in the model
- if there are existing NSURLSessionTasks uploading this file, cancel them
- create a fresh background NSURLSessionTask and schedule it to upload the current modifications
- register the NSURLSessionTask with NSFileProviderManager to provide progress updates
*/
}
- (void)stopProvidingItemAtURLNSURL *)url {
// Called after the last claim to the file has been released. At this point, it is safe for the file provider to remove the content file.
// TODO: look up whether the file has local changes
BOOL fileHasLocalChanges = NO;
if (!fileHasLocalChanges) {
// remove the existing file to free up space
[[NSFileManager defaultManager] removeItemAtURL:url error:NULL];
// write out a placeholder to facilitate future property lookups
[self providePlaceholderAtURL:url completionHandler:^(NSError * __nullable error) {
// TODO: handle any error, do any necessary cleanup
}];
}
}
#pragma mark - Actions
/* TODO: implement the actions for items here
each of the actions follows the same pattern:
- make a note of the change in the local model
- schedule a server request as a background task to inform the server of the change
- call the completion block with the modified item in its post-modification state
*/
#pragma mark - Enumeration
- (nullable id<NSFileProviderEnumerator>)enumeratorForContainerItemIdentifierNSFileProviderItemIdentifier)containerItemIdentifier errorNSError **)error {
id<NSFileProviderEnumerator> enumerator = nil;
if ([containerItemIdentifier isEqualToString:NSFileProviderRootContainerItemIdentifier]) {
// TODO: instantiate an enumerator for the container root
} else if ([containerItemIdentifier isEqualToString:NSFileProviderWorkingSetContainerItemIdentifier]) {
// TODO: instantiate an enumerator for the working set
} else {
// TODO: determine if the item is a directory or a file
// - for a directory, instantiate an enumerator of its subitems
// - for a file, instantiate an enumerator that observes changes to the file
}
return enumerator;
}
@end
由于某种原因,Xcode 不会显示 Files 应用程序来调试您的 NSFileproviderExtension
。
无论如何要测试它,只需选择任何其他应用程序,在该应用程序中搜索“共享”按钮,然后在共享屏幕中选择"file"。 您还可以关闭应用程序并转到文件,您的扩展程序将在其中显示应用程序并进行调试(断点、控制台消息等)。
对于崩溃,添加一个异常断点以在导致崩溃的代码行处停止(就像调试主程序时所做的那样)。
关于iOS 模拟器不显示文件应用程序作为 NSFileproviderExtension 的选项,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/46454839/
欢迎光临 OStack程序员社区-中国程序员成长平台 (https://ostack.cn/) | Powered by Discuz! X3.4 |