-
Notifications
You must be signed in to change notification settings - Fork 85
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
[Bug]: Inconsistencies when changing document directory #255
Comments
Okay I found the issue. You can't use a directory outside of the documents folder. But I will add a notification that users will get a notification that this folder can't be used |
Okay, |
Can confirm that saving files and templates work when in a sub-directory of /Documents. |
I disabled it temporarily. I can't get the current document directory from android to test it. I need to test it more and reenable it after that again |
Templates and documents already in the folder also don't appear when changing to it, even after force stopping and deleting the cache. |
I fixed it now by disabling it on android. Maybe we should add an issue to reimplement it with a safer option. For now the syncing feature should help and the native file system(all files should be stored in |
What happened?
When the document directory is changed, existing files aren't moved. This may be intentional (albeit arguably bad, since there's no other easy way to extract the files from the app's internal storage), however the old files are still shown in the quick open menu, but can't be accessed (a new blank file is shown).
Files can apparently also not be saved or created, neither can templates (see #254).
Folders can be created with the larger file menu, they also appear in the file system. When clicking "create" for a file in the "open" menu, simply nothing happens.
(Are the errors caught somewere?)
Version
1.4.2
Platform
Android
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: