Moloco mediation adapter initialization failure with AdMob Unity SDK

21 views
Skip to first unread message

Guri Jin

unread,
Jan 7, 2026, 5:14:37 AM (yesterday) Jan 7
to Google Mobile Ads SDK Developers

Hello

I am experiencing an issue related to the Moloco mediation adapter initialization when using AdMob in a Unity project, and I would like to ask for your assistance.

Environment

  • Unity

  • AdMob Unity SDK: 10.6.0

  • Moloco Unity SDK: 3.1.0

  • Mediation: Google AdMob

Issue
When running the app, the Moloco adapter fails to initialize and the following error is logged:

Adapter: GADMediationAdapterMoloco not ready
Adapter failed to initialize. HTTP 400 - Bad Request
(state = Not Ready)

Due to this issue, Moloco ads are not being served.

Questions

  1. Is this a known issue with the combination of AdMob Unity SDK 10.6.0 and Moloco Unity SDK 3.1.0?

  2. Are there any known compatibility issues or required configuration changes?

  3. If this issue is environment-specific, could you please advise on possible causes and recommended troubleshooting steps?

If needed, I can provide additional logs or configuration details.

Thank you very much for your support.

Mobile Ads SDK Forum Advisor

unread,
Jan 7, 2026, 11:53:58 AM (22 hours ago) Jan 7
to liayu...@gmail.com, google-adm...@googlegroups.com

Hi,

Thank you for reaching out to Google Mobile Ads Support team.

I understand you are encountering initialization errors with the Moloco adapter. The "HTTP 400" error you described is caused by an incompatibility between the specific SDK versions you are using.

Regarding your question, the Moloco Unity SDK version 3.1.0 is not compatible with the Google Mobile Ads Unity Plugin v10.6.0. For plugin version 10.6.0, the supported Moloco Unity SDK versions are 3.16.4 and 3.16.5.

We recommend upgrading the Moloco Unity SDK to one of the supported versions and re-testing the integration.

You can find the official compatibility and integration details in the documentation below:
https://developers.google.com/admob/unity/mediation/unity

Please let us know if the issue persists after updating,


Thanks,
 
Google Logo Mobile Ads SDK Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5
[2026-01-07 16:52:51Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01wno39:ref" (ADR-00348940)



Guri Jin

unread,
4:37 AM (5 hours ago) 4:37 AM
to Google Mobile Ads SDK Developers

Hello AdMob Team,

According to the attached image, testing was conducted using Google Mobile Ads Unity Plugin version 10.6.0.

In our current setup, initialization works without any issues on Android. However, on iOS, initialization consistently fails with an HTTP 400 (Bad Request) error.

We are unable to find any official information or documentation related to Moloco iOS SDK version 3.16.5. Additionally, if Moloco iOS SDK version 4.1.2.0 has been tested and validated with Google Mobile Ads Unity Plugin 10.6.0, we would like to understand why this initialization error is occurring only on our side.

Could you please advise on:

  • Whether Moloco iOS SDK 4.1.2.0 is fully supported and validated with Google Mobile Ads Unity Plugin 10.6.0

  • Any known issues or configuration requirements on iOS that could lead to an HTTP 400 error during initialization

  • Where we can find official compatibility or test information regarding Moloco SDK versions (including 3.16.5, if applicable)

Any guidance or clarification would be greatly appreciated.

Thank you for your support.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2026년 1월 8일 목요일 AM 1시 53분 58초 UTC+9에 Mobile Ads SDK Forum Advisor님이 작성:
스크린샷 2026-01-08 오전 9.11.05 1.png
Reply all
Reply to author
Forward
0 new messages