The Meta Developer registration process is experiencing an infinite loop where users are redirected back to the phone verification screen after successfully completing the phone number verification and all registration steps, including the 'About You' step. This issue persists across multiple attempts, preventing users from finishing the developer registration and creating a new app.
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.
The requested feature involves creating a functionality where promo codes can be embedded within URLs. When a user clicks on such a URL, it should direct them to the store page and automatically apply the associated promo code to their account. This feature is categorized under Growth tools and Dev dashboard, suggesting its relevance to both user acquisition and developer tools.
The developer, a VR game developer on the MetaQuest Store with a European bank account in euros, is requesting the ability to receive payments in euros instead of dollars. Currently, Meta's payments to developers are in dollars and are automatically triggered once the amount reaches $100. However, European banks charge a significant commission (between €15 and €30 minimum per transfer) for dollar payments, resulting in substantial losses for the developer. The developer suggests implementing euro payments or allowing developers to choose the minimum payment amount to reduce bank commissions.
The user is requesting API access to sales data to display in a custom dashboard, specifically to retrieve the number of items sold per day or revenue, with additional information such as discounts used and country-wise data being desirable. They reference Steam's existing API service as an example, suggesting that this feature would be valuable for other developers and studios to track their success in the Meta Horizon Store.
Release channel invitations are failing due to an incorrect age verification error, where invitees with accounts configured as 18+ are being blocked from accepting invites with a message stating their account age is under 18. This issue appears to be isolated to specific release channel invitation flows, as the affected accounts have successfully accepted invitations to other release channels with the correct age setting. The error suggests a faulty age gate check specific to certain release channel invitation processes.
The feedback suggests that including device model and OS version information in user reviews would greatly aid developers in understanding and addressing issues. Specifically, it would help identify compatibility problems with unsupported hardware, such as Quest 2 users attempting to run an app only supported on Quest 3 and Quest 3S. This information would enable developers to quickly diagnose user issues, improve support and debugging, and prevent confusion when unsupported devices leave negative reviews. The goal is to enhance the quality and usefulness of user feedback for developers by providing context on headset model and Horizon OS version, allowing for more efficient issue resolution and improved app support.
The AI-based identity verification system is failing to accept driver's license documents from Russia, preventing developers in the Russian Federation from completing the required identity verification to publish applications. Specifically, the system repeatedly rejects submitted driver's licenses, regardless of photo quality, because Russia is not listed as a supported country/organization in the verification system. Multiple attempts with different photos have resulted in consistent rejection, highlighting a technical issue that needs to be addressed to enable developers from Russia to successfully complete the verification process.
The issue reported is that the Members page in Dev Dashboard will not load, erroring out with an HTTP 500 message. User has requested a fix for this loading issue, indicating a potential problem with data retrieval or rendering in these areas.