Data does not appear in the console after the client is connected
Event PV and UV are not visible after an event is created in the console
Event UV is always 0 after an event is created in the console
iOS client crash logs are not symbolicated in the Mobile Analysis Service console
How to check if the client is connected correctly
Check the local logs (Android/iOS) or query logs in the console to verify that the client is connected correctly.
Data does not appear in the console after the client is connected
Client logs are automatically uploaded to the log server only when certain conditions are met. For example, when the number of local logs reaches a specific threshold or the application runs in the background for a certain period. During testing, to see data immediately, you can manually force an instant log upload from the client.
For more information, see Manually upload Android logs or Manually upload iOS logs.
Event PV and UV are not visible after an event is created in the console
To see event page views (PV) and unique visitors (UV), ensure that:
The client is connected correctly. For more information, see How to check if the client is connected correctly.
Logs are uploaded to the log server. For more information, see the FAQ entry Data does not appear in the console after the client is connected.
A user triggers the event after it is created in the console.
Event UV is always 0 after an event is created in the console
Ensure that a user ID is set on the client. For instructions, see User ID.
No data is displayed on the custom dashboard
Follow these steps to troubleshoot the issue:
Check if the log reporting switch is enabled. In the console, choose Mobile Analysis Service > Log management > Configure uploading switch > Tracking point configuration from the navigation pane on the left. On the log switch list page, find the corresponding tag and make sure its reporting switch is enabled. For more information, see Configure the log reporting switch.
Check if the logs for the dashboard are uploaded to the server-side. Use the Log management > Play back logs feature in the console to query historical logs.
If you can find the corresponding logs, they have been uploaded. For more information, see Query historical logs.
If you cannot find the logs, check if the app is triggering them. Perform the following steps:
Before triggering the log, disconnect the mobile phone from the network, and then trigger the log.
After the app runs in the background, check the local log directory for the logs you want to query.
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 retention path depends on the value of therelease_typefield inassets/channel.config. For more information, see View local logs.
After the client generates the logs, use log replay again to check if the logs are uploaded to the server-side.
After a client generates logs, the upload is triggered only when the number of cached local logs reaches a certain threshold. This threshold can vary depending on the log type. To trigger an upload for debugging, go to the Mobile Analysis Service > Log management> Configure uploading switch page in the mPaaS console. Set Uploaded log threshold to 1. This setting specifies the number of logs in a local file that triggers an upload. After you finish debugging, restore the original value. For more information about triggering log uploads, see the log upload documents (Android log upload/iOS log upload).
If log replay shows that logs are still not uploaded to the server-side, check the Android instrumentation integration or iOS instrumentation integration document for your log type to find errors in the instrumentation process. After you correctly integrate the instrumentation as described in the document, perform step 2 again to ensure that logs are uploaded correctly.
If logs are uploaded to the server-side but no data appears on the dashboard, check if the log data format is correct.
Compare the raw logs in Play back logs with the tagging log model to confirm the log format. If the format is incorrect, refer to the log model for the corresponding tag type and correct the log format.
If you have followed these steps and confirmed that logs are uploaded to the server-side in the correct data format, but the dashboard still shows no data, search for the DingTalk group ID 145930007362 and join the group for assistance.
iOS client crash logs are not symbolicated in the Mobile Analysis Service console
iOS client crash logs must be symbolicated using the DSYM symbol file generated during packaging.
The iOS crash analysis feature supports crash log symbolication. For apps that require this feature, upload the DSYM symbol file on the Mobile Delivery Service > Delivery management page in the mPaaS console.