Thank you for your quick answers, @eskimo!
Post
Replies
Boosts
Views
Activity
Hi @clenart,
Do you happen to have a look at this yet?
Thank you for your answer, @clenart! We've deployed the fixes to our backend, but I'm still not seeing enumerateChanges triggered, even though PushKit is logging that there's a push coming in for .fileProvider.
The log is now FileProvider::pushDelegate::didReceiveIncomingPush PKPushTypeFileProvider [AnyHashable("container-identifier"): NSFileProviderRootContainerItemIdentifier]
I'm using a real device, with the debugger attached, when running from Xcode. Should I just archive a build and drag it to my iPhone from Finder instead, or should it just work? Or should the container-identifier JSON be wrapped in the aps key as well? That's not clear to me from documentation.
Hi @clenart,
I'm not setting a domain, no. If I look at the above log, I'm seeing "" = "{\"container-identifier\":\"NSFileProviderRootContainerItemIdentifier\"}";, is that maybe the issue? Because as far as I can tell, the container-identifier should be the JSON key instead of a JSON object in the value.
However, I'm not certain of this, as the documentation page mentions:
{
container-identifier = "<identifier>"
domain = "<domain identifier>"
}
Which, to me, doesn't look like valid JSON. Should it also be wrapped in the aps dictionary?
Hi @clenart,
Thank you for your response! I am talking about the iOS FileProvider extension, so that probably helps give you some context. I've got a few questions in the meantime:
Do I need to implement sync anchors for a MVP version of the FileProvider extension? If I don't override the two relevant methods in my enumerator, I notice that my new folders are duplicated when still editing their name.
Do I have to implement workingSet for a MVP version, or can I just release a version of the extension without working set?
Is the FileProvider Validation iPad app still available somewhere?
Is there any way to get in touch with the FileProvider team? I didn't get the answers I needed from the code-level incident I created.