You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hiya - thanks for the plugin, this looks great. Right now, the flow I have in my app is that I attempt to share the file, and let the user choose what to do with it from the share picker. I think it would make more sense to copy to the Downloads folder (using this plugin!) and then offer the share prompt. However, to do this, I need to get a reference or a file path to the now-saved file within the Downloads folder. But alas, this plugin has the nice helpful feature of renaming files in case of a filename conflict. So if the file is saved multiple times, the share dialog would share the first version repeatedly. Would it be possible to return the copied file path instead of just a boolean success value?
The text was updated successfully, but these errors were encountered:
Hi There- I completely agree this is a valuable improvement. I’ll work on updating the plugin to return the final file path (or URI) instead of a boolean...I’ll aim to implement this in the next few weeks.
Cheers!
Hiya - thanks for the plugin, this looks great. Right now, the flow I have in my app is that I attempt to share the file, and let the user choose what to do with it from the share picker. I think it would make more sense to copy to the Downloads folder (using this plugin!) and then offer the share prompt. However, to do this, I need to get a reference or a file path to the now-saved file within the Downloads folder. But alas, this plugin has the nice helpful feature of renaming files in case of a filename conflict. So if the file is saved multiple times, the share dialog would share the first version repeatedly. Would it be possible to return the copied file path instead of just a boolean success value?
The text was updated successfully, but these errors were encountered: