FAQ - uc-union/union-ads-sdk-demo GitHub Wiki

Things to note

About SDK

Check if Ad SDK is implemented according to the steps described in the document, including AndroidManifest.xml configuration, use of initialization interface, use of each ad interface and whether a correct pub for corresponding ad type is used.

About Mediation

Ad SDK currently supports ads from Facebook, Google and UC Union, and will select ads based on certain strategy and return to users for display. If you want to display ads from a specific source, your test client-side device should satisfy the following requirements on top of certain configuration requirements for SDK backend.

Facebook

Be sure:

  1. Integrate the latest version of Facebook Audience Network SDK in your developing application.

  2. Install the latest version Facebook app in your test device.

  3. Sign in a facebook account in Facebook app.

More refer to Facebook Mediation Guide.

AdMob

Be sure:

  1. Integrate the latest Google-play-service-ads SDK in your developing application.

  2. A test device with Google play service installed. (Not necessarily but highly recommended)

More refer to AdMob Mediation Guide.

FAQs

Which character encoding does Ad SDK use?

Ad SDK uses UTF-8 encoding, please use UTF-8 programming environment when implementing ads and importing example program, otherwise unreadable codes will occur.

Which version of Android SDK is compatible with Ad SDK?

Android SDK is compatible with SDK for Android 2.3.3 and above (API Level >= 10), there might be some compatibility issues for versions below 2.3.3.

Wrong pub

If a wrong pub is used when displaying ads, error will occur. In the case of error, please check if your pub is correct for the display ad.

For example two different pub are needed for banner and interstitial ads to differentiate different types of ads.

Crash at first start-up after a clean install【Pay attention to the following problem in Application.onCreate

On some Android 6.0 devices, crash might occur when you start up the SDK at the first time with a clean install. This is a bug of the Android system. The bug causes crashes because Application.onCreate is not used, and the core initialization process of Ad SDK is not used.

We will solve this problem internally in subsequent SDK version. One solution for developers will be to set allowbackup flag to false of Application in AndroidManifest.xml.

More discussion for this issue and be found here.

Contact Us

If you encounter any problem when using Android SDK, or should you have any opinion or suggestion for SDK, please contact customer service.

Next Steps

⚠️ **GitHub.com Fallback** ⚠️