June 2, 2023
If you need to test an integration to make sure your game is making the right network calls to Chartboost, use a Web debugging proxy like Charles – which you can try for free – to do it.
Because all of our iOS and Android SDKs require an SSL proxying certificate, you’ll need to download one and add it to your test devices – this lets the Charles SSL HTTPS request make it to our servers.
To start, download the Charles Proxying Certificate, then see below for OS-specific instructions:
Things are simple on the Android side – you’ll just need to copy the certificate to your mobile device, then open it with any file explorer app. (Note: Some Android devices won’t be able to install the certificate – if you run into this problem, write to us for assistance.)
Note that on iOS 10 and later you must then go into Settings > General > About > Certificate Trust Settings and enable the Charles certificate to be trusted.
This section applies only for Android applications
In order for Charles to record your application SSL traffic, you will need to add the following lines under the path res/xml/network_security_config.xml:
You also need to add the following line to your AndroidManifest.xml
Once you’re all set up, use the steps below to get ready for each testing session:
The very first calls you should see – provided you filtered for Chartboost as mentioned above – is the Chartboost initialization calls:
This is how the initialization calls you’ve added to your code should appear. Because our system needs to receive these calls on every bootup to accurately convert installs and track performance, they must not be dependent on prior network requests or user actions.
After logging these calls, you can consult the content of the same and the respective responses in the lower panel as shown below:
If you’re seeing a 4XX response, double-check your code for the right Chartboost App ID and App Signature.
You can also use Charles to verify successful interstitial calls; they’ll look something like this: