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

52 views
Skip to first unread message

福亮 朱

unread,
Aug 15, 2025, 11:37:51 PM8/15/25
to google-adm...@googlegroups.com
TEAC 

寄件者: google-adm...@googlegroups.com <google-adm...@googlegroups.com>
寄件日期: Friday, August 15, 2025 7:52:16 AM
收件者: Digest recipients <google-adm...@googlegroups.com>
主旨: [google-admob-ads-sdk] Digest for google-adm...@googlegroups.com - 11 updates in 6 topics
 
Myoungkyu Shin <ikaru...@gmail.com>: Aug 14 03:11PM -0700

Hello, team,
 
We are currently reviewing whether it is possible to use multiple
GADApplicationIdentifiers in a single app.
 
By default, the GADApplicationIdentifier is set in the info.plist file.
I am wondering if it is possible to change this value at runtime, as shown
in the example below.
 
[Example]
App IDs
 
- App ID: TestA
- App ID: TestB
- App ID: TestC
 
Scenario
 
- info.plist > GADApplicationIdentifier is set to TestA
- Is it possible to change GADApplicationIdentifier to TestB or TestC at
runtime (while the app is running)?
 
Thank you.
Game Games <forumi...@gmail.com>: Aug 14 02:54AM -0700

Thank you for your reply, Admob SDK support please answer my new questions.
I want to add a clarification to the previous questions.
My application is installed in Google Play from 18 years old with the note
do not show for users under 18 years old, but just in case I want to be on
the safe side so that Admob does not collect data from users under 18 years
old if they still download the application.
 
And here are my questions related to European users:
1) What do I need to install so that Admob does not collect user data from
Europe under 18 years old and does not show the consent window,
.setTagForUnderAgeOfConsent(true) or
.setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE)
?
 
2) What is the difference between .setTagForUnderAgeOfConsent(true) and
.setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE)
?
 
3) If my application is installed from the age of 18 and I install
setTagForUnderAgeOfConsent(true) or
.setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE)
for safety, then this will not violate the rules of Google Play and my
account or application will not be deleted?
 
вторник, 12 августа 2025 г. в 07:06:55 UTC+3, Mobile Ads SDK Forum Advisor:
 
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Aug 14 06:36PM

Hi,
 
Thank you for getting back to us.
 
1) What do I need to install so that Admob does not collect user data from Europe under 18 years old and does not show the consent window, .setTagForUnderAgeOfConsent(true) or .setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE?
 
Ans: To ensure AdMob does not collect user data from users under the age of consent (typically 18 in Europe) and to prevent the consent message from showing, you need to use the setTagForUnderAgeOfConsent() method with TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE. This also prevents the transmission of the Android advertising identifier (AAID).
 
2) What is the difference between .setTagForUnderAgeOfConsent(true) and .setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE?
 
Ans: setTagForUnderAgeOfConsent(true) is for the UMP SDK. When you set TFUA to true, the UMP SDK doesn't request consent from the user. If your app has a mixed audience, set this parameter for child users to ensure consent is not requested.
 
setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE) indicate that you want the ad request to receive treatment for users in the European Economic Area (EEA) under the age of consent. This also prevents the transmission of the Android advertising identifier (AAID). You use this to tell AdMob and its ad partners to treat the user as a minor and serve restricted, non-personalized ads.
 
3) If my application is installed from the age of 18 and I install setTagForUnderAgeOfConsent(true) or .setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE) for safety, then this will not violate the rules of Google Play and my account or application will not be deleted?
 
Ans: No, this will not violate Google Play or AdMob policies. As your app is rated 18+ on Google Play, the expectation is that your audience is adults. However, because a user can technically download and use an 18+ app even if they are younger, your extra safety measure is a responsible way to handle potential edge cases.
 
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-08-14 18:36:53Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01sye5l:ref" (ADR-00329339)
SF <slavo....@gmail.com>: Aug 13 08:55AM -0700

Hello,
 
First of all, thank you for maintaining and updating the *AppOpenExample*
sample – it’s a very helpful reference for many developers.
 
While testing the latest version (updated about two weeks ago), I noticed
that the App Open Ad in the sample is displayed after a splash/loading
screen. Based on my reading of the official guidelines, App Open Ads should
ideally appear immediately when the app is opened (cold start) or when
returning from the background, and always before the user interacts with
any app content. Showing the ad after a splash screen might potentially be
interpreted as an interstitial during app use.
 
