Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Bug: error log of "android.os.RemoteException: Method is not found at com.google.android.gms.ads.mediation.Adapter.loadNativeAdMapper"

107 views
Skip to first unread message

Liran Barsisa

unread,
Jan 27, 2025, 9:26:47 AMJan 27
to Google Mobile Ads SDK Developers
This is what I get:

```
android.os.RemoteException: Method is not found (Ask Gemini)
                                                                      at com.google.android.gms.ads.mediation.Adapter.loadNativeAdMapper(SourceFile:5)
                                                                      at com.google.android.gms.internal.ads.zzbqf.zzz(SourceFile:289)
                                                                      at com.google.android.gms.internal.ads.zzbpg.zzdD(SourceFile:630)
                                                                      at com.google.android.gms.internal.ads.zzayb.onTransact(SourceFile:21)
                                                                      at android.os.Binder.transact(Binder.java:1243)
                                                                      at m.ant.bh(:com.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:8)
                                                                      at com.google.android.gms.ads.internal.mediation.client.f.r(:com.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:28)
                                                                      at com.google.android.gms.ads.nonagon.render.bp.b(:com.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:45)
                                                                      at com.google.android.gms.ads.nonagon.render.dx.a(:com.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:11)
                                                                      at com.google.android.gms.ads.nonagon.util.concurrent.t.call(:com.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:3)
                                                                      at m.ckq.a(:com.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:3)
                                                                      at m.cjx.run(:com.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:19)
                                                                      at m.ckr.run(:com.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:5)
                                                                      at android.os.Handler.handleCallback(Handler.java:991)
                                                                      at android.os.Handler.dispatchMessage(Handler.java:102)
                                                                      at m.bbw.a(:com.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:1)
                                                                      at com.google.android.gms.ads.internal.util.f.a(:com.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:1)
                                                                      at m.bbw.dispatchMessage(:com.google.android.gms.policy_ads_fdr_dynamite@244410211@244410203017.691591528.691591528:1)
                                                                      at android.os.Looper.loopOnce(Looper.java:232)
                                                                      at android.os.Looper.loop(Looper.java:317)
                                                                      at android.app.ActivityThread.main(ActivityThread.java:8787)
                                                                      at java.lang.reflect.Method.invoke(Native Method)
                                                                      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:591)
                                                                      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:871)
```

Dependency:

```
implementation("com.google.android.gms:play-services-ads:23.6.0")
```

I also use various ad-sources for mediation.


Mobile Ads SDK Forum Advisor

unread,
Jan 27, 2025, 4:38:11 PMJan 27
to lbl...@gmail.com, google-adm...@googlegroups.com
Hi,

We are unable reproduce the issue with our sample projects. For us to further investigate kindly share steps to reproduce the issue or the sample project where the issue can be observed.

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:

1. Navigate to

https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=5004Q00002vGycvQAC&entry.80707362=00286013

2. Fill out all fields, and attach your file(s).

3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGycv:ref" (ADR-00286013)

Thanks,
 
Google Logo Mobile Ads SDK Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5



Liran Barsisa

unread,
Jan 27, 2025, 5:35:22 PMJan 27
to Google Mobile Ads SDK Developers
I didn't say it was in a sample project.
In fact, the sample projects are very outdated and don't use ad-sources for mediation, which I use, and don't use the GDPR/US regulations instructions that are needed for them either.
They don't even use kotlin gradle files (kts) as written on the docs (and the docs don't have the old format of gradle files), and don't add the current device as a test ad...
You should check the logs, and see that right on the first lines, it says "mediation.Adapter", giving you a clue that it's related to mediation.

You need to update the sample to use mediation with various ad-sources, add mappings and ad-units.
Anyway, I couldn't reproduce it now, not on my apps and not in the sample. 



However, another common error I see on the logs:

