at export, the resources folder is basically gone, compacted down into a more optimal, minimal structure. That will complicate your directory walking. Two approaches come to mind. 1, try ResourceLoader.load(). It will still take the same res:// relative file paths and return the resource. So that might be enough right there. But me personally, I’d probably opt for a custom Resource that stores all your encoded special information into some kind of collection, save that resource and at runtime just use it for the details, not actual directory contents.
I’d go with option 2. GL!
also, read this:
https://forum.godotengine.org/t/cannot-traverse-asset-directory-in-android/20496