I also observed that the current sample appears to trigger App Open Ads for
both cold start and return-to-app scenarios. Could you kindly clarify if it
is considered policy-compliant to use both triggers in the same app
session, or if best practice is to choose one scenario?
 
If this behavior is intentional, it would be great to add a short note in
the README explaining how it aligns with policy and recommended usage.
Since this sample is widely used as a reference, having this clarification
would help developers ensure compliance in their own apps.
 
Thank you for your time and for providing this valuable resource.
Fabian
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Aug 14 06:27PM

Hi,
 
Thank you for contacting the Mobile Ads SDK Support team.
 
The preferred way to use app open ads on cold starts is to use a loading screen to load your game or app assets, and to only show the ad from the loading screen. If your app has completed loading and has sent the user to the main content of your app, do not show the ad. For more information, kindly refer to Cold starts and loading screens.
 
App open ads help you monetize your app's loading screen, when the app first launches and during app switches, but it's important to keep best practices in mind so that your users enjoy using your app. Kindly refer to Best practices and cold start.
 
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-08-14 18:27:34Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01sz6DQ:ref" (ADR-00329958)
Ken <k...@candlelight.games>: Aug 13 07:19AM -0700

I'm trying to integrate Google Mobile Ads in Unreal Engine targeting iOS
and getting a crash on launch before any of my code is executed (Android
runs and invokes ads just fine). Here is the relevant version info:
 
- Google Mobile Ads SDK - 12.9.0
- XCode - 16.4
- OSX 15.5
- iOS SDK - 18.6
- Unreal Engine - 5.6
- Device - iPhone 13 mini
- Device OS - 18.6
 
My Info.plist definitely has the correct app ID in GADApplicationIdentifier
and the array of SKAdNetworkItems entries from your setup.
 
The crash appears to involve sqlite trying to open a database and perhaps
involves the initialization of an object called GADSettings.
 
#0 0x0000000000000000 in 0x00000000 ()
#1 0x000000010cfea6ec in sqlite3Malloc ()
#2 0x000000010cffe740 in openDatabase ()
#3 0x00000001041e474c in ___lldb_unnamed_symbol1466021 () <--- This is
where the below assembly is coming from, which appears to be your SDK code
#4 0x00000001041e449c in ___lldb_unnamed_symbol1466017 ()
#5 0x00000001041e4378 in ___lldb_unnamed_symbol1466016 ()
#6 0x000000011c402064 in _dispatch_client_callout ()
#7 0x000000011c3eb6d0 in _dispatch_once_callout ()
#8 0x00000001041e4358 in ___lldb_unnamed_symbol1466015 ()
#9 0x00000001041caebc in ___lldb_unnamed_symbol1465463 ()
#10 0x000000011c3e8584 in _dispatch_call_block_and_release ()
#11 0x000000011c402064 in _dispatch_client_callout ()
#12 0x000000011c420e58 in _dispatch_queue_override_invoke ()
#13 0x000000011c3fbf30 in _dispatch_root_queue_drain ()
#14 0x000000011c3fc8c8 in _dispatch_worker_thread2 ()
#15 0x000000021dbec9d0 in _pthread_wqthread ()
 
