Closed sbesh91 closed 9 months ago
I think this is something bevy does. It also happens with the built in loader. I'd also like to know if it can be turned off though, since I don't have meta files for my assets either.
This might be a silly question, but the error fetching that meta file is crashing my app. Do you use a global error handling pattern for bevy apps or are you able to just catch this error somehow?
Tbh I'm not currently using this myself, but i see similar 404s from bevys built in loader that are harmless.
Is the example is crashing for you on wasm?
Yeah, I get a full app crash on wasm.
Could you post the logs here?
Hey, I'm sorry to say I was wrong. The app isn't crashing, it also isn't rendering the image at the moment but that may be a different problem.
"The app", do you mean your app, or the example here?
Yeah, sorry about that. I am referring to my app specifically. I think this issue can be closed since this is a problem with bevy directly not your plugin.
No worries. Thanks for reporting what you thought was a bug! Let me know if you find out how to stop trying to fetch .meta files :)
I've got a weird double image fetching error going on locally. Building for wasm and testing in firefox on M1.
Hey, here's the screenshot of what I'm seeing.
Essentially it looks like there's a second request getting kicked off that will always take any url and append
.meta
on the end.someurl.jpg
->someurl.jpg.meta