Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue related to re-downloading if file is already present in the cache #20

Closed
bulolo opened this issue Dec 8, 2016 · 1 comment
Closed
Assignees
Labels

Comments

@bulolo
Copy link

bulolo commented Dec 8, 2016

Also, if there is already a file present in the cache directory, VeloxDownloader removes the files and replaces the file.

when i download my file the second time(mean i finished the first file,and press the download button second time):

file1 got deleted : true
file is finished downloading

is this mean the second i download the file,it do not redownload the file from the remote url? instead it just replace the file?

then i reopen the app,the temp file deleted,and the cache file still exist,i press the download btn ,the file download from remote url and replace the file that in the cache file?

is that right above?

@nitinsh99
Copy link
Owner

nitinsh99 commented Dec 8, 2016

Hi @bulolo

Thanks for reporting this. I have identified and fixed the issue in version 1.6. Now downloading will occur every time and will either create a new file or will replace the existing file if it's present in the cache. Please download the version 1.6 of the VeloxDownloader.

put following in your PodFile.
pod 'VeloxDownloader', '~> 1.6'
and run pod update from terminal

Along with this I have also fixed an issue related to VeloxDownloader UI so if you want to try that you can see it in action by cloning and running this project.

git clone https://github.com/nitinsh99/VeloxDownloader.git
Please verify and let me know so we can close this issue.

@nitinsh99 nitinsh99 changed the title error? Issue related to re-downloading if file is already present in the cache Dec 8, 2016
@nitinsh99 nitinsh99 self-assigned this Dec 8, 2016
@nitinsh99 nitinsh99 added the bug label Dec 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants