12-22-2022 08:03 AM - edited 01-05-2023 10:05 AM
UPDATE (01/05/2023)
As of January 5th users are being loaded via the Federated App Id but instead of missing their heads they now seem to be missing their hair. It would be funny if our product launch was not dependent on this getting fixed.
UPDATE (01/03/2023)
As of January 3rd Loading Avatars with Federated App Ids simply doesn't work. The User fails to load and I get the error log 'Spec Request Failed'.
__________________________________
We've been experiencing problems with the Meta Avatar 2 SDK in our desktop app. I've narrowed it down to a problem with the way avatars are loaded using the federated app id, or cross play as its called in the documentation. Here are the steps to reproduce:
5. Now try loading the avatar again but this time using the regular app id... The problem persists.
The avatar can be made to load correctly if you load the avatar regularly once, make a change to your avatar, save and then reload the avatar.
Solved! Go to Solution.
01-10-2023 02:00 PM
It looks like it was a backend issue and has been resolved since at least January 6th 2023.
01-10-2023 02:00 PM
It looks like it was a backend issue and has been resolved since at least January 6th 2023.