View local logs - Mobile Platform as a Service - Alibaba Cloud Documentation Center

This guide walks you through the steps to fast find the local logs you want to view.

Log storage path

The log storage path is determined by the release_type field in assets/channel.config.

If the value of this field is dev, test, or testpre, logs are stored in offline mode. If the value is release, logs are stored in online mode.
If no assets/channel.config file is available or the release_type field is not specified:
- The offline mode applies when the APK package is a debug package.
- The online mode applies when the APK package is a release package.

Storage path:

In online mode, log files are stored in /data/data/[PackageName]/files/mdap. After a log file is uploaded, the local one is deleted.
In offline mode, log files are stored in /sdcard/Android/data/[PackageName]/files/mdap. After a log file is uploaded, the local one is moved to /sdcard/Android/data/[PackageName]/files/mdap/upload for backup. The timestamp is added as the file name prefix of the backup file.

Log file name

Log files are named in the following format: (Timestamp_)process name-business code. The business code (bizType) varies with the log type as follows:

Active device/user log: mPaaSAliveAndroid.
App startup time log: mPaaSLaunchAndroid.
Crash log: mPaaSCrashAndroid.
Lag log: mPaaSLAGAndroid
Stuck log: mPaaSANRAndroid
Custom event log: bizType passed in when tracking is created. If no bizType is passed in, the business code is UserBehaviorAndroid by default.
Automation log: mPaaSAutomationAndroid.

Log content format

Active device log: See Log model > Behavior tracking. In the content, the value of field 16 (tracking ID) is reportActive.
Active user log: See Log model > Behavior tracking. In the content, the value of field 16 (tracking ID) is login.
App startup time log: See Log model > Performance tracking. In the content, the value of field 12 (performance ID) is performance and the value of field 13 (performance category) is time_startup.
Crash log: See Log model > Performance tracking.
Lag log: See Log model > Performance tracking.
Stuck log: See Log model > Performance tracking.
Custom event log: See Log model > Behavior tracking. In the content, field 16 (event ID) corresponds to the logId passed in when a tracking is created.
Automation log: See Log model > Automation tracking. In the content, the value of field 09 (behavior ID) is auto_openPage which indicates page automation.

What to do next

Upload logs