This topic describes common issues and troubleshooting methods for Mobile Analysis Service.
Data does not appear in the console after correct client integration
Event PV and UV data is not visible after creating an event in the console
iOS client crash logs are not symbolicated in the Mobile Analysis Service console
Check if the client is correctly integrated
View local logs (Android/iOS) or query logs in the console to check if the client is correctly integrated.
Data does not appear in the console after correct client integration
Client logs are automatically uploaded to the log server only when certain conditions are met, such as when the number of local logs reaches a specific threshold or the application runs in the background for a certain period. To see data sooner during testing, you can manually upload logs from the client to force an immediate upload.
For more information, see Manually upload Android logs or Manually upload iOS logs.
Event PV and UV data is not visible after creating an event in the console
To view event PV and UV data, ensure the following:
The client is correctly integrated. For more information, see Check if the client is correctly integrated.
Logs have been uploaded to the log server. For more information, see Data does not appear in the console after correct client integration.
The event was created in the console and then triggered by the user.
Event UV is always 0 after creating an event in the console
Ensure that a user ID is set on the client. For more information about how to set a user ID, see User ID.
No data is displayed on the custom dashboard
Troubleshoot the issue as follows:
Check if the log upload switch is enabled. Log on to the console. In the navigation pane on the left, choose Mobile Analysis Service > Log management > Configure upload switch > Event tracking configuration to go to the log switch list page. Check if the upload switch for the corresponding tag is enabled. Make sure the log upload switch is enabled. For more information, see Configure log upload switches.
Check if the logs for the dashboard are uploaded to the server. Use the Log management > Log playback feature in the console to query historical logs.
If you can find the logs, they have been uploaded. For more information, see Query historical logs.
If you cannot find the logs, check if the app has triggered them. Perform the following steps:
Before triggering the log, disconnect your phone from the network. Then, trigger the log.
After the app is moved to the background, check if the log you want to query exists in the local log directory.
iOS client: Logs are saved in the sandbox directory
Library > atrack > logs.Android client: Logs are saved in
/data/data/[PackageName]/files/mdapor/sdcard/Android/data/[PackageName]/files/mdap. The log storage path varies based on the value of therelease_typefield inassets/channel.config. For more information, see View local logs.
After the client generates the log, use log replay again to check if the log is uploaded to the server.
After the client generated logs, automatic log uploading is triggered only when the number of locally cached logs reaches the threshold. The threshold may vary depending on the log type. To facilitate debugging, you can go to the Mobile Analysis Service > Log management > Configure upload switch > Event tracking configuration page on the mPaaS console, and temporarily change the value of Upload quantity (the number of logs of the current type in the local file that triggers log reporting) to 1 to trigger log reporting. After the debugging is completed, change it back to the original number. For more information about triggering of log uploading, see the log upload documentation (Android log upload/iOS log upload).
If log replay shows that the logs are still not uploaded to the server, refer to the Android instrumentation or iOS instrumentation documentation based on the log type to check for errors in the instrumentation process. After you correctly integrate the instrumentation according to the document, perform Step 2 again to ensure that logs are uploaded normally.
If logs have been uploaded to the server but the dashboard shows no data, check if the log data format is correct.
Compare the raw logs in Log playback with the instrumentation log model to confirm if the log format is correct. If the log format is incorrect, refer to the log model for the corresponding instrumentation type and modify the log format.
If you have followed the preceding steps and confirmed that logs are uploaded to the server and the data format is correct, but the dashboard still shows no data, search for the group number 145930007362 to join the DingTalk group for assistance.
iOS client crash logs are not symbolicated in the Mobile Analysis Service console
iOS client crash logs require the dSYM symbol table file generated during packaging to be symbolicated.
The iOS crash analysis feature supports crash log symbolication. For apps that require this feature, upload the dSYM symbol table file on the Mobile Analysis Service > Performance analysis > iOS symbol table management page in the mPaaS console. For more information, see iOS Symbol Table Management.