View local logs-Mobile Platform as a Service(mPaaS)-阿里云帮助中心

Find and inspect mPaaS SDK log files stored on your Android device.

Log storage path

The SDK determines the storage path based on the release_type field in assets/channel.config.

Condition	Storage mode
`release_type` is `dev`, `test`, or `testpre`	Offline mode
`release_type` is `release`	Online mode
`assets/channel.config` is absent or `release_type` is not set, and the APK is a debug build	Offline mode
`assets/channel.config` is absent or `release_type` is not set, and the APK is a release build	Online mode

Storage paths and post-upload behavior by mode:

Mode	Path	After upload
Online mode	`/data/data/[PackageName]/files/mdap`	Local copy is deleted.
Offline mode	`/sdcard/Android/data/[PackageName]/files/mdap`	Local copy is moved to `/sdcard/Android/data/[PackageName]/files/mdap/upload` as a backup. The backup filename is prefixed with a timestamp.

Log files follow this naming format: (Timestamp_)process name-business code.

The business code (bizType) identifies the log type:

Log type	`bizType` value
Active device/user log	`mPaaSAliveAndroid`
App startup time log	`mPaaSLaunchAndroid`
Crash log	`mPaaSCrashAndroid`
Lag log	`mPaaSLAGAndroid`
Stuck log (Application Not Responding)	`mPaaSANRAndroid`
Custom event log	The `bizType` passed in when the tracking is created. Defaults to `UserBehaviorAndroid` if no `bizType` is provided.
Automation log	`mPaaSAutomationAndroid`

The following table maps each log type to its log model and key field values.

Log type	Log model	Key fields
Active device log	Log model > Behavior tracking	Field 16 (tracking ID): `reportActive`
Active user log	Log model > Behavior tracking	Field 16 (tracking ID): `login`
App startup time log	Log model > Performance tracking	Field 12 (performance ID): `performance`; field 13 (performance category): `time_startup`
Crash log	Log model > Performance tracking	—
Lag log	Log model > Performance tracking	—
Stuck log	Log model > Performance tracking	—
Custom event log	Log model > Behavior tracking	Field 16 (event ID): the `logId` passed in when the tracking is created
Automation log	Log model > Automation tracking	Field 09 (behavior ID): `auto_openPage` (page automation)