0x1041e46e0 <+28>: bl 0x1041e3fd4 ;
GADGoogleMobileAdsSupportDirectoryURL
0x1041e46e4 <+32>: mov x29, x29
0x1041e46e8 <+36>: bl 0x10bcd6820 ;
objc_retainAutoreleasedReturnValue.island
0x1041e46ec <+40>: mov x20, x0
0x1041e46f0 <+44>: adrp x2, 54130
0x1041e46f4 <+48>: add x2, x2, #0x758 ; @"Settings"
0x1041e46f8 <+52>: bl 0x10bcd35cc ;
objc_msgSend$URLByAppendingPathComponent:.island
0x1041e46fc <+56>: mov x29, x29
0x1041e4700 <+60>: bl 0x10bcd6820 ;
objc_retainAutoreleasedReturnValue.island
0x1041e4704 <+64>: mov x19, x0
0x1041e4708 <+68>: mov x0, x20
0x1041e470c <+72>: bl 0x10bcd682c ;
objc_release.island
0x1041e4710 <+76>: cbz x19, 0x1041e4768 ; <+164>
0x1041e4714 <+80>: mov x0, x19
0x1041e4718 <+84>: bl 0x10bcd5238 ;
objc_msgSend$path.island
0x1041e471c <+88>: mov x29, x29
0x1041e4720 <+92>: bl 0x10bcd6820 ;
objc_retainAutoreleasedReturnValue.island
0x1041e4724 <+96>: mov x22, x0
0x1041e4728 <+100>: bl 0x10bcd3e78 ;
objc_msgSend$copy.island
0x1041e472c <+104>: mov x20, x0
0x1041e4730 <+108>: mov x0, x22
0x1041e4734 <+112>: bl 0x10bcd682c ;
objc_release.island
0x1041e4738 <+116>: mov x0, x20
0x1041e473c <+120>: bl 0x10bcd35f4 ;
objc_msgSend$UTF8String.island
0x1041e4740 <+124>: str xzr, [sp, #0x28]
0x1041e4744 <+128>: add x1, sp, #0x28
0x1041e4748 <+132>: bl 0x10bcd336c ;
sqlite3_open.island <--- This is where it crashes
-> 0x1041e474c <+136>: cbz w0, 0x1041e4770 ; <+172>
0x1041e4750 <+140>: adrp x1, 54128
0x1041e4754 <+144>: add x1, x1, #0x298 ; @"Couldn't open
database."
0x1041e4758 <+148>: mov x0, #0x0 ; =0
0x1041e475c <+152>: bl 0x10412b560 ; GADPostErrorEvent
 
For what it's worth, this would be far easier to debug if you published the
source code to the SDK. If it's somewhere I'm not aware of, please let me
know. In either case, please let me know how I can resolve this issue.
 
Best,
Ken
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Aug 14 06:18PM

Hi,
 
Thank you for contacting the Mobile Ads SDK Support Team.
 
According to the Google Mobile Ads SDK documentation, we support the following platforms: Android, iOS, Unity and Flutter. Currently, the Google Mobile Ads (GMA) SDK does not have an official support for Unreal Engine.
 
Could you confirm whether the mentioned issue is reproduced in our Google sample application? If yes please share the following details privately with us for further investigation:
 
Steps to reproduce the issue in Google sample project
If no, please share your sample application and full crash logs where the issue is reproducible
 
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 via reply to author option or 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=500Ht00001sz6DBIAY&entry.80707362=00329956
 
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.
 
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-08-14 18:18:05Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01sz6DB:ref" (ADR-00329956)
Alban Delanchy <delanc...@gmail.com>: Aug 13 07:59AM -0700

*Hi,*
AdMob continues to show that *app-ads.txt is not found* for my iOS app,
even though the file is correctly hosted and publicly accessible. I’d
appreciate help spotting what I’m missing.
Environment

-

*Game engine:* Flutter 3.32.8
-

*Ads plugin:* google_mobile_ads 6.0.0
-

*iOS Mobile Ads SDK (CocoaPods):* Google-Mobile-Ads-SDK (12.2.0)
-

*Devices / OS versions showing the issue:* iOS

App & domain

-

*iOS App Store listing:* https://apps.apple.com/fr/app/zyloc/id6749594346
(App availability: *France only*.)
-

*Domain where app-ads.txt is hosted:* zyloc.fr
*File URL:* https://zyloc.fr/app-ads.txt

What I see

-

In *AdMob → Apps → [my iOS app] → app-ads.txt*, the status remains *“not
found / needs attention”*.
-

Clicking *Check status* doesn’t change it.

What I’ve already verified

-

https://zyloc.fr/app-ads.txt returns *HTTP 200* and plain text (no HTML
wrapper).
-

No redirects to another host (no www. vs apex mismatch); both HTTP→HTTPS
and direct HTTPS serve the same file.
-

*robots.txt* doesn’t block /app-ads.txt.
-

The file has no BOM, uses LF line endings, and is under 1MB.
-

Lines follow the standard format and include my AdMob publisher ID used
by the iOS app.

Questions
1.

Is there any *iOS-specific linkage* AdMob requires (e.g., Store
listing metadata, app → domain association) that could delay recognition
even when the file is reachable?
2.

Could *regional availability (France-only)* or a *recent App Store
release* delay the crawler?
3.

Are there any additional *domain verification* steps for iOS I should
do in AdMob beyond entering the domain in the app-ads.txt section?

