Game Games <forumi...@gmail.com>: Sep 09 03:49AM -0700
Thank you for your answer, please answer my new questions. 1) You asked - 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. My answer Advertisements are shown if the user clicks the consent button, or accept all. 2) If I see the code 4444, does this mean that AdMob does not collect user data and does not use cookies and advertising ID? Or if I also see status=3 canRequestAds=true, then AdMob collects user data and uses cookies and advertising ID? 3)You wrote (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.) My question So if I give consent in the GDPR window and then restart the game, then 4444 will be there because I don't change the consent? I thought that if I give consent, it should be 1111. понедельник, 8 сентября 2025 г. в 21:20:00 UTC+3, Mobile Ads SDK Forum Advisor: |
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Sep 09 04:30PM
Hi, Please note that thE code 4444 is generated by the User Messaging Platform's initial API (fundingchoicesmessages.google.com) and is not influenced by the user's consent status. Whether the user gives consent or not, the code remains unrelated to that decision. I hope this helps, please reach out to us, if you need any further assistance related to Google Mobile Ads SDK Thanks, Mobile Ads SDK Team Feedback How was our support today? [2025-09-09 16:30:43Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u63EX:ref" (ADR-00332145) |
Rocket Llama Games <rocketll...@gmail.com>: Sep 06 08:38AM -0700
Hi, The build still got rejected, is there any other solution to this as we are using Admob as part for the Level Play SDK mediation otherwise we will have to disable ads from Admob which we do not wan't to do. Please let me know. Thanks. On Friday, September 5, 2025 at 12:35:39 AM UTC+5:30 Mobile Ads SDK Forum Advisor wrote: |
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Sep 09 07:19AM
Hi, Thank you for getting back to us. Please note that the Google Mobile Ads SDK does not support Level play SDK. We support the Google Mobile Ads for Unity plugin. Thanks, Mobile Ads SDK Team Feedback How was our support today? [2025-09-09 07:19:54Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u5op4:ref" (ADR-00331825) |
Rocket Llama Games <rocketll...@gmail.com>: Sep 09 01:44AM -0700
AdMob supports mediation with networks like LevelPlay, but we’re facing an issue with *rewarded ad close buttons*. In the attached screen record, the close option appears as *“Ad 1 of 2”* in the top-left instead of a clear *“X”* on the top-right. This causes confusion and rejection during Play Console review. |
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Sep 09 02:50PM
Hi, Please ignore our previous response. Could you please confirm whether you're using the Google Mobile Ads SDK? If so, share the SDK version, and also provide a Charles proxy log along with the Ad Unit ID at the time the issue occurs via reply to author option. 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=500Ht00001u5op4IAA&entry.80707362=00331825 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-09-09 14:50:25Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u5op4:ref" (ADR-00331825) |
Rok Arnuš <rok....@gmail.com>: Sep 07 11:01AM -0700
We have the same problem with just 1 of our apps not getting TEST AD. Its always no fill error. It's an Android app that has been live for months and is receiving real ads. All our other apps are getting test ads. To exclude any bugs in the implementation we used the admob banner sample app: https://github.com/googleads/googleads-mobile-android-examples/tree/main/java/admob/BannerExample We changed the manifest to our actual app: <meta-data android:name="com.google.android.gms.ads.APPLICATION_ID" android:value="ca-app-pub-XXXX"/> The build.gradle to our actual app: applicationId "xxx.xxx.xxx" And the ad unit ID to the test admob ID: private static final String AD_UNIT_ID = "ca-app-pub-3940256099942544/6300978111"; from here https://developers.google.com/admob/android/test-ads *And we always get no fill, although test ads should always have a fill.* If we change the manifest meta-data and applicationId to one of our other apps, test ads works. All of our apps are showing "app-ads.txt file found and verified", "App verification Verified", "Approval status Ready" on the admob console. I don't know if it's OK to share production admob app and ad unit ids on this forum, so the XXX values. Will gladly send these to admob support for testing On Wednesday, September 3, 2025 at 7:57:15 AM UTC+2 2MinLab wrote: |
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Sep 09 02:14PM
Hi, Thank you for contacting the Mobile Ads SDK Support team. We understand you’re experiencing a no fill error for test ads on one of your Android apps, while other apps are receiving test ads correctly. To help us investigate further, could you please provide your app’s package name? This will allow us to review the specific setup and provide more targeted assistance. Thanks, Mobile Ads SDK Team Feedback How was our support today? [2025-09-09 14:14:10Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u6AGa:ref" (ADR-00332239) |
karishma kevdiya <karishma...@gmail.com>: Sep 08 11:08PM -0700
Dear AdMob Team, I hope this message finds you well. I am writing to respectfully submit an appeal regarding the recent rejection of my app with the reason: "App doesn’t adhere to program policies." *Publisher ID: pub-5631073920607842* My app currently has over *40,000 daily active users*, with an* average user session time of 35 minutes and 57 seconds*, which reflects strong user engagement and value. After receiving the rejection notice, I carefully reviewed the *AdMob Policy Center* and thoroughly examined my app. I could not identify any specific policy violations mentioned in the rejection, which led me to believe that the decision may have been based on concerns about the app’s overall quality or user experience. To address this and ensure my app fully meets program expectations, I have taken the following steps: 1. *Introduced a new "Story Creation" feature* with unique, modern templates that enhance user creativity and engagement. 2. *Completely overhauled the user interface (UI)* to deliver a more polished, professional, and user-friendly experience. I genuinely value AdMob’s policies and standards, and I am committed to maintaining full compliance. I kindly request a re-evaluation of my app based on the recent improvements and enhancements. I believe these changes significantly improve both the app’s quality and user value. Thank you for your time, consideration, and support. I look forward to your positive response. Sincerely, Karishma Kevadiya |
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Sep 09 02:05PM
Hi, Thank you for contacting the Mobile Ads SDK Support team. I have checked your account and noticed that ad serving is disabled due to a policy issue. Based on the AdMob app ID, 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. If you have any questions about usage of the Google Mobile Ads SDK, please feel free to reach out. Thanks, Mobile Ads SDK Team Feedback How was our support today? [2025-09-09 14:05:37Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u6AGf:ref" (ADR-00332240) |
Szymon Gajdzica Labmatic <sz.ga...@labmatic.com>: Sep 09 12:03AM -0700
Is it fixed in version 12.11.0? On Thursday, September 4, 2025 at 9:09:03 PM UTC+2 Mobile Ads SDK Forum Advisor wrote: |
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Sep 09 11:58AM
Hi, Currently we have no updates at this moment. Please note that our team is actively working on the issue and will let you know as soon as an update is ready. Meanwhile, your patience is highly appreciated. Thanks, Mobile Ads SDK Team Feedback How was our support today? [2025-09-09 11:58:25Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u53mu:ref" (ADR-00330890) |
Jake <jaker...@gmail.com>: Sep 09 02:49AM -0700
I can see that SDK 24.6.0 has just been released. Is the Android 15 issue fixed in this update? On Monday, 8 September 2025 at 11:00:52 UTC+2 master word wrote: |
Liran Barsisa <lbl...@gmail.com>: Sep 09 02:59AM -0700
@Jake How did you find about it? I can't find it on any of these websites, and the IDE doesn't offer it either: https://firebase.google.com/docs/admob/android/quick-start#add-and-initialize-sdk https://mvnrepository.com/artifact/com.google.android.gms/play-services-ads?repo=google https://developers.google.com/admob/android/rel-notes https://developers.google.com/android/guides/setup#add_google_play_services_to_your_project Also, can you please test it out and tell ? Such a change should be possible to check if it has some fix... On Tuesday, September 9, 2025 at 12:49:04 PM UTC+3 Jake wrote: |
Liran Barsisa <lbl...@gmail.com>: Sep 09 03:10AM -0700
Anyway, I removed all workarounds I had for this, including the theme of the AdActivity, and targeted API 36. Testing on Pixel 6 with Android 16, not sure if fixed, at least for test ads. It has the "Test Ad" in the problematic region (the camera hole is there), yet the ad itself is below the top insets. I've also noticed that even though I have "test ad" at the top, some of them are of actual apps (even localized), which is a bit weird... I hope it's ok. See attached. On Tuesday, September 9, 2025 at 12:59:53 PM UTC+3 Liran Barsisa wrote: |
Liran Barsisa <lbl...@gmail.com>: Sep 09 03:13AM -0700
On the other hand, the ad-inspector is still not working properly. Not only that it shows content on the problematic region at the top, but its bottom region is still being cut. See attached. So, maybe it's not fixed... On Tuesday, September 9, 2025 at 1:10:39 PM UTC+3 Liran Barsisa wrote: |
Alina Alcott <alina...@gmail.com>: Sep 08 10:52PM -0700
implementation 'com.google.android.gms:play-services-ads:24.6.0' how to fixes this version 24.6.0 |
Ez'raa Dechwong <dechwon...@gmail.com>: Sep 09 07:06AM +0700
ในวันที่ อ. 9 ก.ย. 2025 06:52 น. <google-adm...@googlegroups.com> เขียนว่า: |
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. |
Hi Pedro,
Thank you for contacting the Mobile Ads SDK Support team.
Please note that our support channel can only best assist you with regards to Google Mobile Ads SDK implementation and technical issues. Should you encounter any difficulties related to the Mobile Ads SDK, kindly provide a detailed description of your concern, and we will guide you accordingly.
![]() |
Mobile Ads SDK Team |