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

8 views
Skip to first unread message

Ez'raa Dechwong

unread,
Sep 8, 2025, 9:11:21 PM (9 hours ago) Sep 8
to google-adm...@googlegroups.com, True Move H SIM 1


ในวันที่ อ. 9 ก.ย. 2025 06:52 น. <google-adm...@googlegroups.com> เขียนว่า:
Google Mobile Ads SDK Developers <google-adm...@googlegroups.com>: Sep 08 12:24PM -0700

Version 12.11.0 was released on 09/08/25.
 
Notes:
 
 
- Bug fixes and performance improvements.
 
 
On Friday, September 5, 2025 at 9:59:57 AM UTC-7 Google Mobile Ads SDK
Developers wrote:
 
Game Games <forumi...@gmail.com>: Sep 08 02:57AM -0700

Admob sdk support please answer my questions:
 
1) I use the GDPR consent window from Admob ump sdk, and when I click the
consent button or when I click accept all, in the logs I have this status
after that = (status=3 canRequestAds=true) from these logs
Log.d("UMP", "status=" + consentInformation.getConsentStatus()
+ " canRequestAds=" + consentInformation.canRequestAds());
But I also have other logs that display IABTCF_CmpSdkID":300,
UMP_consentModeValues":"4444". Is it supposed to display 4444? Does this
mean that consent was not received, although I clicked the consent button?
If after clicking the consent button I immediately restart the application,
I will still see the code 4444.
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Sep 08 06:18PM

Hi,
 
Thank you for contacting the Mobile Ads SDK support team.
 
Please note that status=3 corresponds to ConsentStatus.OBTAINED (meaning user consent is obtained) and canRequestAds=true means you can request personalized ads based on that consent. This is exactly what you expect after the user clicks the consent button or accepts all.
 
Could you confirm whether you're experiencing any ad serving issues when receiving the '4444' value? And it does not mean that consent is not received.
 
Because consent values are stored in SharedPreferences. If the consent status doesn't change , it won't be updated again. So seeing ‘4444’ again after restart is expected.
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-09-08 18:18:58Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u63EX:ref" (ADR-00332145)
MrLivsi <drli...@gmail.com>: Sep 05 05:04AM -0700

Hello,
I’m developing a mobile app related to cryptocurrencies. The app is for *educational
and analytical purposes only* — it allows users to backtest trading
strategies with historical data (no wallets, mining and rewards).
 
Is such an app eligible for AdMob monetization?
 
Thank you!
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Sep 08 01:59PM

Hi,
 
Thank you for contacting the Mobile Ads SDK support team.
 
Yes, It is eligible for AdMob Monetization. I would recommend you to check the following Google AdMob help center article for more information.
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-09-08 13:59:54Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u63DF:ref" (ADR-00332136)
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Sep 08 01:01PM

Hi,
 
Here are the clarifications regarding SDK initialization and consent management:
 
1. Are both sequences (initializing Mobile Ads before vs. after UMP consent) correct and policy-compliant? Which is recommended?
Both approaches are valid and compliant. However, it is recommended to initialize the Mobile Ads SDK after you have obtained user consent or confirmed that consent was previously given. This helps ensure compliance and avoids unnecessary SDK initialization.
 
2. Why do the official examples seem to differ from the guidance I received? Should I follow the examples exactly?
The official examples cover different consent scenarios, including handling users who already gave consent. They include extra checks to cover all cases. You don’t have to follow them exactly, but following their general pattern helps ensure compliance and good performance.
 
3. Why is MobileAds.initialize() called twice in the first example? Does this affect performance?
It is intentional to call MobileAds.initialize() both in onCreate() and after consent is gathered. This ensures the SDK is initialized whether consent is newly obtained or was granted in a previous session. It does not cause performance issues because the initialization is safe to call multiple times.
 
