Re: [google-admob-ads-sdk] Digest for google-admob-ads-sdk@googlegroups.com - 7 updates in 2 topics
2 views
Skip to first unread message
Asara Dechwong
12:03 AM (9 hours ago) 12:03 AM
to google-adm...@googlegroups.com
ในวันที่ ส. 29 พ.ย. 2025 06:52 น. <google-adm...@googlegroups.com> เขียนว่า:
exciting corp <corp.e...@gmail.com>: Nov 27 07:23AM -0800
*Here’s what I’ve concluded after running a full investigation on my side.*
AdMob’s review team is almost certainly testing the app on an *Android
emulator*, not on a real physical device.
I verified this because the app runs perfectly on four real Android devices
I personally tested on:
1.
Galaxy Z Fold
2.
Galaxy Tab S7
3.
Galaxy A8 2018
4.
Galaxy S11
Not a single crash, freeze, or instability was observed on any physical
hardware.
However, when I tested on a *Pixel emulator*, I immediately reproduced the
same type of error that your team flagged.
This clearly proves that the issue is tied to the emulator environment, not
the application itself.
Foreground services combined with microphone access and continuous audio
processing *are not supported* on Android emulators.
This is a known limitation documented across Android development and is not
something an app developer can fix.
Based on this, I completely redesigned the start flow.
• On emulators: the feature is now *blocked* and a popup clearly states
that sleep monitoring cannot run in a virtual environment
• On real devices:
– first launch shows a normal microphone permission request
– if denied, the user is redirected to system settings
• ForegroundTask + audio analysis now run *only* when real hardware
conditions are detected
This should eliminate every false stability signal that originates from
virtual test infrastructure.
So yes, I’m confident this resolves the issue.
The app itself was never the root cause; the emulator was.
And one more thing.
I originally reached out to “Mobile Ads SDK Support Team Groups.”
I want to be absolutely clear on this.
*Are you an official AdMob support agent, an automated bot response, or
just a community group member replying?*
I need to know who exactly is communicating with me, because the review
outcomes directly affect the operation of my business.
Please respond with your role so I understand who I’m actually dealing with.
2025년 11월 28일 금요일 오전 12시 7분 20초 UTC+9에 Mobile Ads SDK Forum Advisor님이 작성:
exciting corp <corp.e...@gmail.com>: Nov 27 03:53PM -0800
1. Sleep monitor, Snoring - Sleep
ca-app-pub-4313786027034225~5136477531
1. admob_aos_sleeptoneai_banner
ca-app-pub-4313786027034225/3985255380
admob_aos_sleeptoneai_front
ca-app-pub-4313786027034225/5269909054
These are my ad app ID, banner I'm using, and full ad ID. The Admob team
keeps saying that the app keeps turning off? This seems to be a problem,
but with the actual 4 devices including my Android simulator, there is no
problem with the core sleep measurement function at all. It seems like they
repeatedly deliver me the results of the commonly known Robo test inside
Google or send me the results of testing based on underqualified Android
virtual devices. Please give me a specific guide to solving the problem.
There is no problem with the core function, so the ad-mob team said there
is a problem with the function that passed in the Play Store, without any
details. I think it's unfair to say that you will suspend your account on
December 1st?
2025년 11월 28일 금요일 오전 2시 41분 5초 UTC+9에 Mobile Ads SDK Forum Advisor님이 작성:
exciting corp <corp.e...@gmail.com>: Nov 27 03:52PM -0800
1. Sleep monitor, Snoring - Sleep
ca-app-pub-4313786027034225~5136477531
1. admob_aos_sleeptoneai_banner
ca-app-pub-4313786027034225/3985255380
admob_aos_sleeptoneai_front
ca-app-pub-4313786027034225/5269909054
These are my ad app ID, banner I'm using, and full ad ID. The Admob team
keeps saying that the app keeps turning off? This seems to be a problem,
but with the actual 4 devices including my Android simulator, there is no
problem with the core sleep measurement function at all. It seems like they
repeatedly deliver me the results of the commonly known Robo test inside
Google or send me the results of testing based on underqualified Android
virtual devices. Please give me a specific guide to solving the problem.
There is no problem with the core function, so the ad-mob team said there
is a problem with the function that passed in the Play Store, without any
details. I think it's unfair to say that you will suspend your account on
December 1st?
2025년 11월 28일 금요일 오전 2시 41분 5초 UTC+9에 Mobile Ads SDK Forum Advisor님이 작성:
Andrew Chongo Situmba <andrew...@gmail.com>: Nov 28 10:19AM +0200
App ID: ca-app
-bub -2907366599470663-7567415358
Ad unit ID: Barner:ca-app -bub -29073665994470663/6553199665
Interstitial:ca-2907366599470663/5944902998
Native advanced:ca -app -bub -2907366599470663/4581642444
On Thu, Nov 27, 2025, 17:07 'Mobile Ads SDK Forum Advisor' via Google
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Nov 28 10:07AM
Hi,
Thank you for providing the details.
After reviewing your account, I can see that there is a Site Behavior: Navigation policy issue.
Regarding your concern, the “Site Behavior: Navigation — Must Fix” policy error is related to your app’s implementation, specifically its navigation behavior. We recommend checking the following:
Ensure your app does not include any false claims or fake content.
All buttons in your app should function properly and serve a clear purpose. Buttons must not lead to non-working URLs.
The app should not redirect users to irrelevant or misleading content.
Ads should not cover any usable parts of the app.
Ads should not interfere with the user’s ability to navigate or use the app.
We also recommend reviewing our implementation guidance.
Thanks,
Mobile Ads SDK Team
Feedback
How was our support today?
[2025-11-28 10:06:59Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vUWeW:ref" (ADR-00346125)
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Nov 28 11:17AM
Hi,
Thank you for contacting the Mobile Ads SDK Support team.
Based on the details you provided, after reviewing your account, I can see that ad serving has been disabled for your apps. To fix this, please follow the steps in the Disable Ad Serving documentation.
Additionally, your AdMob account is currently inactive. Your account has not served ads for over 5 months. Please note that AdMob accounts that have not served ads for 6 months will be automatically deactivated.
For more information, please refer to the AdMob: Reactivate Your Account documentation.
Thanks,
Mobile Ads SDK Team
Feedback
How was our support today?
[2025-11-28 11:17:48Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vUWYY:ref" (ADR-00346112)
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: Nov 28 10:25AM
Hi,
Thank you for getting back to us.
I understand your concern. Please note that our support channel can only best assist you with regards to Google Mobile Ads SDK implementation and technical issues.
Please note that we have seen one more thread created for the same issue. I would suggest continuing communication to the Mobile Ads team on the one thread.
To help resolve this, I’m escalating the case to the Publisher Support Team, who specialize in account side issues. You will receive an email shortly including all the relevant teams involved.
Thanks,
Mobile Ads SDK Team
Feedback
How was our support today?
[2025-11-28 10:25:46Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vUUKA:ref" (ADR-00346062)
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