I just installed the app. When trying to select the folder to store my notes I get this os error 13. I tried to give storage permission but I'm getting the same message.
I'm on Android, all the info in the screen attacched.
Os error 13 when trying to select destination folder #72
Hello, you'll have to Grant File Access to HelixNotes to manage files on your device.
I've already granted storage access, I don't see any other permission available.
Thanks for the details, that pinned it down. The problem is specific to Android 10. The app's storage flow relies on the "All files access" permission, which only exists on Android 11 and newer, so on Android 10 there's no permission you can grant that lets the app write to the folder. That's why you're seeing os error 13 and don't see any other permission to enable. It's a gap on our side, not yours.
I've implemented a fix that restores proper storage access on Android 10 (and older). It'll ship in the next release, after which selecting your notes folder will work normally. I'll update this issue once it's out.
Thanks for reporting it and for the clear screenshots.
Thank you for having a look and for taking the time to work on a solution. Really appreciate that
I'm getting a similar error message at random times when trying to open Helix Notes on a Windows 11 Pro PC. Probably 30% of the time when I try to open the app, instead of returning to the files I was previously using, it asks me to browse to the files but then throws a permissions error when I point it to those files. Clicking the Back button instead will take me to those same files with no error.
@operative2503 wrote in #72 (comment):
I'm getting a similar error message at random times when trying to open Helix Notes on a Windows 11 Pro PC. Probably 30% of the time when I try to open the app, instead of returning to the files I was previously using, it asks me to browse to the files but then throws a permissions error when I point it to those files. Clicking the Back button instead will take me to those same files with no error.
I'm not 100% sure, but this might be the OneDrive files on demand feature behavior.
Hello, this has been addressed in v1.3.0. Closing this issue.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?