googleads-mobile-unity: External Dependency Manager fails to resolve the MetaAudienceNetwork dependencies.

Any workaround/update on this yet? since this issue is so widespread, no version of the admob unity plugin is getting an Android build with meta mediation, shouldn’t it be a p1? any eta at least?

same problem here, using: Google Mobile Ads Unity Plugin v8.5.2 Meta Mediation Adapter [Version 3.11.0] UnityAds Mediation Adapter [Version 3.8.0] AppLovin Mediation Adapter [Version 6.9.1]

So, for a month I’m having build issues with Meta Audience Network mediation via AdMob

To recreate you just open any new unity project under any unity version, switch to android, download Google Ads Mobile SDK, resolve then add Meta Audience Network unity package from mediation page, resolve, the resolve will take a long time attempting to resolve and then timeout with few conflicting dependencies and the build will result in workers$actionfacade

Since meta mediation is important for me, i tried to go to previous versions where the build was fine but the build still failed, then i went to Meta Audience Network Unity Mediation Plugin Changelog page and tried every single new and previous version mentioned as built and tested there, with this same result once the mediation plugin is added

Without the meta plugin everything’s fine,

I looked a bit further, the EDM’s resolution attempts fails and it attempts to resolve 13 to 15 times, that’s what makes the resolve take so much time, seems like some dependency of meta is not available in their links.

This issue i think is from meta somehow, Meta is a very important mediation for us since we get around 40% of our revenue from meta, since this issue is so wide spread, i hope the team will take this as their first priority and come up with a fix fast.

Thanks in advance.

Hi Everyone,

We are aware of the issue and are currently looking into a fix.

Same problem for me, using identical mediation setup as luizjunior. Meta is the culprit - removing it and everything works fine.

Also for whatever reason when Meta is involved there are depency conflicts which causes a lot of depencies to get bumped to use the latest version (resulting in downloading versions that are not officially supported). For me it looks like this:

Some conflicting dependencies were found. The following dependency versions were modified: com.google.ads.mediation:applovin:11.10.1.0 --> com.google.ads.mediation:applovin:11.+ com.google.ads.mediation:facebook:6.15.0.0 --> com.google.ads.mediation:facebook:6.+ com.google.ads.mediation:unity:4.8.0.0 --> com.google.ads.mediation:unity:4.+ com.google.android.gms:play-services-ads:22.3.0 --> com.google.android.gms:play-services-ads:+ com.google.android.gms:play-services-auth:20.4.1+ --> com.google.android.gms:play-services-auth:+ com.google.android.gms:play-services-base:18.2.0 --> com.google.android.gms:play-services-base:+ com.google.android.gms:play-services-games:23.1.0+ --> com.google.android.gms:play-services-games:+ com.google.android.gms:play-services-nearby:17.0.0+ --> com.google.android.gms:play-services-nearby:+ com.google.android.play:review:2.0.1+ --> com.google.android.play:review:+ com.google.android.ump:user-messaging-platform:2.1.0 --> com.google.android.ump:user-messaging-platform:+ com.google.firebase:firebase-analytics:21.3.0 --> com.google.firebase:firebase-analytics:+ com.google.firebase:firebase-auth:22.1.1 --> com.google.firebase:firebase-auth:+ com.google.firebase:firebase-common:20.3.3 --> com.google.firebase:firebase-common:+ com.google.firebase:firebase-config:21.4.1 --> com.google.firebase:firebase-config:+ com.google.firebase:firebase-database:20.2.2 --> com.google.firebase:firebase-database:+ com.google.firebase:firebase-functions:20.3.1 --> com.google.firebase:firebase-functions:+ com.unity3d.ads:unity-ads:4.8.0 --> com.unity3d.ads:unity-ads:+