Has there been a resolution to this issue? We are still experiencing it. Doesn't seem to cause problems... but it should be resolved none the less... if provider.hasItemConformingToTypeIdentifier(UTType.url.identifier) { provider.loadItem(forTypeIdentifier: UTType.url.identifier, options: nil) { item, _ in ... } } -[_EXSinkLoadOperator loadItemForTypeIdentifier:completionHandler:expectedValueClass:options:] nil expectedValueClass allowing {( NSMutableArray, NSNumber, NSMutableString, NSURL, NSMutableData, _EXItemProviderSandboxedResource, NSDictionary, NSArray, NSUUID, NSMutableDictionary, CKShare, NSDate, NSValue, NSData, NSString, UIImage, NSError )}