Skip to content

Troubleshooting

The following section describes many common issues you may find when integrating XMediator. Ensure you have followed the integration steps.

Problem #1

I'm not able to see ads, whether I set the test flag to true or false

Reason:

If you have already installed an adapter and you are still not receiving any ads, there might be a missing configuration.

Solution:

Ensure your app-ads.txt is properly set, reachable and updated with the adapters you have installed. If you have just created it, take into account that some networks may experience a delay in order to crawl and verify your app-ads.txt file.

Problem #2

I'm not able to see non-test ads even if I set the test flag to false and use a production placement Id

Reason:

Your device is being recognized as a test device.

Solution:

There are many things you could try to start receiving production ads:

  • Be sure you are building your app in release mode.

  • Run your app on a physical device, not an emulator/simulator.

  • Some networks provide a way to configure your device as a test device, so every time a request comes from these devices, a test ad is returned. Check that the device you are using is not whitelisted in the network's website.

  • In case you are testing Google Ads integration, try uploading your app to App Bundle Explorer or Internal App Sharing and download your app from there.

Problem #3

AppLovin SDK stopped working since my last update

Reason:

AppLovin introduced a new initialization API in it's release 12.4.0, which is not compatible with a legacy configuration. This problem affects not only X3M but any other mediation that uses AppLovin's new initialization API.

Solution:

Remove any entry for applovin.sdk.key in your AndroidManifest.xml. For more information, please visit AppLovin's documentation.

Problem #4

I'm getting compilation errors related to incompatible Kotlin versions, similar to the following:

Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The actual metadata version is 2.1.0, but the compiler version 1.9.0 can read versions up to 2.0.0.

Reason:

Your project depends on a version of Kotlin lower than 2.0.0, and a transitive dependency was compiled against a higher version of Kotlin.

Solution:

Either update your project's Kotlin version or remove the transitive dependency. (for example, Meta Audience's SDK v19.0.0 is one of the SDKs that depends on Kotlin 2.x.x)