Our documentation is changing, please click here to enjoy it!

Skip to end of metadata
Go to start of metadata

Find your A4SID (or Device ID or Mobinaute ID)

If you need to get the Accengage Device ID (or "Mobinaute Id") of the user, use the following method:

Restrict SDK connection

You can temporarily restrict the connections in order to tell our SDK to stop flushing network requests.

All requests will be locked until you use setRestrictedConnection(false). In order to know if the connection is restricted for our SDK, please use:

Specific for Android

Activate Logs

To enable logs in the console, you can modify the following value of BMA4SCordovaConfig.json :

You will have to rebuild your app in order to see the logs

Dependencies conflicts 

If you encounter conflicts regarding Google Play Services versions and Firebase versions, you have two possibilities : 

  • use the same versions as our plugin ones
  • override the versions of our plugin


Please find below an example for the second point : 

You'll have to modify the two following files.



Please see the Android Troubleshooting and Android Optional Code.

Specific for iOS

Activate Logs

To enable logs in the console, you can use the method :

To enable logs in the Accengage logging application, please follow this documentation.


AppStore unsupported architectures 

Accengage's frameworks contains architectures for iPhone simulators (x86_64 and i386). If you try to submit an application that contains these architectures to AppStore, it will be rejected by Apple.

To fix that behaviour, go on Build Phases on XCode and add a new Run Script Phase. Then paste the content of this script, in order to eliminate simulator architecture slices.


The order of the build phases is important. The Run Script phase must be added after (or placed below) the Copy Files phase.


Please see the iOS Troubleshooting.


  • No labels