Distribute and grow

Bug reports

Updated: Oct 29, 2026

The Bug reports page collects bug reports and feedback from the people who use your app. It shows reports from players of your public release together with feedback from your playtesters. Use it to find issues, filter them, and track each report with a status.

Find the Bug reports page in the left-side navigation for your app in the Meta Horizon Developer Dashboard⁠. You don’t need to set anything up. Reports appear as soon as people submit them.

Where bug reports come from

Bug reports come from two groups of people.

Players of your public release. People can report a bug from your app’s page in the Meta Horizon Store in VR, on the web, and in the Meta Horizon mobile app. To submit a report, a person must own your app and have spent time playing it. Bug reports are separate from reviews, so they don’t affect your app’s star rating. For more about reviews, see Customer reviews.
Playtesters. People you added to one of your app’s release channels can submit playtesting feedback. Playtesters don’t need to meet the playtime requirement. For more about release channels and playtesting feedback, see Get playtesting feedback from users added to release channels. To help your playtesters send useful feedback, share Collecting remote playtest feedback with them.

Each report can include a title, a description, a category, and an attached screenshot or video. Each report also records the device, the Horizon OS version, and the build of your app the person was using.

Who submitted a report

The Reporter field in a report’s details depends on where the report came from.

Playtest feedback shows the username of the person who submitted it.
Reports from your public release don’t show the reporter’s name or account. When a person submits a report, they can choose to share an app-specific ID. This scoped ID is the same user ID that your app receives for that person, so you can match the report to your own logs. The scoped ID is included only if your app was approved for User ID access through the Data Use Checkup when the person submitted the report.

How Meta stores bug reports

Meta stores bug reports and the media attached to them. Your team views and manages the reports on the Developer Dashboard.

The people who submit reports don’t get updates after they submit. They can’t see a report’s status or your team’s resolution notes, and Meta doesn’t notify them when your team acts on a report. You can’t reply to a report from the Developer Dashboard.

Access the Bug reports page

To view the Bug reports page, follow these steps.

Open the Developer Dashboard⁠.
Select your app.
Select Bug reports in the left-side navigation. You can also go directly to /manage/applications/{APP_ID}/user-feedback/.

Permissions

Two organization permissions control access to bug reports. An organization administrator can add them to a role. For more about roles, see Create your team.

Permission	What it allows
View bug reports	View all bug reports for the app, including reports from your public release and scoped IDs.
Manage bug reports	Everything in View bug reports, plus changing report statuses and adding resolution notes.

Team members without either permission see only playtest feedback. A notice at the top of the page tells them which reports are hidden.

Bug report volume

The Bug report volume card at the top of the page summarizes the reports for your app.

Metric	Description
Total reports	The number of reports submitted for your app
New	The number of reports that no one has reviewed yet
In progress	The number of reports your team is working on
Resolved	The number of reports your team marked as resolved
Most recent	The date of the most recent report

Find reports

The reports table lists each report’s date, title, description, device, and status. Select a column heading to sort the table.

Use the filters above the table to narrow the list.

Filter	Description
Category	The category the reporter chose: Audio, Controls, Crash, Gameplay, General feedback, Graphics, Performance, or Other. Select Uncategorized to include reports submitted without a category. You can select more than one category.
Device	The device the report came from
Media	Whether the report includes an image, a video, or no media
OS version	The Horizon OS version the device was running
Source	Public for reports from your public release, or Playtesters for playtest feedback. This filter appears only if you have the View bug reports or Manage bug reports permission.
Status	The report’s status. You can select more than one status.

To find a specific report, enter text in Search reports. The search matches report titles and descriptions.

View report details

Select View details on a report to open its details. The details panel shows:

The category, reporter, and description
The device, Horizon OS version, and app build
The status
The source, and where the report was submitted from, such as the Store page or a playtest build
The attached screenshot or video, if the reporter added one
The date the report was closed and its resolution note, if the report is resolved or closed

Track reports with statuses

Every new report starts with the New status. If you have the Manage bug reports permission, you can change a report’s status from the table or from the details panel. Statuses are for your team only. The person who submitted the report doesn’t see them.

Status	Meaning
New	No one on your team has reviewed the report yet.
Not started	Your team has seen the report but hasn’t started work on it.
In progress	Your team is working on the report.
Resolved	Your team fixed the issue.
Closed	Your team closed the report.

To update several reports at once, follow these steps.

Select the reports in the table. You can select up to 50 reports at a time.
Choose the new status from Bulk change status.
Select Update selected.

Add a resolution note

When you mark a report as Resolved or Closed, you can add an optional resolution note of up to 1,000 characters. Use it to record what your team did about the report. Team members who can see the report can read the note. The person who submitted the report can’t.