The logs related to the MOCA SDK are very helpful to find configuration errors. The log starts with these two lines:
I/MOCA: Initializing MOCAPlugin
I/MOCA: Init MOCA SDK, version x.x.x
This shows that the plugin has started, and which is the version of the MOCA SDK. Below these lines you will typically find:
W/MOCA: Service geo-tracking was not permitted by the user. Service is disabled now.
W/MOCA: Service proximity was not permitted by the user. Service is disabled now.
I/MOCA: Event Tracking : [RUNNING]
I/MOCA: Remote Push : [RUNNING]
I/MOCA: Geo Tracking : [STOPPED]
I/MOCA: Proximity : [STOPPED]
W/MOCA: Indoor location not available
I/MOCA: Indoor Analytics: [UNAVAILABLE]
I/MOCA: Recommendations : [STOPPED]
These modules are dependant on permissions and/or configuration. You can see if the permissions are granted/denied, the service is running/stopped or if you don't have an expected module (not available). This instance shows us that Geo Tracking and Proximity are both stopped, caused by a permission that was denied (Location permission).
Not all notifications are critical, but Errors are to be checked in depth as they impact directly on the stability and usability of the SDK:
ID | Meaning |
| I/ | Info |
| W/ | Warning |
| E/ | Error |
| D/ | Debug |
Warnings are good indicators of what can trigger an unexpected behavior, but should not impact on the stability and usability of the SDK.