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
Potential Issue with copying Large files to temp directory #9
Comments
Reason behind copying to temp directory is that in this case there is no need to handle Android permissions - no permission is required when reading/writing file from app temp dir. Additionally in iOS this copying is performed automatically. Also it could be problematic to get path to file otherwise - file could be in Google Drive or iCloud - what kind of paths to return to Flutter/Dart side in these cases? |
For cloud cases, it can be copied, but leave the other ones optional. I'm
having the issue where my files are being overwritten because they have the
same name. (mmssms.db)even though I'm opening it from different
directories, and I have no way of differentiating them, nor accessing
anything other than the latest file. It's only a slight inconvenience now,
but I do forsee the lack of the option to be a bigger problem for others.
I'd love to submit a pull request, but it would take me too far off my
current focus to figure out how to adjust this.
Thank you for your excellent work so far. This is the next plugin I've
found to get the job done!
… |
Don’t copy the document if you can avoid it. |
Large Files that are copied to temp directory may fill up storage since they're being duplicated. Also, it may not be preferable to copy the files to the temp directory at all times, for example in cases where:
Long story short, can the copying to temp directory be made an optional flag that defaults to true?
The text was updated successfully, but these errors were encountered: