UnityAdapter not linked on iOS
mwelk opened this issue · 4 comments
mwelk commented
UnityAds mediation on iOS throws following error message:
<Google> Cannot find an ad network adapter with the name(s): com.google.ads.mediation.unity.UnityAdapter. Remember to link all required ad network adapters and SDKs, and set -ObjC in the 'Other Linker Flags' setting of your build target.
Adverts-Mediation: 5.1.0
Adverts: 10.1.037
AIR: 33.1.1.300
marchbold commented
Can you provide some additional information as to how to replicate this?
mwelk commented
The log appears always at start:
default 09:15:44.429879+0100 SmeetVMMobile64-debug [AdvertsMediator] setup AdMob at 45.0
default 09:15:44.430669+0100 SmeetVMMobile64-debug com.distriqt.Adverts::DTADAdvertsManager::isPlatformSupported: adman
default 09:15:44.431291+0100 SmeetVMMobile64-debug com.distriqt.Adverts::DTADAdvertsManager::setup: admob accountId: ca-app-pub-xx~xx
default 09:15:44.501060+0100 SmeetVMMobile64-debug [ironSource SDK] API: IronSource: setConsent true
default 09:15:44.511693+0100 SmeetVMMobile64-debug com.distriqt.Adverts::DTADAdvertsManager::initialise
default 09:15:44.511934+0100 SmeetVMMobile64-debug com.distriqt.Adverts::DTADGoogleAdMob::initialise
default 09:15:44.512989+0100 SmeetVMMobile64-debug [ironSource SDK] EVENT: {
eventId = 40;
eventSessionId = "AEC2E6E8-AD5C-49BC-8CFB-C29DB69738D8";
provider = Mediation;
timestamp = 1607501744501;
}
default 09:15:44.627810+0100 SmeetVMMobile64-debug com.distriqt.Adverts::DTADGoogleAdMob::initialised
default 09:15:44.937618+0100 SmeetVMMobile64-debug com.distriqt.Adverts::DTADGoogleAdMob::createAdView
default 09:15:44.937758+0100 SmeetVMMobile64-debug com.distriqt.Adverts::DTADGoogleAdMobAdView::[2903205B-7B9C-49F7-BB1E-D2ABA160325C]::setAdaptiveAdSize: -1 orientation: auto
default 09:15:44.937931+0100 SmeetVMMobile64-debug com.distriqt.Adverts::DTADGoogleAdMobAdView::[2903205B-7B9C-49F7-BB1E-D2ABA160325C]::setAdaptiveAdSize: [320.000000,50.000000]
default 09:15:44.941236+0100 SmeetVMMobile64-debug com.distriqt.Adverts::DTADGoogleAdMobAdView::[2903205B-7B9C-49F7-BB1E-D2ABA160325C]::setAdUnitId: ca-app-pub-xx/xx
default 09:15:44.948699+0100 SmeetVMMobile64-debug com.distriqt.Adverts::DTADGoogleAdMob::createRewardedVideoAd
default 09:15:44.949027+0100 SmeetVMMobile64-debug com.distriqt.Adverts::DTADGoogleAdMobRewardedVideoAd::setAdUnitId: ca-app-pub-xx/xx
default 09:15:44.951503+0100 SmeetVMMobile64-debug com.distriqt.Adverts::DTADGoogleAdMobRewardedVideoAd::load: ...
default 09:15:44.956111+0100 SmeetVMMobile64-debug <Google> To get test ads on this device, set: GADMobileAds.sharedInstance.requestConfiguration.testDeviceIdentifiers = @[ @"xx" ];
default 09:15:45.147576+0100 SmeetVMMobile64-debug AppLovinAdapter: AppLovin adapter version: 6.14.8.0
default 09:15:45.147699+0100 SmeetVMMobile64-debug AppLovinAdapter: AppLovin SDK version: 6.14.8
default 09:15:47.364001+0100 SmeetVMMobile64-debug <Google> Cannot find an ad network adapter with the name(s): com.google.ads.mediation.unity.UnityAdapter. Remember to link all required ad network adapters and SDKs, and set -ObjC in the 'Other Linker Flags' setting of your build target.
default 09:15:47.369293+0100 SmeetVMMobile64-debug <Google> Cannot find an ad network adapter with the name(s): com.google.ads.mediation.facebook.FacebookAdapter. Remember to link all required ad network adapters and SDKs, and set -ObjC in the 'Other Linker Flags' setting of your build target.
default 09:15:47.369987+0100 SmeetVMMobile64-debug <Google> Cannot find an ad network adapter with the name(s): com.google.ads.mediation.ironsource.IronSourceRewardedAdapter. Remember to link all required ad network adapters and SDKs, and set -ObjC in the 'Other Linker Flags' setting of your build target.
I've tested the adverts implementation only with test ads at the moment ant can't really tell if mediation with ironSource will work. Thought the log entry is worth it to open a task to investigate.
mwelk commented
It seems that adding the IDFA-ANE solved the problem.
marchbold commented
Could you verify this is still happening with the latest SDK version?