Extra details you might need
-

*AdMob Publisher ID:* pub-3336994833677310
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Aug 14 06:15PM

Hi,
 
Thank you for contacting the Mobile Ads SDK Support team.
 
Upon reviewing your AdMob account with the provided information, I observed that your app status is in "Requires review" state. This indicates that your app has not yet been subject to the review process. To have it reviewed, it is necessary to establish a link between your app and the supported app store. You can link a supported store to your app within the All Apps or App settings pages and subsequently submit it for review. For more information, you can visit Requires review.
 
The app-ads.txt file has not been configured yet. It can take up to 24 hours for AdMob to crawl and verify your app-ads.txt files. You need to wait at least 24 hours for the app-ads.txt status to update.
 
If you've recently added your developer website or updated your app listing in Google Play, allow up to 24 hours for AdMob to detect these changes.
 
Please use the following help center article to Set up an app-ads.txt file for your app, Resolve issues with app-ads.txt and Ensure your app-ads.txt files can be crawled.
 
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-08-14 18:15:39Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01sz6DG:ref" (ADR-00329957)
Serhat Savaş <serhat...@gmail.com>: Aug 14 02:15AM -0700

So i am trying to open an AdMob account but I keep getting the mail from
AdMob that says My AdMob account is not approved because I do have an
another account. but I've closed that account completely, I've deleted that
google account completely so I don't have an access to it but the AdMob
still says me that I have an another account and the first 4 letter of that
account is the one that I've deleted so I am sure that I don't have another
account. I've tried to sign in to account but I'm getting google account
not found error because I've completely deleted it but AdMob still says
that I have a second AdMob account. I'm so frustrated right now... Need
help asap.
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Aug 14 06:14PM

Hi,
 
Thank you for contacting the Mobile Ads SDK Support team.
 
It is important to follow AdMob policies and restrictions to avoid any issues.
 
Kindly refer to the help center articles for Resolve common onboarding issues and Account issues FAQ.
 
Kindly note that our support channel can only best assist you with regards to Google Mobile Ads SDK implementation and technical issues.
 
The best way to get more information about your issue is the AdMob Help Center. You can also utilize the AdMob Communities for additional support.
 
 
Thanks,
 
Mobile Ads SDK Team
 
 
Feedback
How was our support today?
 
 
[2025-08-14 18:14:13Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01sz6Da:ref" (ADR-00329959)
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.

Mobile Ads SDK Forum Advisor

unread,
Aug 18, 2025, 11:55:48 AM8/18/25
to forumi...@gmail.com, google-adm...@googlegroups.com

Hi,

Thank you for getting back to us.

Question 1: As I understood from your previous reply, I need to add these two methods, setTagForUnderAgeOfConsent(true) to not show the GDPR consent window from Admob ump sdk for users under 18 from Europe and setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE) to not collect data and not show personalized ads for users under 18 from Europe. Did I understand everything correctly?

Answer : Yes, your understanding is correct.

Question 2 : I installed setTagForUnderAgeOfConsent(true) and now I have stopped showing the GDPR consent window from Admob ump sdk at all, although I am logged into a Google account on my phone, in which the date of birth is set to 1991.

Here is how I set up the code:

ConsentRequestParameters params;

params = new ConsentRequestParameters.Builder().setTagForUnderAgeOfConsent(true) .build();

Why is the consent window no longer showing for me?

Answer : If you call setTagForUnderAgeOfConsent(true) without applying any age-based logic, it will always signal to the SDK that the user is under the age of consent. As a result, the UMP SDK will not request consent from the user, even if the user is an adult.

 To display consent for adults(18+), you must call setTagForUnderAgeOfConsent(false). Ensure that you implement the appropriate conditions in your code based on the user’s age.

Question 3: And I set RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE before initialization as you can see below, is that correct?

private void setupAds() {

RequestConfiguration requestConfiguration = new RequestConfiguration.Builder()

.setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE)

.build();

MobileAds.setRequestConfiguration(requestConfiguration);

MobileAds.initialize(this, new OnInitializationCompleteListener() {}

Answer : Based on our sample project, the RequestConfiguration must be set before initializing the SDK.


Thanks,
 
Google Logo Mobile Ads SDK Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5
[2025-08-18 15:55:02Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01sye5l:ref" (ADR-00329339)



Reply all
Reply to author
Forward
0 new messages