A GraphQL mutation failure is preventing users from saving changes on the application submission metadata assets page in the Developer Dashboard. Specifically, the OCDevManageApplicationSubmissionMetadataAssetsMutation operation is failing with error code 1675030, indicating an "Error performing query". The error originates from Relay's GraphQL request handling layer, particularly in RelayError.js and RelayGraphQLRequestUtils.js, when attempting to persist asset metadata changes during the app submission workflow.
In a specific world, VR Build/Edit Mode fails to load on Quest with the error 'Unable to Travel – We were unable to take you to your destination.' This issue is reproducible across multiple users and headsets, but does not affect Desktop Editor and Preview Mode for the same world. Cloning the world or loading other worlds does not reproduce the issue. Attempts to resolve the problem by restoring older backups, replacing the spawn point, removing scene geometry, and detaching all scripts were unsuccessful. The issue appears to be isolated to the original world's VR Build Mode destination or world instance state, suggesting possible world metadata corruption or invalid VR Build Mode configuration specific to that world instance.
When a user accidentally rejects an invitation to an alpha distribution channel, subsequent re-invitation attempts from the Developer Dashboard's release channel users page fail with a GraphQL error (1891875) indicating a pending invitation exists, despite the invitation having been rejected. This error occurs during the BulkInviteUsersMutation operation and suggests a state inconsistency where rejected invitations are not properly cleared, blocking further re-invitation attempts.
The app submission categorization field on the store metadata page becomes unresponsive, throwing a React error #185 (maximum update depth exceeded) in the OCDevManageApplicationSubmissionMetadataForm component. This error indicates an infinite re-render loop, causing the UI to freeze and preventing completion of the categorization field, which in turn blocks app submission. The issue is specifically traced to the OCDevManageApplicationSubmissionMetadataName.react.js component.
The issue occurs on the application submission page in the Developer Dashboard, where a GraphQL rate limit exceeded error (error code 1675004) prevents navigation to previous pages or loading of the page. Specifically, the OCDevManageApplicationSubmissionRootQuery operation fails due to rate limiting, causing the submission management interface to become unresponsive. This error is caught in the OCDevManageApplicationSubmissionRoot React component.
A test user subscription purchase fails with an 'Item Not Available' error (code 1891831) when attempting to purchase a subscription through the Manage Test User Subscriptions tab in the Monetization dashboard. The subscription has a $0.99/month plan after a 7-day free trial, appears in the Subscriptions list, and has a SKU set. The test user has test payment information configured. The error message states 'Sorry, this item isn't setup for purchases yet. Please try again later.' The failure occurs immediately upon attempting the purchase, with Trace ID D52vhu0zTUD returned with the error.
The application submission metadata specs page is displaying corrupted dropdown values, where all selection lists (interaction type, internet requirements, etc.) are populated with repeated 'Sports' entries instead of the correct options. This issue prevents developers from completing game submissions, persists across logout and device changes, and affects multiple developers. The GraphQL mutation OCDevManageApplicationSubmissionMetadataSpecsMutation fails with error code 1675030 when attempting to save specs, indicating a backend data issue that returns incorrect enum/option values for the submission form fields.
A GraphQL query error (code 1675030) occurs on the Worlds inventory page in the Developer Dashboard when editing a creatable item. The error is specifically with the OCDevManageWorldsInventoryQuestRewardTiersNotificationBannerLazyQuery, which is used to power the quest reward tiers notification banner component. The error message indicates "Error performing query" and is caught in the OCDevManagePlaceholder.react module. This issue appears to be a server-side query failure that prevents the notification banner from loading during inventory item editing workflows.
The identity verification flow fails when attempting to scan an ID barcode, resulting in a GraphQL error 1891992 indicating that "identity verification is already complete". Despite the verification status showing as failed in the URL parameters, the barcode scanner is unable to read the ID. The underlying issue appears to be a state conflict, where the system blocks new verification attempts due to an existing verification record. This error originates from the Relay runtime during the GraphQL mutation, specifically with the useOCDevStartIdentityVerificationMutation operation.
When attempting to reveal the App Secret in the Meta for Developers Dashboard, the correct Facebook password is rejected with an 'Incorrect password. Try again.' message, despite the same password being accepted for normal login and dashboard access. This issue appears isolated to the reauthentication flow for revealing the App Secret, suggesting a potential stuck session or reauthentication state. Logging out and back in does not resolve the issue, and app creation and general dashboard functionality work normally.