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 issue reported is that changes made to assets are not being saved, as indicated by the absence of a green tick mark after clicking the 'Save Changes' button. Despite updating the required images, the system fails to confirm the changes with a green tick and does not display any error messages, leaving the user uncertain about whether the changes have been successfully saved.
The current subscription period options are limiting for B2B customers, and the request is to offer further subscription options for longer periods, specifically 2, 3, and 5 years, to simplify specific business offerings.
The issue is that when attempting to invite users to a Release Channel, no invitation emails are sent to the invited users. This problem has been tested with multiple email providers, suggesting that the issue lies with the invitation process itself, rather than with a specific email service. The issue is related to Permissions and the Dev dashboard.
The sales page is not showing individual sales data. The issue persists as reported previously, with users unable to view specific sales information, which was available last month. The problem is categorized under 'Other' and 'Dev dashboard'.
The user is unable to see if their app, 'Brandschutzhelfer DGUV 205-023', has been successfully submitted. They are seeking confirmation on whether everything is fine or if something is missing, indicating a lack of visibility into the app submission status on the Dev dashboard.
When updating the world description, a bug report popup appeared, despite the user believing that the update was saved. The issue occurred in the Developer dashboard/Dev dashboard, suggesting a potential problem with error handling or feedback mechanisms in the UI, specifically when interacting with world description updates.
The key generation process failed to work as expected. This issue is categorized under Platform services and Dev dashboard, indicating that the problem occurred within the development environment or infrastructure. The failure of the key generation process suggests a technical issue that may be related to configuration, dependencies, or the algorithm used for key generation. Further investigation is required to determine the root cause, which may involve examining logs, reviewing recent changes to the platform or dashboard, and assessing the specific steps or conditions under which the key generation was attempted.
There is a bug affecting the creation and destruction of apps, resulting in inconsistent success rates. The issue manifests as an error when attempting to create or delete an app, with success varying between attempts. This problem is reported in the App submission and Dev dashboard areas.
The current implementation of mixed reality recording is disabled when the boundary is turned off in developer mode. Users are requesting the ability to record and cast in mixed reality even when the boundary is deactivated, allowing for larger play areas to be captured. Two possible solutions are proposed: 1) enable recording when a consent form is completed and a thorough privacy statement is provided to the end user, or 2) expand the boundary area to a significantly larger size, potentially to encompass entire houses, effectively providing an unlimited space.