Frustration

note

The frustration detector is new in 7.0.0.

The frustration detector observes the user's interaction pattern and the SDK's network / log streams to identify moments when the user is likely struggling with the app. Four sub-detectors ship by default; each fires a Bugsee issue report when its specific pattern is recognised:

Sub-detector	What it observes	Typical signal
Rage tap	A burst of taps on the same UI region within a short window	User perceives the button as unresponsive and retries by tapping repeatedly
Error tap	A user tap that is closely followed by a Bugsee error report	A button press that immediately crashes a screen
Stuck loading	A network request that runs long enough to be perceived as hung, with the user still interacting	Long-running RPC that the user has clearly noticed
Frozen UI	The top activity stops emitting frames while the user is still touching the screen	Renderer-thread stall that doesn't trip the hang detector

Each sub-detector produces a simulated error report through the standard SDK reporting pipeline, so they participate in the same dedup / mapping / upload paths as crash reports.

Configuration

Form	Setting
Manifest meta-data	<meta-data android:name="com.bugsee.option.detect.frustration" android:value="true" />
Bugsee.launch() map	options.put(Options.DetectFrustration, true)
Default	false

AndroidManifest.xml

<meta-data android:name="com.bugsee.option.detect.frustration"
           android:value="true" />

Programmatic

HashMap<String, Object> options = new HashMap<>();
options.put(Options.DetectFrustration, true);
Bugsee.launch(this, "<APP_TOKEN>", options);

The four sub-detectors are bundled — there are no individual on/off knobs. Enable or disable the family as a whole via the single option above.

See also

• Configuration → Detection — the option-key reference for all detection options.