New Support Ticket
Check Ticket Status
It's simple to check if Soomla SDK is integrated and working properly.
All you need to do is look at the console logs.
Check if the Ad Network SDKs are discovered and supported:
Once you open the app and Soomla SDK is initialized, you'll start seeing INFO logs for each ad network SDK that have integrated within your app. An example of such log is:
SOOMLA Agent SDK: -------------- MoPub connector 4.1.2 --------------
MoPub SDK version: 5.6.0
SDK Versions supported: 4.7.0 - 5.6.0
Status: OK
As you can see, the log shows you the detected ad network SDK version and the SDK versions supported by Soomla. If the status is 'OK' then this ad network SDK is checked and approved.
Important Testing Notes
- Make sure you see logs for each one of the ad networks that you work with.
- Make sure each one of the ad networks you work with are confirmed with Status 'OK'.
- If the Status of and ad network is not 'OK', make sure to fix the issue and rerun the app to confirm the Status turns to 'OK'.
Example Log Issues
SOOMLA SDK: RemoteConfig: Error getting config from server: 403
This means that Soomla SDK was initialized with the wrong appkey which does not exist.
Also, this error is shown when Soomla SDK was shutdown.
You can check the app settings on Soomla dashboard to see if this is the case.
SOOMLA Agent SDK: -------------- Facebook connector 4.1.2 --------------
Facebook SDK version: Not fetched - please make sure your version is supported
SDK Versions supported: 4.25.0 - 5.2.0
Status: OK
This means that Soomla couldn't fetch the version of Facebook SDK and is asking you to manually confirm that you're using a supported version. Once you manually confirmed that you're good to go.
[*** ERROR ***] SOOMLA Agent SDK: -------------- IronSource connector 1.1.3 --------------
[*** ERROR ***] SOOMLA Agent SDK: IronSource SDK version: 6.16.1
[*** ERROR ***] SOOMLA Agent SDK: SDK Versions supported: 6.5 - 6.15.0
[*** ERROR ***] SOOMLA Agent SDK: Status: ERROR
[*** ERROR ***] SOOMLA Agent SDK: Message: IronSource SDK version 6.16.1 is not yet supported by the connector
[*** ERROR ***] SOOMLA Traceback: IronSource sdk version 6.16.1 is not supported by ironsource version 1.1.3
Here the status is ERROR and the reason is that the remote Soomla connector version does not support the ad network SDK. Please contact Soomla support to check this.
SOOMLA Agent SDK: -------------- Tapjoy connector 4.1.3 --------------
Tapjoy SDK version: 12.2.1
SDK Versions supported: 11.8.0 - 12.2.1
Status: ERROR
Message: Tapjoy sdk version 12.2.1 requires Soomla sdk version 4.9.4 or newer
Sometimes there is a dependency between the remote Soomla connector version and Soomla SDK version. In this example the connector was updated (remotely) while Soomla SDK was not. Please try to upgrade Soomla SDK to the latest version.
SOOMLA Agent SDK: -------------- Soomla agent 5.1.1 --------------
[*** WARNING ***] SOOMLA Agent SDK: -------------- Inneractive connector --------------
[*** WARNING ***] SOOMLA Agent SDK: Status: MISSING
[*** WARNING ***] SOOMLA Agent SDK: Message: Found Inneractive sdk but missing Soomla Inneractive connector
This issue might indicate that on the current Soomla SDK version the remote Soomla connector for this specific network is not yet supported. Please try to upgrade Soomla SDK or contact Soomla support.
SOOMLA Agent SDK: -------------- Flurry connector 4.1.3 --------------
Flurry SDK version: 11.6.0
SDK Versions supported: 9.0.0 - 11.6.0
Status: ERROR
Message: Failed to initialize connector
SOOMLA Agent SDK: -------------- Flurry connector --------------
Status: ERROR
Message: Failed to create connector
These two are unexpected issues. Please contact Soomla support to check this
Check if Soomla SDK captures ad impressions:
When setting the log level to Debug or Verbose you will be able to see the events that Soomla SDK is trying to send to the server. These are some of the log messages you should look for after viewing an ad:
SOOMLA SDK: ...: Trying to send event: ad_displayed and extra info: {...}
SOOMLA SDK: ...: Trying to send event: iab_displayed and extra info: {...}
SOOMLA SDK: ...: Trying to send event with name: ad_displayed
SOOMLA SDK: ...: Trying to send event: imp_extra with extra info: {...}
When testing tags, you can look for these log messages:
SOOMLA SDK: ...: Trying to send event: add_tags with extra info:
{"tags":["tag1","tag2"]}
Important Testing Notes
- After you view an ad, Soomla SDK caches the event and does not send it right away.
To force Soomla SDK to send the events you will need to put the app to the background and bring it back to the foreground.