The following are some common problems you may encounter when using MAS and how to troubleshoot them.
Why the data is invisible in the console after the client is integrated correctly?
Why are the event PV and UV invisible after an event is created in the console?
Why is the event UV always displayed as 0 after an event is created in the console?
How to check whether the client is integrated correctly?
You can view local logs (Android/iOS) or Query logs in the console to check whether the client is integrated correctly.
Why the data is invisible in the console after the client is integrated correctly?
The client log will be automatically reported to the log server only when certain conditions are met (such as a certain number of local logs or the Application is pushed to the background for more than a certain period of time). During testing, in order to see the data as soon as possible, you can force the log to be reported immediately by manually reporting on the client.
For more information, see Report logs manually - Android or Report logs manually - iOS.
Why are the event PV and UV invisible after an event is created in the console?
To view the event PV and UV, ensure that:
The client is integrated correctly. For more information, see How to check whether the client is integrated correctly?.
Logs are reported to the log server. For more information, see Why the data is invisible in the console after the client is integrated correctly?.
The event created in the console has been triggered.
Why is the event UV always displayed as 0 after an event is created in the console?
Ensure that a user ID is set on the client. For more information, see User ID.
Why no data is displayed in the custom dashboard?
Perform the following steps to troubleshoot the issue:
Check whether the log upload switch is turned on. Log in to the mPaaS console, on the left navigation pane, click Mobile Analysis Service > Log management > Configure upload switch > Event tracking configuration to go to the log switch list page, and check if the log upload switch is turned on for the specified tracking configuration. If not, just turn the switch on. For more information, see Switch configuration.
Check whether the log that corresponds to the dashboard is uploaded to the server. In the console, click Log management > Log playback to query history logs.
If the log that corresponds to the dashboard is found, it means the log has been uploaded. For more information, see Query history logs.
If the log that corresponds to the dashboard is not found, check whether the App has triggered log generation. Perform the following steps:
Disconnect the mobile from network, and then trigger log generation.
After the App switches to background, go to the local log directory to check whether the queried log exists.
iOS clients: The log is stored in the sandbox directory:
Library > atrack > logs.Android clients: The log is stored in
/data/data/[PackageName]/files/mdapor/sdcard/Android/data/[PackageName]/files/mdap. The logging path varies depending on therelease_typefield inassets/channel.config. For more information, see View local logs.
After the client triggered log generation, playback the log again to check whether 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 Upload logs from Android client or Upload logs from iOS client.
If you find that the logs are still not reported to the server through log playback, refer to Active device/user log or Add activity report log according to the log type to check whether there is any error in the tracking point integration process. After correctly integrating the tracking point according to the document, proceed to step 2 to ensure that the logs are reported normally.
If logs are uploaded to the server but no data is displayed on the dashboard, check whether the log data format is correct.
Compare the original logs in log playback with the tracking log model to check whether the log data format is correct. If the log data format is incorrect, modify the format based on the log models for different types of tracking.
After you have performed the preceding steps and ensured that the logs in correct format have been uploaded to the server, but still no data is displayed on the dashboard, please search for the group number 145930007362 with DingTalk to join the group for further communication.
Why the iOS crash logs in the MAS console are not parsed?
The iOS client's crash log parsing requires the packaged and generated dSYM symbol table.
The iOS crash statistics feature supports symbolicating crash logs. To use this feature in your App, you must upload the dSYM file on the Mobile Analysis Service > Performance analysis > iOS symbol table management page in the mPaaS console. For more information, refer to iOS symbol table management.