What's the problem? (Site Behavior)

[exciting corp]

There is no URL problem, and there is no problem with the functionality of the app.
Google Mobile Adobe Team says there's a problem..
Is the color of this banner and app a problem?

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team.

We understand that receiving feedback from the Google Mobile Adobe Team about the banner or app color is confusing, especially since your URL and app functionality appear fine. We are happy to investigate this specific concern regarding the visual elements of your implementation.

To thoroughly troubleshoot this, please provide the following details:

• Your App ID.
• The Ad Unit ID(s) involved.
• Confirmation if you are currently using any mediation networks.

Kindly provide the requested details via reply to the author option.

Thanks,

 

Mobile Ads SDK Team

Feedback
How was our support today?

               
[2025-11-27 15:06:25Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vUWYY:ref" (ADR-00346112)

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for getting back to us.

I have noticed that queries are being submitted in multiple threads. For better tracking and faster support, please consolidate all communications into one thread.

Upon reviewing the details of your inquiry, it appears that the Adobe review team has flagged your app for a “Site behavior” or “Navigation error” violation, even though you see no URL or functionality problems. No, the color of your banner/app does not cause this type of rejection.

Please note that my area of responsibility is limited to providing support for Google Mobile Ads SDK integration and resolving associated technical issues.

Could you kindly provide the app ID and ad unit ID via reply to author option for further investigation?

Thanks,

 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-11-27 17:40:09Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vUWeW:ref" (ADR-00346125)

[exciting corp]

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]

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]

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]

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

--

---
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/ioB2i000000000000000000000000000000000000000000000T6E4MP00C6x316JXQuupZNUQK8Ws3A%40sfdc.net.

[Mobile Ads SDK Forum Advisor]

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]

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)