Akseli
Akseli
Also found this, maybe some more help in there: https://stackoverflow.com/questions/5657411/android-getting-a-file-uri-from-a-content-uri
Could the bug be the random `%2F` symbols in the path? `%2F` should be `/` like mentioned here: https://www.w3schools.com/tags/ref_urlencode.ASP
> I'm getting the same error while running on LineageOS even with a new empty folder. Does your error message also have `%2F` symbols?
That seems to be `:` symbol. Seems more likely now that the URI is not being parsed correctly by the app.
I poked around a bit: After fixing the uri decoding, it still didnt work. My guess is that `content://` folders and docs need to be handled some other way
From what I've gathered, it seems the ROOT variable is not resolved during the time when the docs are generated, so it doesn't match anything in the `robot.libraries.libdoc.needsArgs`
Sounds good to me, I have time to work on this whenever.
Thanks, will give it a looksie!
Sorry ive been so busy i forgot. I could try this on weekend possibly but cant promise anything. If someone else wants to make this, go right ahead :)
This seems still to be an issue in v1.17.0