This document details the process of troubleshooting mPulse SDK with your Android application.
MPulse SDK Android
- Check the API Key/ License used in the app.
- Remove any Empty space in API Key/ License
- Verify the akamai_sdk_init.xml with the below structure :
- Config received in app - If config is not received then API Key/ License is not entered correctly or limit(threshold) for Beacons is reached for the app.
- Config - if all the metrics and other information are added (you can check the URL in the browser). If any settings are added on Soasta portal ,eg you added a Metrics, this will take a couple of minutes to reflect in config.
- Check for third party framework used for network and image calls, interceptors will be required if you are using any of these Retrofit/OkHttp/Picasso, if you are using any other 3rd party lib do let us know we could provide interceptors for the same.
- In order to accelerate traffic originated from WebViews, the SDK provides the following custom WebViewClient.
- AkaWebViewL21Client - For Android API level 21 and above.
- AkaWebViewL15Client - For Android API level 15 and above.
- Both WebViewClients delegate all network calls via the MAP SDK library internally. The only difference between the two is that the L21 WebViewClient uses newer APIs added in level 21 and above.
- To gather more debug logs, enable debug logs in code:
Corner Cases :
- Reports not available
- Check in the SDK logs, if SDK is initialized successfully.
- Check the Beacon Rate Limiting applied at the tenant level, some customers apply it to cut the budget - Beacon Rate Limiting
- Config is not applied
- When config is not applied to SDK, none of the functionality will work for the SDK, so it's important that config is applied.