4. Should MobileAds.initialize() be called in MainActivity or MyApplication?
Calling MobileAds.initialize() in the MyApplication class is recommended because it initializes the SDK once per app lifecycle and works well for app-wide features like App Open Ads. Initializing in MainActivity can work but may be less efficient.
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-09-08 13:01:45Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01sxDN0:ref" (ADR-00321136)
Timothy Hutton <serv...@optimalnurturing.com>: Sep 07 07:34AM -0700

Hello, I am curious about the timeline for linking my Apple App Store
listing to my matching AdMob iOS app entry. I have completed review of my
app with Apple and I am ready to release it. 4 days have passed since the
successful review, but I still cannot get the linkage to work within AdMob
despite trying with my developer name, app name, and app ID.
 
Is it possible to link the app before it's released so that ads will
display? I don't want to release it without making sure that monetization
is functioning correctly. Test ads display correctly, but I am yet to see
production ads populating within the app.
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Sep 08 09:03AM

Hi,
 
Thank you for contacting the Mobile Ads SDK Support team.
 
If you have recently listed your app on a store, it may take 24 to 48 hours before you can link to it. In some cases, it may take up to one week. For more information, kindly refer to Link your app to an app store.
 
No, you cannot get production ads in an app before it's officially released and linked to an app store. If your application is in the closed testing phase or in the open testing phase, you will only receive test ads until the application is fully launched. If you want to test ads before going into production, kindly refer to Enable test ads.
 
I hope this helps! Let me know if you have any other questions.
 
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-09-08 09:03:17Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u62yZ:ref" (ADR-00332107)
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Sep 08 07:36AM

Hi,
 
The team is actively working on a resolution. Once we receive any updates, we will intimate you. Meanwhile, your patience is important.
 
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-09-08 07:36:07Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rhF6i:ref" (ADR-00317274)
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Sep 08 07:38AM

Hi,
 
Thank you for contacting the 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,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-09-08 07:38:25Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u5vhR:ref" (ADR-00331966)
master word <master...@gmail.com>: Sep 08 01:01AM -0700

We are losing many users because of this issue! users can't close the
interstitial ads to continue the features of the app, the first thing they
do after this bug is removing the app ! We are doing Ads by google, paying
35% on ads, using AdMob which is again gets 35% of the income and now we
are losing 35% of our users because of this dummy bug which is promising to
fix for few month! is anybody alive in Google company or you are just
playing around and get the money of our hard work on applicaitons ?
 
On Monday, 8 September 2025 at 11:39:24 UTC+4 Mobile Ads SDK Forum Advisor
wrote:
 
Takashi Katsumoto <sirom...@gmail.com>: Sep 05 01:40AM -0700

Hello. My app published on Google Play cannot be found by AdMob, so I
cannot complete the setup. Could you please check?
https://play.google.com/store/apps/details?id=net.dirsense.shoalert
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Sep 08 08:07AM

Hi,
 
Thank you for contacting the Mobile Ads SDK Support team.
 
If you have recently listed your app on a store, it may take 24 to 48 hours before you can link to it. In some cases, it may take up to one week. For more information, kindly visit to Set up an app in AdMob.
 
The id “net.dirsense.shoalert” provided in the play store URL seems to be incorrect. On clicking the provided play store link I am getting the error “We're sorry, the requested URL was not found on this server". Kindly share the correct link for further investigation.
 
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-09-08 08:07:15Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u62yF:ref" (ADR-00332104)
Hightlight digital music company <singerdeep...@gmail.com>: Sep 06 09:47AM +0545

य क्या हे साप
 
Hightlight digital music company <singerdeep...@gmail.com>: Sep 06 06:04AM +0545

ये क्या हे
 
User345738945 <gork...@gmail.com>: Sep 04 05:46AM -0700

thank you, sizeClass environment variable (e.g., @Environment(\.horizontalSizeClass)
var horizontalSizeClass) has helped
 
On Wednesday, September 3, 2025 at 10:00:44 PM UTC+3 Mobile Ads SDK Forum
Advisor wrote:
 
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