Bug report request fails with "another bug report collection already in progress": clear stuck state via ADB

Android

If you're unable to request a bug report from the Esper Console and see the error Bug report permission denied or another bug report collection already in progress, your device may have a stuck bug report state. This article explains how to clear it.

Before you begin

This issue occurs when your device retains an internal "bug report in progress" state even though no report is actively being generated. It typically appears days or weeks after a successful bug report was collected, and a standard device reboot does not resolve it.

If your bug report request is timing out (you see a notification but haven't tapped Share within 30 minutes), that's a different issue — a reboot usually resolves timeout scenarios.

How to fix a stuck bug report state

You'll use Android Debug Bridge (ADB) to dispatch a broadcast command that clears the stuck state. Make sure you have ADB set up on your computer before proceeding.

1. Connect your device to your computer via USB and enable ADB access.
2. Open a terminal or command prompt on your computer.
3. Run this broadcast command:

   adb shell am broadcast -a android.app.action.REMOTE_BUGREPORT_DISPATCH --receiver-include-background

4. If that command fails or returns an exception, run this fallback command instead:

   adb shell am broadcast -a android.intent.action.BUGREPORT_FINISHED --receiver-include-background

5. After the command completes, return to the Esper Console.
6. Navigate to Devices & Groups → [Device] → Actions → Request Bug Report and trigger a new bug report request.
7. Verify that the request succeeded by checking the Activity Feed — it should show Successful status, and your device should display a bug report notification in its notification panel.

If the ADB commands don't work

If both ADB broadcast commands fail and you need an immediate solution, you can perform a factory reset of the device. After a factory reset, bug report generation should function normally. Weigh this option against your operational needs before proceeding.

Still need help?

If neither ADB command resolves the issue and a factory reset is not an option, contact Esper Support and include the following information:

• Device serial number
• Full terminal output from both ADB commands you ran
• Timestamps of the last successful and first failing bug report requests from your Activity Feed
• Esper Agent / Esper Agent version (found in Devices & Groups → [Device] → Device Info)
• Whether you're seeing this pattern on multiple devices in your account