Mobile Monitoring iOS SDK version history-Enterprise Mobile Application Studio(EMAS)-阿里云帮助中心

This document describes the changes for each version of the Mobile Monitoring iOS SDK.

SDK privacy policy and compliance

To meet privacy compliance requirements, use the latest SDK version from the official Alibaba Cloud website. Before using Mobile Monitoring, you must carefully read the EMAS Privacy Policy and follow the iOS SDK integration guide.

SDK information

SDK name	Mobile Monitoring
Developer	Alibaba Cloud
SDK version	2.2.3
SDK update date	2026-06-01
SDK size	8.9 MB Note This size excludes indirectly dependent frameworks.
SDK MD5	908d72bcb59fa4b24bac6d8bdad09c0f
Privacy policy	EMAS Privacy Policy Important To meet privacy compliance requirements, use the latest SDK version from the official Alibaba Cloud website. Before using Mobile Monitoring, you must read its privacy policy and follow the iOS SDK integration guide.

Version history

Version	Description
2.2.3	`Added` support for monitoring cross-platform application startup.
2.2.2	`Added` support for monitoring the EMASCurl network library.
2.2.1	`Fixed` a compatibility issue in Network Monitoring.
2.2.0	`Refactored` Performance Analysis, including startup, page, and Network Monitoring.
2.1.10	`Optimized` the underlying engine for Remote Log. `Added` a scheduled pull mode for Remote Log.
2.1.9	`Fixed` a compatibility issue between Remote Log and the Alibaba Cloud OSS SDK.
2.1.8	`Refactored` Remote Log and added a conditional pull mode.
2.1.7	`Refactored` lag analysis to support flame graphs, stack trees, and time slice views during lag events.
2.1.6	`Added` support for Dart exceptions in Flutter applications.
2.1.5	`Refactored` memory analysis and added optional Swift retain cycle detection.
2.1.4	`Fixed` a potential thread safety issue in the transport layer.
2.1.3	`Added` a flag to indicate if a device is jailbroken. `Fixed` issues in specific use cases to improve stability and compatibility.
2.1.2	`Fixed` an issue that caused memory analysis to crash in highly concurrent scenarios.
2.1.1	`Added` function-level symbolication for call stacks in Crash Analysis. This enables preliminary issue identification even when symbol files are not uploaded.
2.1.0	`Added` memory analysis features, including large object monitoring, memory leak detection, and allocation stack tracing for out-of-memory (OOM) scenarios.
2.0.0	`Refactored` and consolidated the Crash Analysis, Performance Analysis, and Remote Log SDKs into a single Mobile Monitoring SDK to simplify integration.
1.0.0	Initial release.

Sub-product version history

Note

As of April 14, 2025, the Mobile Monitoring SDK incorporates the Crash Analysis, Performance Analysis, and Remote Log SDKs. Consequently, these individual SDKs are no longer maintained, and their version histories are not updated.

Crash Analysis

Version	Description
2.1.0	`Optimized` the crash reporting mechanism.
2.0.0	`Refactored` crash collection. `Added` OOM monitoring. `Added` support for App Extension integration. `Deprecated` monitoring for certain types of exceptions. `Refactored` Abort signal monitoring.
1.2.0	Added support for custom errors. Added support for custom information in crash reports.
1.1.0	Initial release.

Performance Analysis

Version	Description
1.2.3	Optimized parameter validation and log levels.
1.2.2	Optimized Network Monitoring.
1.2.1	The initialization API now requires the `AppRsaSecret` field for reporting Network Monitoring data.
1.2.0	Added the build number to reported data. Optimized package dependencies.
1.1.1	Released the Network Monitoring feature.
1.0.0.1	Initial release.

Remote Log

Version	Description
1.1.1	Streamlined dependencies.
1.0.2	Changed the packaging format to XCFramework to fully support the Apple silicon (M1) simulator architecture. Optimized SDK performance.
1.0.1.2	Fixed an issue with incorrect log writing across midnight. Added the ability to set a maximum log file size.
1.0.1.1	Optimized code. Added proactive reporting.
1.0.0.1	Initial release.