[BUG] Firebase Storage: A StorageRefrence is valid even though the file it refrences does not exist.

[ronsiv8]

[BUG] Firebase Storage: A StorageRefrence is valid even though the file it refrences does not exist.

[ronsiv8]

The project im working on has a server with the firebase admin api. I think ill just use that to check if images exist and share around download links. Its pretty odd that no exists function... Uhh, exists.

[WolfgangSenff]

Hm. Very weird. I'll have to look into this. I'm not sure we can do anything about the first bug - unless it has tried to get the file, the Godot code can't know whether or not it exists in Firebase. But maybe there's something, not sure, like an "exists" function.

[ronsiv8]

I'd really appreciate it. As of now, I came up with a scuffed-as-all-hell solution, but it is nothing im happy with, thats for sure.

[WolfgangSenff]

What happens when you try to just get the metadata?

[ronsiv8]

I'm gonna have to get back to you on that one tomorrow, i've got to head out now

[WolfgangSenff]

Been looking around, seems like there is no way to solve that problem. Our own valid property is used for after a file is deleted, nothing more. Apparently what you'd have to do is call list, then manually look for the file client-side.

How I've handled such a thing before is to make a Firestore reference document that holds onto metadata (in the traditional sense, rather than what Firebase Storage says is metadata). Then I can just ask to see if the document exists and if not, then don't attempt to get it. It's ugly, but doable.

[WolfgangSenff]

I completely agree! I'll see if I can ask the Firebase team to add it. Closing this for now.