UGC Emotes Cause Infinite Loading in Profile Picture Editor on Roblox Universal App

Issue Description

With the recent release of custom UGC animations being publishable and sellable on the Marketplace, there is a critical issue affecting the Profile Picture Editor on the Roblox Universal App. When selecting a user-created emote as the pose for your avatar, the editor fails to load the preview and instead shows an infinite loading spinner. In some cases, after removing the emote, the loading spinner persists in the torso area, making the system unusable.

This issue appears specific to UGC animations and does not occur with official Roblox emotes.

This problem is similar to a previously reported issue:

Reproduction Steps

  1. Purchase or acquire a UGC emote created and published by another user from the Marketplace.
  2. Open the Roblox Universal App (tested on Windows).
  3. Go to the Avatar tab.
  4. Click on your Profile Headshot to launch the Profile Picture Editor.
  5. In the emote selection panel, choose the UGC emote you previously acquired.

Expected Behavior

The editor should load a preview of the avatar posed using the selected UGC emote, just like it does with official Roblox animations. You should also be able to remove the emote cleanly and return to a neutral pose without any UI glitches or stuck loaders.

Visual Aids:

A private message is associated with this bug report

8 Likes

Thanks for reporting. This is a known issue Avatar Creators Can Publish and Sell Emotes on Marketplace and we are actively working on the fix.

13 Likes

Thank you for letting me know!

I hope this can be fixed soon… Let us know if you have any updates in this thread!

5 Likes

We have fixed the issue on IOS, Android, and Desktop. Other platforms will be fixed by next week.

6 Likes

Hey @vk_rObl0x,

Thank you for your message here! Unfortunately, regarding the fix for iOS devices, I’m still experiencing this issue… It occurs the same way as I initially reported.

Do I need to share my Roblox Universal App version?

Apologies that you are still experiencing the issue. Can you help share the build version that you encountered this issue on? Can you help check on your side if the issue is still encountered? Thanks

1 Like

Hello,

I wanted to say that this problem that I face is no longer happening. I suppose the situation was that it wasn’t released to the specific app version. However, after updates, it’s working fine now.

If I manage to encounter the same issue, I’ll be sure to report it!

Putting @vk_rObl0x reply as a solution! Thanks for checking in @starhiker13 !

Thank you for the update. Closing

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.