saveFile method implemented for android platform #1396
Conversation
This file contains hidden or 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
now the saveFile method for android uses the fileName as input file from where it reads the content to be written in the file that the user is going to choose. this way there is no need to ask for permission and no need to delete the 0 byte file created by the save filePicker window. From the android app ONLY you need to write the file in a temporary file before calling the saveFile() method. then you pass the temp file to the saveMethod(), the user choose the file where the content of the temp file will be saved and the temp file is written to the file chosen by the user
miguelpruivo
added
improvement
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I implemented a saveFile method for the android platform because I needed it.
I don't know if it is interesting, I think that you already know how to do it but maybe violates some android security rule and that's the reason why you didn't add it.
If this is the case just ignore it.
The only way I found to implement the method is by removing the file that the saveFile dialog creates because that file cannot be written by the calling thread. By removing the 0 length created file and returning the path, the calling thread is able to open the file, provided that the file is in an accessible folder.