A crash stack is usually a list of memory addresses or obfuscated short names. It doesn't tell you which function or which line of code failed until a symbol file maps it back to the real source. This update fills in symbolication for WeChat Mini Programs, HarmonyOS, and Android NDK native code, joining the Web and iOS support already in place, so RUM now covers most of what runs in production.
Here's how it works: a SourceMap, ProGuard mapping file, or debug symbol file generated at build time records how minified or obfuscated positions map back to the original source. Once uploaded, RUM matches incoming crash events by service name and version, then resolves the addresses or short names in the stack into real function names, file names, and line numbers.
WeChat Mini Program RUM
Production error stacks used to show only the transformed file path and line/column numbers. You can now run miniprogram-ci get-dev-source-map to generate a sourcemap and upload it through the Flashduty CLI for automatic resolution. Issue grouping and a dedicated Mini Program dashboard are also in place.
HarmonyOS RUM
A HarmonyOS crash stack can mix ArkTS/JS frames with native .so frames. Once the @flashcatcloud/hvigor-plugin is installed, the build automatically uploads the ArkTS sourcemap and the unstripped native symbol files, so both frame types resolve in the console. The dashboard and symbol management page now support HarmonyOS, and a Trace integration guide has been added.
Android NDK Native Crash Symbolication
We fixed a grouping bug that was splitting a single NDK crash site into several unrelated issues. Upload the unstripped .so file with its GNU build-id, and the C/C++ crash address resolves to a function name and line number. Native startup metrics now separate cold start from warm start instead of reporting them together.
Alert Decoupling and Private Deployment
RUM alerts used to require the On-call module to reach anyone. They can now be delivered as a Webhook POST straight to your own endpoint, so a self-hosted, RUM-only deployment without On-call can still receive alerts. The SDK also supports a custom data ingest endpoint and CDN for private deployments.
Getting started
Go to Flashduty console → RUM → App Management → Source Management to upload symbol files for your platform. Alert delivery is configured under "App Management → Alert Settings."
See Source Mapping and Error Tracking and Issue Alerts for details.