Closed natebragg closed 5 months ago
Of interest is that this seems to be due to the file extension, even though the file only contains ascii text. If I change the name to quest.txt
the file opens fine.
As I see in the logs, termux should be configured to allow external applications to read the content
java.lang.IllegalArgumentException: TermuxContentProvider requires allow-external-apps
property to be set to true
in ~/.termux/termux.properties
file.
As I stated in my comment, this is due to the file extension. I have this property set in Termux. Please set this property in that file, and try an ascii file with the name from my report, quest.logcat
, and you should see that it does not open.
When attempting to open a file in Librera from within Termux, I got the following toast (which it truncated due to space):
The termux command I ran was:
I tried this on two platforms, same results.
I also tried choosing a different app in the dialog that popped up when I ran
termux-open
, which worked fine, so I don't believe this is a Termux issue.