How Alibaba Cloud RUM SDK Captures iOS App Performance and Crashes

Mobile developers often struggle to reproduce user‑reported issues such as freezes or crashes because logs are noisy and crash stacks lack context. To address this, Alibaba Cloud built a cloud‑native iOS SDK that links performance metrics, error logs, and user behavior into a unified view.

iOS Data Collection Overview

The SDK provides four core capabilities:

User session trace: records the complete sequence of user actions, API calls, and resource loads so that a problem can be back‑tracked.

Performance metrics: monitors launch time, page load time, network request latency and success rate, and UI jank.

Exception and stability monitoring: automatically captures Mach kernel, Objective‑C, Swift, and C/C++ exceptions.

Custom data reporting: allows businesses to send custom events and logs, tying user behavior to business KPIs.

SDK Architecture

The SDK is organized into four layers:

Public API layer: exposed methods for app developers.

SDK management layer: controls module lifecycle and start/stop logic.

Data collection layer: isolates each collector (session, performance, exception) to keep implementations independent.

Core foundation layer: written in C for cross‑platform consistency, handling time sync, data serialization, configuration fetching, and persistence.

Data‑Collection Techniques

Two main techniques are used:

Method Swizzling: leverages Objective‑C runtime to replace implementations of networking APIs (e.g., URLSession, URLConnection) and UI controls, enabling non‑intrusive capture of request details, response codes, errors, and UI events.

System‑level APIs: registers for iOS lifecycle notifications (e.g., willEnterForeground, didBecomeActive, willResignActive, didEnterBackground) and monitors the main RunLoop to detect UI jank.

Lifecycle Event Handling

The SDK wraps these notifications in an AppLifeCycle class to guarantee correct ordering and to simplify developer integration. RunLoop monitoring adds additional jank‑event data.

Crash Collection with KSCrash

For crash reporting, the SDK integrates the open‑source KSCrash framework, which safely captures Mach, C++, Objective‑C, and signal‑based crashes. KSCrash consists of five subsystems: core coordination, monitor management, report generation, configuration, and installation. It produces detailed reports with thread stacks and context, and also supports capturing stack traces for UI jank.

Supported Data Types

Network request metrics (latency, status code, error reason, end‑to‑end trace).

Page load timing and state changes.

UI actions from controls such as UITableView and UICollectionView.

WebView events via a web probe (resource requests, route changes, JS errors).

App launch times (cold and hot), jank events with stack traces, and network type.

The SDK is positioned as a performance‑experience monitoring tool that helps developers quickly locate and fix issues in iOS apps.