Why is FileAccess not finding certain files?

housatic

I have a file with an extension Godot ignores, I've added said extension to the export settings, when I build my project from a command line I can see that it is being exported:

[ 82% ] savepack | Storing File: res://data/en/test/test.cjson

Yet when I launch the exported game, FileAccess can't find it. I log:
GD.Print("Path: '" + path + "' FileAccess.FileExists: " + FileAccess.FileExists(path));
And in the console I see:
08:44:53:6302: Path: 'res://data/en/test/test.cjson' FileAccess.FileExists: False

I've triple checked that the file path is correct (in the "savepack" log, the "FileAccess" log, and on the disk, whitespaces included). I have other files with the same extension that I'm opening with the exact same function and they're working fine. The only difference I can think of is that they're not in multiple subfolders (e.g. "res://data/en/something.cjson") as this specific file. What could be happening here / what else should I check? :-(

Toxe

housatic Maybe the export skips directories called "test" or handles them differently. After all you usually don't want to ship your tests. Did you try putting it into another directory?

Or is the file empty and the export skipped it or something like that?

DaveTheCoder

housatic I have other files with the same extension that I'm opening with the exact same function and they're working fine.

Are they in res:// ?

I didn't think you can reliably access those using FileAccess in exported projects.

housatic

Toxe The file isn't empty, I'm not excluding "test" or anything like it. I actually renamed the folder and file to "test" right before making this post, so that isn't the problem.

And like I wrote, I can see in the build log (when running Godot --headless --export-release) that this specific file is being included. Unless "Storing File" means something else than I think.

housatic

DaveTheCoder To my knowledge it's not a problem as long as you include them in the export settings. load()/ResourceLoader.Load() will absolutely not find them, but that makes sense since they're not Resources

housatic

Ahh nevermind, I was copying the build from one folder to another using rsync and apparently it skipped the .pck. I know rsync has a --ignore-times flag I didn't add, so I assume it just looked at the timestamps and assumed they were the same file...