Asset ContentIds beginning with "rbxgameasset://" are not loading properly

Currently, there’s an issue where the assetid “rbxgameasset” protocol is failing to load because it is unable to find the requested assets.
The issue happens to both images and sounds in Studio and in the client; in Studio, it refuses to load every asset with “rbxgameasset://”, whereas in the client it may or may not load them.
Studio Error

ContentId: https://assetdelivery.roblox.com/v1/asset?universeId=3010065818&assetName=Images%2F736_43&skipSigningScripts=1 failed due to: Request asset was not found  -  Studio

Client
Failed to load sound rbxgameasset://Audio/male_death: Request asset was not found

A private message is associated with this bug report

3 Likes

Hi, what is the real universeId ? For 12345678, there is no data associated with it

Oh, sorry, here it is: 3010065818

1 Like

I also tried to reproduce it on different devices, PCs and mobiles; same issue

what asset image you trying to fetch e.g. the specific name of the asset ? i searched logs with 3010065818 but no logging with it.

are you able load the asset with rbxassetid:// ?

Yes, I am, but this does not resolve the underlying issue

Asking you to test with rbxassetid was trying to isolate the issue. hmmm, i checked universe and assets in your screenshot. There is no data issue from our side. Checked logs but no luck. Are you still able to reproduce it ? I wonder if this is transient.
If you still see the issue, can you post the timestamp, problematic api call trace id . i will try to locate the logs by traceid..

It’s still not fixed on my end.
I tested on a different pc and location and still no luck.
The Roblox Client doesn’t throw warnings; only Studio does



If you still see the issue, can you post the timestamp, problematic api call trace id . i will try to locate the logs by traceid..

How do I do that?

Root cause found. And there is a fix going on. Thanks for reporting.

2 Likes

It has broken yet again. Evident in the game “Super Doomspire”.

Hi, is it still an issue for you? Is it on the client or Studio? For me, it’s fixed