Contrary to what the source says:
|
// This method won't be called for custom events. |
|
override fun initialize( |
|
context: Context, |
|
initializationCompleteCallback: InitializationCompleteCallback, |
|
list: List<MediationConfiguration> |
|
) { |
|
return |
|
} |
it is called, very much so, and expects to be called back as:
initializationCompleteCallback.onInitializationSucceeded()
Otherwise, the GMS will wait for the timeout, note a failure with the adapter and won't use it at all.
So:
override fun initialize(context: Context, initializationCompleteCallback: InitializationCompleteCallback, list: List<MediationConfiguration>) {
Log.d(TAG, "initialize()")
HwAds.init(context);
initializationCompleteCallback.onInitializationSucceeded()
}
See the documentation at: https://developers.google.com/ad-manager/mobile-ads-sdk/android/custom-events/setup
Contrary to what the source says:
huawei.ads.admob_mediation/admob_mediation/src/main/java/com/hmscl/huawei/admob_mediation/all_ads.kt
Lines 77 to 84 in deb4ef1
it is called, very much so, and expects to be called back as:
Otherwise, the GMS will wait for the timeout, note a failure with the adapter and won't use it at all.
So:
See the documentation at: https://developers.google.com/ad-manager/mobile-ads-sdk/android/custom-events/setup