Re: [google-admob-ads-sdk] Digest for google-admob-ads-sdk@googlegroups.com - 11 updates in 5 topics

20 views
Skip to first unread message

Nguyen Hong phong

unread,
Jun 10, 2025, 6:28:33 AM (6 days ago) Jun 10
to google-adm...@googlegroups.com
Xin chào 

From: google-adm...@googlegroups.com <google-adm...@googlegroups.com>
Sent: Tuesday, June 10, 2025 6:52:16 AM
To: Digest recipients <google-adm...@googlegroups.com>
Subject: [google-admob-ads-sdk] Digest for google-adm...@googlegroups.com - 11 updates in 5 topics
 
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Jun 09 06:07AM

Hi Shota,
 
Thank you for providing the requested information.
 
Please note that the 'loadAd()' is deprecated. This method will be removed in future version. Testing of the provided sample project using 'loadAdWithBidPayload' has confirmed the successful loading of Ads.
 
It is requested that you utilize 'adView.loadAd(withBidPayload: "PLACEMENTID")' in place of 'adView.loadAd()'.
 
Kindly report the outcomes subsequent to implementing these modifications.
 
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-06-09 06:07:36Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01qYNQW:ref" (ADR-00308673)
K Shota <kin...@quadsystem.co.jp>: Jun 09 12:01AM -0700

Dear Team,
 
Thank you for your continued support.
 
We understand that loadAd() is deprecated and scheduled to be removed in a
future release.
However, *the current Meta Audience Network iOS mediation adapter (version
6.17.1.0) still uses loadAd() internally*, which is the root cause of the
crash we are experiencing.
 
Our app is built to support multi-window environments and does not define a
window property on the AppDelegate. As a result, when the adapter
internally calls loadAd(), it triggers a crash due to an unrecognized
selector when trying to access AppDelegate.window.
 
While using loadAd(withBidPayload:) directly in the app works correctly, *this
crash cannot be avoided when using AdMob mediation, since the adapter
enforces the use of the deprecated loadAd() method internally*.
 
Therefore, *we strongly request that the mediation adapter itself be
updated to stop using the deprecated loadAd() method and instead use
loadAd(withBidPayload:)*.
 
We would greatly appreciate your consideration of this change.
 
Best regards,
K Shota
2025年6月9日月曜日 15:08:43 UTC+9 Mobile Ads SDK Forum Advisor:
 
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Jun 09 01:49PM

Hi,
 
The loadAd method still works for single-window apps without causing a crash. However, the SDK cannot determine in advance whether your app uses multiple windows or a single window.
 
But Yes, that’s a good suggestion to remove this method permanently if it’s deprecated.
 
For your use case, please use adView.loadAd. If you encounter any further issues related to the Mobile Ads SDK, feel free to reach out to us again.
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-06-09 13:49:40Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01qYNQW:ref" (ADR-00308673)
Natalia Surkova <natalia...@ab-games.com>: Jun 06 10:56AM -0700

We are using AppLovin MAX as our mediation platform and have successfully
connected our AdMob account via OAuth (Authorize with Google). The
connection is initially successful, but within a few hours the connection
breaks with the following error on AppLovin dashboard:
 
"Failed to connect due to invalid permissions. Please check the user or
token has appropriate permissions to access this data."
 
Can you please help us understand why the OAuth token is being revoked
automatically?
We would like to know if there are any permission scopes or security
settings on our AdMob account that could be causing this issue.
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Jun 09 01:04PM

Hi,
 
Thank you for contacting the Mobile Ads SDK Support team.
 
Could you provide the App ID, Ad Unit ID, and the platform you’re using so we can proceed with further investigation.
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-06-09 13:04:27Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01ree4a:ref" (ADR-00312473)
Faelight Developer <d...@faelightgames.com>: Jun 06 07:13AM -0700

Hi,
 
I’m calling ConsentForm.LoadAndShowConsentFormIfRequired() with TFUA set to
true for child users. I understand that in this case it will not show the
consent form but it should still initialise the required flags for consent
status and ads.
 
I’m using Unity 6000.0.48, and Google Mobile Ads v10.1.0. And this error
only occurs if I publish IDFA explainer from AdMob Privacy and Messaging
section.
 
If I show the ATT prompt using other methods, then
LoadAndShowConsentFormIfRequired() with TFUA set to true doesn’t show the
consent screen, initialises whatever is needed and the app proceeds
normally without error.
 
On Wednesday, June 4, 2025 at 4:53:17 AM UTC+5:30 Mobile Ads SDK Forum
Advisor wrote:
 
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Jun 09 12:32PM

Hi,
 
Thanks for providing the details. I will get back to you once I receive an update on this.
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-06-09 12:32:28Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01qVxh7:ref" (ADR-00303983)
Wing <win...@gmail.com>: Jun 08 06:35PM -0700

Files have been submitted, please help to investigate, thanks.
 
On Wednesday, 4 June 2025 at 07:31:38 UTC+8 Mobile Ads SDK Forum Advisor
wrote:
 
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Jun 09 09:24AM

Hi,
 
Thank you for getting back to us.
 
I will check with the wider team and get back to you. Meanwhile your patience is important.
 
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-06-09 09:24:06Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01qXDrl:ref" (ADR-00306162)
Flex Yan <yan...@gmail.com>: Jun 08 07:11AM -0700

Hi,
 
Is customer search ads no longer supported? Our request to
www.adsensecustomsearchads.com has no response. We are using
GADDynamicHeightSearchRequest() to send the request.
 
Here is our app information:
 
iOS:
app id: ca-app-pub-3211416997935949~9483363513
ad unit id: ca-app-pub-3211416997935949/9920172261
sdk version: Google-Mobile-Ads-SDK (7.69.0)
 
Thanks,
Flex
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Jun 09 07:30AM

Hi Flex,
 
Thank you for contacting the Mobile Ads SDK Support team.
 
Please be advised that Mobile Ads SDK version 7.69.0 has been deprecated
 
The GMA SDK currently supports only versions v12.x.x and v11.x.x.
 
It is always recommended to use the latest versions of the SDK to avoid any issues. As of today the latest version of iOS is 12.5.0.
 
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-06-09 07:30:05Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01ree4f:ref" (ADR-00312474)
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to google-admob-ads...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages