Developers are requesting an optional 'Classic Dashboard' mode that restores the pre-redesign Meta Quest Developer Dashboard UI from May 2024. The previous single-page interface provided a comprehensive overview of key information, including app submission status, release status, production build version, organization switching, requirements, legal documents, organization events, financial information, and access to multiplayer testing tools. The current post-Meta Horizon redesign requires additional navigation to access these features, reducing efficiency for developers managing multiple applications. The request is for an optional layout toggle to allow developers to switch between the current design and the classic layout, rather than replacing the existing design.
The Desktop Editor crashes when attempting to open a world for editing, despite launching successfully. The error occurs after a recent update that previously resolved a launch failure issue. The error message references Unity 6000.0.59f2 (build ef281c76c3c1) and is categorized under Developer dashboard and Dev dashboard. This issue appears to be a regression, introduced after a recent update.
The Desktop Editor fails to launch after an update, crashing immediately with a 'FATAL ERROR: Failed to load il2cpp' error. This issue appears to be related to the Unity scripting backend components not loading correctly post-update, specifically with the il2cpp runtime initialization. The application itself updates successfully, but the subsequent launch fails due to this initialization failure.
Deleting test users from the organization test users management page in the Developer Dashboard fails due to a GraphQL authorization error. The error occurs when triggering the OCDevManageOrganizationTestUsersDeleteConfirmationModalMutation operation, resulting in error code 3969005 with the message "You're not allowed to complete this action." The issue appears to stem from the user lacking permission to delete test users or a permissions misconfiguration, despite having access to view them. The error is thrown from the Relay GraphQL layer when processing the mutation response payload.
The Organization verification page in the Developer Dashboard fails to load due to a GraphQL rate limit exceeded error (code 1675004). This error occurs specifically on the OCDevManageOrganizationVerificationRootQuery operation, which prevents both personal and organizational verification from completing. The issue is traced to the OCDevManageOrganizationVerificationRoot.react.js component. As a result, the rate limiting causes the verification workflow to be inaccessible, affecting users' ability to verify their organizations.
The Meta Developer documentation site (developer.meta.com) has become incompatible with non-Chromium browsers such as Firefox and Brave on Linux. Specifically, interactive navigation elements like dropdown menus are non-functional, while standard hyperlinks continue to work. This issue appears to be a recent regression, suggesting a problem with JavaScript compatibility or event handling for browsers other than Chrome.
The app submission process fails to transition to the 'ready for review' state after saving a draft, triggering a GraphQL error 1675004 (rate limit exceeded) on the OCDevManageApplicationSubmissionSubmitSaveDraftMutation operation. This issue occurs specifically with new submissions using the save draft flow, while submissions with a live binary work correctly. The error is encountered in the RelayGraphQLRequestUtils network layer during the API request.
During organization onboarding in the Developer Dashboard, the verification process for developer mode fails due to an error (1891932) indicating that a team with the same name already exists. This issue occurs when attempting to create or configure an organization, specifically when the OCDevManageOnboardingOrganizationCardMutation GraphQL operation is executed, suggesting a name collision with an existing team entity that blocks the onboarding flow.
Users are experiencing an issue with creating new clothing assets in the desktop editor, specifically when attempting to add them through the world's inventory management page. The issue does not provide a specific error message or failure behavior, but it consistently occurs in this context.
When attempting to resend an invitation to a release channel user after they have declined, an error occurs with GraphQL error 1891875 stating 'There is already a pending invite for this release feed'. Despite the release channel users page not displaying any pending invitation, the backend prevents the new invitation attempt. This issue arises from a state inconsistency where declined invitations are not properly cleared from the pending state, thereby blocking re-invitation of users who previously declined. The error is specifically associated with the OCDevManageApplicationReleaseChannelInviteUserModalBulkInviteUsersMutation operation.