-
Notifications
You must be signed in to change notification settings - Fork 100
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
Cannot add dictionaries - permission problem? #198
Comments
"Add" asks OS to open a document which OS typically fulfills by presenting a built-in file chooser (but it can also be a 3rd party file manager app). I've seen a similar problem reported on an Honor device with MagicOS - the issue there was that the file manager was stopped for some reason, opening files didn't work in any apps (e.g. attaching images to email didn't work) and starting the file manager fixed it. Perhaps something similar is going on here? I don't think there's anything to be changed in the app. |
Thank you for this clarification. I then suspected that it crashed because of 3rd party file manager (I had replaced the google filemananger with that from fossify). So I removed the 3rd party and enabled the google one - but it still crashes. No email or messenger app installed - I use it mainly as a offline reading app. But the file manager does work when I open it manually. I tried also with older aard2 versions (as it worked before), but no changes (v53, v56, v58). Hm, no idea. |
I don't know what steps are involved in that, looks like something is still missing. Ultimately there should be an application in the system that handles ACTION_OPEN_DOCUMENT, maybe what you did to enable google file chooser didn't actually register the intent handler. |
On Armor pad lite (Android13) I cannot add dictionaries in my Aard2 app (version 58). So I removed all dictioaries that were added before (older version??), and clicked on ADD in the Dictionaries tab. As soon as I click it, the app crashes.
Checking for file system permission, it tells me, there are no permissions required to run this app. Is this something that needs to be changed in the app, or is there a workaround?
The text was updated successfully, but these errors were encountered: