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

Tanu Haru

unread,

Sep 22, 2025, 7:28:28 AMSep 22

to Google Mobile Ads SDK Developers

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

unread,

Sep 22, 2025, 8:02:41 AMSep 22

to Google Mobile Ads SDK Developers

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

unread,

Sep 22, 2025, 9:08:05 AMSep 22

to Tanu Haru, Google Mobile Ads SDK Developers

--

---
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

unread,

Sep 22, 2025, 1:35:38 PMSep 22

to chaota...@gmail.com, google-adm...@googlegroups.com

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

unread,

Sep 22, 2025, 3:08:57 PMSep 22

to Google Mobile Ads SDK Developers

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:

Tanu Haru

unread,

Sep 29, 2025, 8:31:46 AMSep 29

to Google Mobile Ads SDK Developers

Hello AdMob SDK Team,

This is a polite follow-up to my reply sent on September 22nd.

While I have been waiting for your technical analysis, there has been a critical development. On **September 26th**, I detected internal access to my app from Google's own locations (Mountain View & Boardman, CA).

Immediately following this internal access, on **September 27th**, my account status was officially updated to "Invalid traffic concerns". This update also coincided with the first significant increase in my request count (from ~12/day to **122 on Sep 26**).

This sequence of events proves my deadlock theory is correct:

1. My report reached a human team at Google, who began a manual investigation (the access from Mountain View).

2. This investigation seems to have partially lifted the 7-minute SDK delay, allowing my first real data (122 requests) to reach the server.

3. The automated system immediately analyzed this small amount of data and made a flawed judgment ("invalid traffic").

4. The policy team is now acting on this flawed data generated by a technical deadlock.

I am trapped. My code is correct (proven by the Test ID video). The problem is the technical behavior of the SDK when it detects my production ID.

Please, I need your urgent technical intervention. The internal investigation has already started, but they are making a decision based on data that is corrupted by the SDK's deadlock behavior. Only your team can explain this technical anomaly to the policy team before they take irreversible action.

Thank you for your time and assistance.

2025年9月22日月曜日 22:08:57 UTC+9 Tanu Haru:

Mobile Ads SDK Forum Advisor

unread,

Sep 29, 2025, 3:06:35 PMSep 29

to chaota...@gmail.com, google-adm...@googlegroups.com

Hi,

Thanks for getting back to us.

As previously mentioned, this appears to be an account-level issue rather than an SDK integration issue.

Based on our observations, your AdMob account is currently facing ad serving limitations due to "Invalid traffic concerns", which can prevent production ad units from serving—even if everything works correctly using the test ad unit.

We recommend 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-29 13:05:28Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u7BGP:ref" (ADR-00333357)

Reply all

Reply to author

Forward