How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix a Web Game Where the Audio Context Stays Suspended on Mobile

Q: What causes a web game where the audio context stays suspended on mobile?

The AudioContext starts suspended and is only resumed reliably from inside a real touch handler, so a resume scheduled elsewhere is ignored and audio never plays.

Quick answer: Call audioContext.resume() directly inside a touchend or pointerup listener on the first interaction, and verify the state changes to running before playing sounds.

Players tap to start your mobile web game but there is still no sound. The resume ran from a timer or promise, not the touch handler, so the browser ignored it. Resume the context inside the real gesture event.

How to fix it

1. Resume inside the gesture

Call audioContext.resume() synchronously within a touchend, pointerup, or click handler. Browsers only honor resume from a genuine user activation.

2. Verify the state

Check that audioContext.state === 'running' after resuming before scheduling sounds, and retry on the next gesture if it is still suspended.

3. Unlock once, then reuse

Resume on the first interaction and keep the single context for the session rather than creating new contexts, which can hit per-page context limits on iOS.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every HTML5 error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.