```
 java.lang.SecurityException: Unknown calling package name 'com.google.android.gms'.
                                                                       at android.os.Parcel.createExceptionOrNull(Parcel.java:3231)
                                                                       at android.os.Parcel.createException(Parcel.java:3215)
                                                                       at android.os.Parcel.readException(Parcel.java:3198)
                                                                       at android.os.Parcel.readException(Parcel.java:3140)
                                                                       at arri.a(:com.google.android.gms@250332035@25.03.32 (260400-716700083):36)
                                                                       at arpp.z(:com.google.android.gms@250332035@25.03.32 (260400-716700083):143)
                                                                       at aqxk.run(:com.google.android.gms@250332035@25.03.32 (260400-716700083):54)

                                                                       at android.os.Handler.handleCallback(Handler.java:991)
                                                                       at android.os.Handler.dispatchMessage(Handler.java:102)
                                                                       at byif.mw(:com.google.android.gms@250332035@25.03.32 (260400-716700083):1)
                                                                       at byif.dispatchMessage(:com.google.android.gms@250332035@25.03.32 (260400-716700083):5)

                                                                       at android.os.Looper.loopOnce(Looper.java:232)
                                                                       at android.os.Looper.loop(Looper.java:317)
                                                                       at android.os.HandlerThread.run(HandlerThread.java:85)
```

As for a sample for you, I've sent one, but without this issue above.
Instead I've succeeded to reproduce this issue I've reported of, that MobileAds.initialize() can take a very long time:
https://groups.google.com/g/google-admob-ads-sdk/c/As0gxGnVjoE

Please check it out, and also modify the sample I've sent you with the mappings of the various ad-sources.
Please use these ad-sources that I use:
AppLovin, InMobi (SDK), Liftoff Monetize, Mintegral, Equativ, Improve Digital, InMobi Exchange, Magnite DV+, Mobfox, OpenX, AdMob Network, Chartboost, ironSource Ads, Unity Ads.

Mobile Ads SDK Forum Advisor

unread,
Jan 29, 2025, 8:10:45 AMJan 29
to google-adm...@googlegroups.com, lbl...@gmail.com
Hi,

Thank you for sharing a sample project with us.
We tried replicating your issue in a given sample project, unfortunately we are also not able to reproduce it at our end. Since you have mentioned that you are also not able to reproduce it now, If it occurs again at your end feel free to reach us.

Liran Barsisa

unread,
Jan 29, 2025, 5:38:52 PMJan 29
to Google Mobile Ads SDK Developers
Can you please explain about the other logs I'm seeing? 

Mobile Ads SDK Forum Advisor

unread,
Jan 30, 2025, 12:05:52 AMJan 30
to lbl...@gmail.com, google-adm...@googlegroups.com

Hi,

I will check with our team regarding your query and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated. 

tomi.u...@gmail.com

unread,
Feb 10, 2025, 3:27:18 AMFeb 10
to Google Mobile Ads SDK Developers
It's happening to me as well. It appears to be a widespread issue pertaining to NativeAds when using an adapter such as Meta

Mobile Ads SDK Forum Advisor

unread,
Feb 10, 2025, 9:48:16 AMFeb 10
to tomi.u...@gmail.com, google-adm...@googlegroups.com
Hi, 

Regarding logs in console, can you please confirm if the issue is replicating in our Google NativeAdvancedExample? If yes, Kindly provide the sample project reproducing the issue. 

Tomi

unread,
Feb 11, 2025, 4:10:43 AMFeb 11
to mobile...@forumsupport.google, google-adm...@googlegroups.com

For this error to occur, a third-party mediation adapter, such as Meta, must be added. Since NativeAdvancedExample does not include such an adapter, the issue cannot be reproduced there.

Mobile Ads SDK Forum Advisor

unread,
Feb 11, 2025, 9:41:05 AMFeb 11
to tomi.u...@gmail.com, google-adm...@googlegroups.com

Hi,

Thanks for connecting back to us.

Currently this NativeAdvancedExample adUnit Id is not associated with the Meta mediation. I would suggest configuring meta mediation by using our own account For your own project and use those as test ads.

kindly follow Add your test device in the AdMob UI or programmatically guide for testing your Ads.
Reply all
Reply to author
Forward
0 new messages