Know which build crashed, before the review does.
A mobile release reaches thousands of devices at once and you cannot attach a debugger to any of them. bughq collects the crash, groups it by build and release, and tells you how many users a version affected.
Crash-free sessions, by releaseSample data
How mobile teams use it
01
Tag the build on release
Set the release and build number in the init call. Every crash and handled error carries the exact version that produced it.
02
Crashes group by signature
Native and JavaScript-layer errors fold into one issue per fault, with an affected-user count instead of a raw event stream.
03
Catch a bad release early
A crash-free-sessions drop on a new build surfaces immediately, so you can halt a staged rollout before it reaches everyone.
Per build
Crashes and crash-free rates are broken down by release and build number.
User count
Each issue shows how many devices and users it reached, not just events.
One issue
Native and JS-layer faults for the same bug fold into a single thread.