Manually resume URLSessionTask after it has been successfully registered #301
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We introduced with #293 the progress reporting for Download & Upload for WebDAV. However, it seems like the FileProviderExtension doesn't like when one registers a already running URLSessionTask and this could trigger
EXC_RESOURCE RESOURCE_TYPE_MEMORY. Somehow registering and then resuming the task seem to fix this issue (and thus closing #299)… which is a bit unexpected but the documentation inside the header file of NSFileProvideManager (but not the online documentation) also states:So I guess we are interacting now a bit more according to the specifications.