Android: Issue: Violation of Interfering with Apps, Third-party Ads, or Device Functionality policy

Temeteron commented 4 years ago

As it seems google claims that the ads are triggered after the application is closed. The update i did had no changes in the code about the triggering of the ads.

Probably something changed at the algorithm of google store. I also cannot recreate the claims of google.

The ad i use is an interstitial. It is triggered from a user action. Also i check from the platform { App }, the state of the application before i show the ad.

Those are the dependencies i use

"dependencies": {
    "@angular/common": "^9.0.1",
    "@angular/core": "^9.0.1",
    "@angular/forms": "^9.0.1",
    "@angular/platform-browser": "^9.0.1",
    "@angular/platform-browser-dynamic": "^9.0.1",
    "@angular/router": "^9.0.1",
    "@capacitor-community/admob": "^1.0.1",
    "@capacitor/android": "^2.2.0",
    "@capacitor/cli": "^2.2.0",
    "@capacitor/core": "^2.2.0",
    "@capacitor/ios": "^2.2.0",
    "@ionic/angular": "^5.2.2",
    "@ionic/app-scripts": "^3.2.4",
    "chart.js": "^2.8.0",
    "core-js": "^2.5.4",
    "css-loader": "^3.4.2",
    "jetifier": "^1.6.6",
    "karma-coverage": "^2.0.1",
    "karma-phantomjs-launcher": "^1.0.4",
    "rxjs": "^6.5.4",
    "to-string-loader": "^1.1.5",
    "tslib": "^1.9.0",
    "webpack": "^4.41.6",
    "zone.js": "^0.10.2"
  },

I believe i tested everything that will fix the problem at the typescript code, except from changing the type of ad itself.

rdlabo commented 4 years ago

As it seems google claims that the ads are triggered after the application is closed.

What is mean this?? If possible, I would like to get more information.(ex: error log). Thanks.

Temeteron commented 4 years ago

There is not error log. When testing everything is working fine. When uploading a new version of the app it is rejected by the store. The only response from the google store is the following email:

Hi Developers at Greasidis Dimitris,

Thanks for submitting {your-app} to Google Play. After review, your app has been rejected due to a policy violation. If you submitted an update, the previous version of your app is still available on Google Play.

Issue: Violation of Interfering with Apps, Third-party Ads, or Device Functionality policy

Ads associated with your app must not interfere with other apps, ads, or the operation of the device, including system or device buttons and ports. This includes overlays, companion functionality, and widgetized ad units. Ads must only be displayed within the app serving them.

Next steps:

Read through the Interfering with Apps, Third-party Ads, or Device Functionality policy and make appropriate changes to your app. Be sure to remove any ads that appear after the user has exited the app, or after the user has pressed the back button to exit the app.
Make sure that your app is compliant with all other Developer Program Policies. Additional enforcement could occur if there are further policy violations.
Sign in to your Play Console and submit the update to your app.

If you’ve reviewed the ads policy and feel this decision may have been in error, please reach out to our policy support team. One of my colleagues will get back to you within 2 business days.

Best,

Google Play Review Team

rdlabo commented 4 years ago

Issue: Violation of Interfering with Apps, Third-party Ads, or Device Functionality policy

Where did you display AdMob Ad position? You can't display ads on above the content. In reality, it will be displayed at the top or bottom of the app, like this: https://i.stack.imgur.com/OR76l.png

So we must add margin for admob area: like this: https://github.com/rdlabo-team/capacitor-admob/blob/master/demo/angular/src/app/home/home.page.ts#L58-L64

and can't do this: https://user-images.githubusercontent.com/1326504/35255268-145225e2-ffa3-11e7-8eb6-0a5a2fa06e93.png

Temeteron commented 4 years ago

At first i had the following setup:

const options = {
  adId: **********,
  adSize: AdSize.SMART_BANNER,
  position: AdPosition.BOTTOM_CENTER,
  isTesting: false,
}

This was working obviously but it was rejected and then i tested the same options as the example in the documentation for an interstitial ad.

const options = {
  adId: **********,
  isTesting: false,
}

Same thing. It worked but still rejected.

So probably the buttons of the phone should be always visible even in an interstitial app?

rdlabo commented 4 years ago

Sorry, I'm not know. I'm using this plugin now, right.

You can reply this email to ask the AdMob team for more specifics. This issue may not a plugin, but an AdMob convention issue.

Temeteron commented 4 years ago

Is there a way to set margin to an interstitial ad throught the adOptions. I believe this is the solution of the problem

rdlabo commented 4 years ago

I understood! You don't said about banner. This issue is about interstitial.

Certainly we need the option of ensuring the height of the header and footer. Can you create pull request about this??

capacitor-community / admob

Android: Issue: Violation of Interfering with Apps, Third-party Ads, or Device Functionality policy #1