Skip to content

Conversation

@nlutsenko
Copy link
Contributor

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why was this async before? Wasn't it to ensure that all the progress block ticks finished?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, not really... It was attached to PFTaskQueue vs PFAsyncTaskQueue, which was safer to use with async APIs.
It's no longer needed. downloadAsync already performs on the background thread, so there is basically no need to do this scheduling here.

nlutsenko added a commit that referenced this pull request Aug 29, 2015
Cleaned up implementation, added nullability annotations for PFFile.m
@nlutsenko nlutsenko merged commit e8a0362 into master Aug 29, 2015
@nlutsenko nlutsenko deleted the nlutsenko.file.cleanup branch August 29, 2015 00:19
@nlutsenko nlutsenko added this to the 1.8.3 milestone Sep 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants