Skip to content

fix(rum): report APP_FREEZE with error.category ANR instead of App Hang - #25

Merged
Fiona2016 merged 2 commits into
mainfrom
feat/freeze-error-category-anr
Aug 18, 2026
Merged

fix(rum): report APP_FREEZE with error.category ANR instead of App Hang#25
Fiona2016 merged 2 commits into
mainfrom
feat/freeze-error-category-anr

Conversation

@Fiona2016

Copy link
Copy Markdown
Collaborator

What

App freezes captured via hiAppEvent APP_FREEZE were reported with error.category: "App Hang". They now carry error.category: "ANR". is_crash semantics are unchanged, and crashes still report "Exception".

Why

A HarmonyOS APP_FREEZE is the system watchdog's application-not-responding verdict: judged by the OS (thread block, input block, lifecycle timeout), delivered on the next launch, carrying a diagnostic snapshot. That is the same mechanism family as an Android ANR. "App Hang" describes a different thing — a hang the SDK samples itself in-process (the iOS model), which this SDK does not do. Categorizing freezes as ANR groups them with their Android counterparts for cross-platform aggregation.

Changes

  • RumFeature.crashAttributes: crash_kind: 'freeze' maps to ANR
  • Unit test + demo README expectations updated
  • CHANGELOG entry

🤖 Generated with Claude Code

HarmonyOS APP_FREEZE is the system watchdog's application-not-responding
verdict: judged by the OS, delivered on the next launch, carrying a
diagnostic snapshot. That is the same mechanism family as an Android ANR,
not a self-sampled in-process hang, so freezes now carry
error.category: "ANR" for consistent cross-platform aggregation.
is_crash semantics are unchanged.
@Fiona2016
Fiona2016 merged commit 8855eb2 into main Aug 18, 2026
6 checks passed
This was referenced Aug 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant