[CRITICAL DEADLOCK] Account-level Limit (pub-4897...) is causing 7+ min SDK delay, preventing review (VIDEO PROOF & CODE)

[Tanu Haru]

Hello AdMob SDK Team,

​I am a developer experiencing a critical system deadlock. My account limitation (policy) is causing an SDK behavior that makes the automated review process physically impossible. I need an engineer to investigate.

​THE PROBLEM:

​1. My AdMob Account (pub-4897133038334286) has been under an Ad Serving Limit since August 12, 2025, for "Traffic Quality."

​2. THE CORE PROOF (Code is Correct): When I use a Global Test Ad ID (ca-app-pub-3940...) in my app, test ads load INSTANTLY. This proves my application code is correct. I have included my MainActivity.java in the evidence folder below to prove my standard, async implementation.

​3. THE DEADLOCK SYMPTOM: When I use ANY Production Ad ID from my account (even on a registered Test Device AND on a normal, non-test user's device), the AdMob SDK waits 7+ minutes (or requires specific user interaction) before loading the ad.

​4. THE DEADLOCK: My app is a utility (a split-the-bill calculator). Users finish their task and leave within 1-2 minutes. Because of this 7-minute SDK delay (which is a symptom of the limit itself), 99% of my clean, real users close the app BEFORE the first ad request is ever sent. This means I can provide ZERO traffic data to the automated review system.

​This is an unsolvable loop. The review cannot complete because the "symptom" of the restriction (the 7-min delay) prevents the "cure" (collecting clean data).

​Please, can an engineer investigate why this account limitation (pub-4897...) is manifesting as an SDK delay that makes review impossible?

​EVIDENCE (VIDEO PROOF, CODE & SUPPORT HISTORY):

I have collected video proof of this bug (Prod ID failing/delaying), my MainActivity.java file (to prove correct implementation), and screenshots of my unanswered official support ticket (Case ID: [2-4828000039057]).

Google Drive Link:

https://drive.google.com/drive/folders/176fYWiXtqucZm2wKe9c-gCSj2EC_ULQe

​APP DETAILS:

Package Name: choco.nextyearforsure.letssplitthebill

Prod Interstitial ID: ca-app-pub-4897133038334286/6206663113

Prod Banner (Top) ID: 

ca-app-pub-4897133038334286/4591093450

Prod Banner (Bottom) ID: (Same as top banner.)

ca-app-pub-4897133038334286/4591093450

​Thank you for your help.

[Tanu Haru]

UPDATE: I have added a crucial A/B test video to the Google Drive folder.The evidence in the folder now proves:

1. (Video A: [Test Ad ID] Let's split the bill! Time elapsed since launch): My App + Global Test Ad ID (ca-app-pub-3940...) = Loads INSTANTLY. 

2. (Video B: 9/18 [Production Ad ID/Test Device] Let's split the bill! Time elapsed after app launch & 9/20 [Production Ad ID/Test Device] Let's split the bill! App launch followed by ad display after 10 minutes): The EXACT SAME App + my Production ID = 7+ minute DELAY.

This 100% proves my code (WebView, SplashScreen) is NOT the problem. The delay is ONLY caused by the Account-level Limitation on my Production ID.

Google Drive link:

https://drive.google.com/drive/folders/176fYWiXtqucZm2wKe9c-gCSj2EC_ULQe

2025年9月22日月曜日 14:28:28 UTC+9 Tanu Haru:

[Vinay Kumar]

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-admob-ads-sdk/53ad0bc8-0d4d-4c7f-9f81-ab9fcf331966n%40googlegroups.com.

[Mobile Ads SDK Forum Advisor]

Hi,
Thank you for contacting the Mobile Ads SDK Support team.
Please note that this channel supports only SDK-related and technical issues.
​​​​​​​I checked your AdMob account and found that ad serving is limited for your apps due to “invalid traffic concerns”.
To restore ads showing in your app:

• Know your ad traffic sources and app visitors
• Never click on your own ads
• Avoid partnering with parties you don't trust
• Learn more about limited ad serving

Based on the details that you shared, 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-22 11:34:45Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u7BGP:ref" (ADR-00333357)

[Tanu Haru]

Thank you for your quick reply.

​I must clarify this point, as it is critical: **I am NOT asking the SDK team to solve my "invalid traffic concern" (the policy issue).**

​I am contacting the SDK (technical) team to report a **CRITICAL TECHNICAL BUG** in the SDK's behavior.

​Please re-read my evidence (the Google Drive link: https://drive.google.com/drive/folders/176fYWiXtqucZm2wKe9c-gCSj2EC_ULQe):

​1. My app's code is **100% correct**. (This is PROVEN by **Video A([Test Ad ID] Let's split the bill! Time elapsed since launch)**, where a Global Test Ad ID (ca-app-pub-3940...) loads INSTANTLY in my app).

​2. Your SDK, when it detects my Production ID (which is under a "policy limit"), creates an **abnormal 7+ MINUTE DELAY** (This is PROVEN by **Video B(9/18 [Production Ad ID/Test Device] Let's split the bill! Time elapsed after app launch & 9/20 [Production Ad ID/Test Device] Let's split the bill! App launch followed by ad display after 10 minutes))**).

​This TECHNICAL DELAY (a symptom *your* SDK controls) is creating an automated "review deadlock," because my users leave before the 7 minutes are up.

​The AdMob Help Center (the policy team) *cannot* fix this. This is an **engineering problem (an abnormal SDK behavior)**.

​Please, I beg you, re-investigate this **technical symptom** (the 7-minute delay) that is *caused* by your SDK's response to a policy limit. This is a technical bug, not a policy complaint.

​Thank you.

2025年9月22日月曜日 20:35:38 UTC+9 Mobile Ads SDK Forum Advisor: