Mobile Analysis Service FAQ

• How to check if the client is connected correctly

• 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

• No data is displayed on the custom dashboard

• 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.

Data does not appear in the console after the client is connected

Client logs are uploaded to the log server only when specific conditions are met, such as reaching a local log count threshold or the app running in the background for a set period. During testing, you can manually force an instant log upload to see data immediately.

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

To troubleshoot this issue:

1. Check whether the dashboard logs have been uploaded to the server. 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 whether the app is triggering them:

     1. Disconnect the mobile phone from the network, and then trigger the log.

     2. 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/mdap or /sdcard/Android/data/[PackageName]/files/mdap. The log retention path depends on the value of the release_type field in assets/channel.config. For more information, see View local logs.

     3. After the client generates logs, use log replay again to check whether the logs are uploaded to the server.

        Log uploads are triggered only when the number of cached local logs reaches a threshold, which varies by log type. For debugging, go to Mobile Analysis Service > Log management> Configure uploading switch in the mPaaS console and set Uploaded log threshold to 1. This triggers an upload after a single log is cached locally. Restore the original value after debugging. For more information, see the log upload documents (Android log upload/iOS log upload).

2. If log replay shows that logs are still not uploaded to the server, review the Android instrumentation integration or iOS instrumentation integration document for your log type to identify errors. After you fix the instrumentation, repeat step 2 to confirm that logs are uploaded.

3. If logs are uploaded to the server but no data appears on the dashboard, verify that the log data format is correct.

   Compare the raw logs in Play back logs with the tagging log model to confirm the format. If the format is incorrect, refer to the log model for the corresponding tag type to correct it.

4. If you have confirmed that logs are uploaded to the server in the correct 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 crash logs must be symbolicated using the dSYM symbol file generated during app packaging.

To enable crash log symbolication, upload the dSYM symbol file on the Mobile Delivery Service > Delivery management page in the mPaaS console.