Ready Player Me

Ready Player Me enables avatar creation across web and Unity platforms, but users face significant technical challenges. Web version issues cause asset loading failures, especially for Firefox users, while Unity integration problems generate unauthorized errors. The company attributes these problems partly to browser configurations, but developers and users continue to encounter reliability issues requiring proper subdomain and AppID setup.

Company Overview

Ready Player Me offers avatar creation capabilities through both web-based and Unity platforms. The web application allows users to create and customize virtual representations across multiple accounts and applications, while developers can utilize Unity sample assets for integration into their projects.

However, users have encountered several technical challenges. On the web front, many users report asset loading issues, including failed requests and 404 errors. The problem appears browser-specific, affecting Chrome and Firefox users more prominently. Some users experience an "infinite wearables load screen of death," with crossed circle indicators replacing expected avatar content. Permissions errors, particularly 403 Forbidden, indicate potential authentication problems when attempting to unlock assets through the API.

The company attributes these issues partly to browser configurations, as testing with Chrome showed normal functionality. Clearing cache and cookies or using incognito mode often resolves the problem. Interestingly, logging in directly through the application works without issues, while subdomain access causes the errors. Ready Player Me is actively working with their development team to address these concerns and improve the platform's reliability.

On the Unity side, developers face their own set of challenges. The Avatar Creator Sample generates an internal server error {"type":"UnauthorizedError","status":401,"message":"Unauthorized"} when attempting API requests. This error occurs specifically with the URL https://api.readyplayer.me/v1/assets?limit=100&page=1&filter=viewable-by-user-and-app, requiring proper project setup including subdomain and AppID configuration. According to the company's documentation, Unity projects need both these credentials, obtained from the studio.readyplayer.me/applications page, and set in Tools > Ready Player Me > Settings.

Some developers found success by clearing PlayerPrefs within their projects, though the exact cause of the issue remains unclear. The company continues to investigate and provides regular updates to their development team to address these technical challenges and improve their platform's stability.

Web Version Issues

The Ready Player Me web application has experienced persistent technical issues since the previous reporting period, with users reporting asset loading failures across both Chrome and Firefox browsers. Common complaints include infinite load screens displaying crossed circle indicators instead of avatar content, making it impossible to view selected assets. Many users have noted that while avatar creation functions proceed to completion, the customizations made during the process are not retained—users save the default outfit but lose any changes they try to implement.

Security permissions have proven particularly problematic, with 404 errors occurring when attempting to unlock assets through the API. Although basic authentication works when logging directly into the application, accessing the service through a subdomain triggers these permission-based access denied messages. Firefox users have reported the most consistent issues, though Chrome and Brave browser users also experience high rates of failure. Community members have recommended troubleshooting steps including clearing cache and cookies, or testing in incognito mode, which sometimes resolves the display problems but does not fix the underlying permission errors.

The company has acknowledged these issues, with preliminary testing confirming the problems exist when using a test subdomain. While the development team works to identify and resolve the root cause, users are advised to ensure they are testing the standalone web application rather than integration functionality. Efforts are also underway to clarify how the subdomain and AppID configuration requirements affect both web and Unity integration.

Avatar Linking and API Integration

Avatar linking functionality was reported to be non-functional since several weeks prior to the company's acknowledgment. A user encountered 403 errors while attempting to access accounts in private browsing modes using Firefox and Chrome/Brave browsers, despite not using an API key during login attempts. The user was successful in unlocking assets for themselves and others through Postman with proper configuration, confirming that the issue lay with the web application rather than user account settings.

The underlying problem became apparent when the user created avatars within their account and subsequently found themselves unable to unlock the associated assets, receiving 404 Not Found errors in response. This confirmed the failure of avatar linking across the platform.

The company was able to reproduce the problem using a test subdomain, indicating that the issue is platform-wide rather than account-specific. They have prioritized investigation with their development team to address this critical functionality, with the matter resolved as confirmed by successful operations reported from multiple users after the fix was implemented.

Unity Integration Troubleshooting

The Unity integration issue stems from API requests generating an {"type":"UnauthorizedError","status":401,"message":"Unauthorized"} response when targeting https://api.readyplayer.me/v1/assets. This error became apparent through testing but did not manifest in a fresh Unity project, indicating a potential configuration problem.

The core requirement for resolving this issue lies in proper project setup. According to the Ready Player Me documentation, Unity projects need both a subdomain and an AppID to function correctly. To obtain these credentials, users must log into the studio.readyplayer.me/applications page and then configure the AppID in their Unity project through Tools > Ready Player Me > Settings.

Initially, developers attempted to resolve the issue by clearing PlayerPrefs within their projects, though the exact cause of the problem remains unclear. The issue affected multiple developers across different Unity projects, demonstrating its widespread nature.

The problem persisted despite these initial steps, leading some developers to investigate further configuration options. The community has emphasized the importance of testing the standalone web application versus integration functionality, as different behaviors were observed in each scenario.

The issue's resolution came through an unspecified change to the project configuration, though the precise fix remains undocumented in the available reports. This suggests that while the problem was successfully resolved, the underlying cause may still require further investigation to prevent future occurrences.