RE: [google-admob-ads-sdk] admob 24.7.0 nosuchmethoderror: no virtual method setiscontentspatialized

124 views
Skip to first unread message

Mobile Ads SDK Forum Advisor

unread,
Dec 1, 2025, 4:32:29 AMDec 1
to xujia...@zhuilai.com.cn, google-adm...@googlegroups.com

Hi,

Thank you for contacting Mobile Ads SDK Support team.

This is a known issue. We already raised this issue with the wider team and the team took a look at the crash and they believe this is a weird corner case. As part of investigating your issue, we need some additional information.

  • How often does this occur (recent frequency and number of impacted users), and what is the device model distribution?
  • Based on your stack trace, we can see setIsContentSpatialized. Do you see the same crash occurring with setSpatializationBehavior, similar to setIsContentSpatialized?
  • Did you apply any special settings related to R8 desugaring?
  • Do you see the same crash in the Play Console?

Thanks,
 
Google Logo Mobile Ads SDK Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5
[2025-12-01 09:31:32Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vUa8K:ref" (ADR-00346262)



Lian Peng

unread,
Dec 11, 2025, 7:32:54 PM (11 days ago) Dec 11
to Google Mobile Ads SDK Developers

I've also encountered a similar issue. Here are the stack trace and affected environment
 Caused by java.lang.NoSuchMethodError: No virtual method setIsContentSpatialized(Z)Landroid/media/AudioAttributes$Builder; in class Landroid/media/AudioAttributes$Builder; or its super classes (declaration of 'android.media.AudioAttributes$Builder' appears in /system/framework/framework.jar!classes2.dex)
   at m84.gj.a(:com.google.android.gms.policy_ads_fdr_dynamite@253405702@253405700017.794833465.794833465:42)
   at m84.xc.Y(:com.google.android.gms.policy_ads_fdr_dynamite@253405702@253405700017.794833465.794833465:168)
   at m84.ys.W(:com.google.android.gms.policy_ads_fdr_dynamite@253405702@253405700017.794833465.794833465:3)
   at m84.qv.p(:com.google.android.gms.policy_ads_fdr_dynamite@253405702@253405700017.794833465.794833465:85)
   at m84.qv.q(:com.google.android.gms.policy_ads_fdr_dynamite@253405702@253405700017.794833465.794833465:12)
   at m84.qn.handleMessage(:com.google.android.gms.policy_ads_fdr_dynamite@253405702@253405700017.794833465.794833465:150)
   at android.os.Handler.dispatchMessage(Handler.java:102)
   at android.os.Looper.loop(Looper.java:223)
   at android.os.HandlerThread.run(HandlerThread.java:67)

Affected Environment:

SDK/Library Version: com.google.android.gms:play-services-ads (likely around version 21.5.0, inferred from dynamic module version 253405700017.794833465.794833465)
Android Versions: Primarily affects Android 13-15 (API 33-35)
Device Models: Samsung devices are predominantly affected
Trigger Scenario: During ad initialization or display (triggered internally by GMS HandlerThread)

Mobile Ads SDK Forum Advisor

unread,
Dec 12, 2025, 1:05:42 AM (11 days ago) Dec 12
to google-adm...@googlegroups.com

Hi, 

Thank you for contacting Mobile Ads SDK Support team.

This is a known issue and our team is actively working on a resolution. Once we receive any updates, we will intimate you. Meanwhile, your patience is important.


Thanks,
 
Google Logo Mobile Ads SDK Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5

[2025-12-12 06:04:29Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vUa8K:ref" (ADR-00346262)



Reply all
Reply to author
Forward
0 new messages