StartApp ExitAd = Banned App

Monetizing, Advertising & Marketing Advertising Networks
21

So it seems i’m still alive… i’ve worked with Ariel on this issue.
Maybe it can be a specific case here and not a general case as it seems i’m still the only one with a google notification for an ExitAd

This is what we pointed out in my Application: In some cases, my app can’t work on some devices… so in that case we show an error dialog launched from a service. This message is on the device home screen (a standard main window with app title, icon etc etc.) Then, when the user clicks the back button, StartApp ExitAd loads and it could be perceived as an out of app ad showing up.

Ariel, do you agree with that ?

22

There was unfortunately one more person (Yuriy): http://forums.makingmoneywithandroid.com/advertising-networks/3192-notification-google-play.html#post24920
I’ve checked his app and could not find a violation (only maybe the close button on the interstitial is not that clear, I don’t know, or maybe the download more button is the cause of the violation).
He was not using StartApp though but MobileCore.

23

Hi Actarus,

Thanks for following up with everyone here on the forum.

Indeed this seems to be the case, and in this specific app, the warning would have come regardless of which ad network you were using. Even an Admob banner popping up at that point would have led to the warning.

So, for everyone, we can put the lid on this issue - There is no problem with our interstitials/ExitAd units.

Ariel.

24

So you show a Screen (A full screen and not a pop dialog) with error message. on Back you show exit ad.
IF I may ask how is this any different from a simple app that shows some text data and bring up exit ad? Hope you can give details on this.

25

He wasn’t showing a screen, just a dialog box - behind the dialog box was the home screen of the device with icons and widgets and stuff.

26

Got it. Thanks.

27

no, i wasn’t showing simply a dialogbox… it was a standard application screen with an actionbar containing Application’s name and icons. the layout was showing a message saying: “unfortunately, your device is incompatible…” with the reasons . The problem i think is coming from the fact that a service launched this screen in an asynchronous way.
here is the detail:
1- you launch my application
2- you click the button the launch a process (main purpose of the application). But it’s a long running process, this is why i used a service to perform the task
3- once the process is started, no need to keep the main application screen. So the main screen is closed
4- if there is a problem (error, incompatiblity…) the service launch another screen to say what happened. this is the error screen

It can be seen as “Out of App” screen… but this really something unclear. What is “out of App” or “in App” ?? as my service is clearly part of the Application and the screen showed was a standard screen with everything needed to identify from which application it was coming.

28

@Actarus it was clearly out of app. This is a limitation for wallpaper, lock screen, caller id and widgets based apps as of now.

29

You suggest that lock screen is out of app?

30

no but showing ad in lock screen (even if your app is lock screen) is a dicey.

31

some if my apps are new and some are 2 -3 months old.
One of them even have about 50k downloads.

I’ve contacted the startapp team for help, hope they will reply soon, as there are only 6 days left.

32

You were using their search install or just exit ads?

33

Also received 7 day Notification from Google Play with my two games.

REASON FOR WARNING: Violation of the Ad-Policy:
Ads associated with your app must not interfere with other apps or their ads.

Using:
chartboost interstitial,
Startapp interstitial,
Startapp Exit ads by “Back” and “Home” button ,
Startapp searchbox

34

The issue must be one or all of these:
Startapp Exit ads by “Back”
Startapp Exit ads by “Home” button
Startapp searchbox

I also have games with only chartboost interstitial and Startapp interstitial, and they didn’t receive any issue.

35

today I received email from Startapp about Google’s policy.

Over the past 24 hours, Google Play has updated their enforcement methods of their advertising policy.

After thoroughly reviewing the features of our different products, we have come to the conclusion that some of the current features of the Post Call Manager are not compliant with Google Play’s new enforcement methods. Until we release a new version of the Post Call Manager SDK, we strongly advise you to remove it using the attached Post Call Manager SDK removal process.

In addition, we have decided to double the current bonus for using both our Search Box SDK and In App Ads SDK from 25% to 50% of the Search Box pay-per-download rate.

Contact support at [email protected] if you have any other questions.

36

I also got the exact mail, although i explained that i don’t use the Call Manager SDK.

i only have Search Box SDK and In App Ads SDK.

one thing that might be is that i have added the PostCallManager-1.5.0.jar to my libs folder in the apk, but i didnt called it from any where.

please help, if you can.

left only few days till the deadline :frowning:

37

Also Search Box may get you in warning . I didn’t use PostCallManager, and also didn’t add the lib, But still get the warning .

38

so what are you suggesting to do ?

39

Remove StartApp “Search SDK” and “PostCall SDK” jar files(ofcourse calls to them as well) from your App except InApp SDK(For Banner/Interstitial/Exit ads)

40

I’ve talked to Matthew Kaminsky from StartApp that ensured me that The Search Box SDK is fully compliant to Google Play’s policies.

he said that many of the developers who contacted them saying they didn’t integrate the Post Call Manager,
still had the post call manager code, jar file, and/or permissions inside their apps, even if it was not activated or called to.

This is what, believed by StartApp, caused the apps to be flagged.

thank you Matthew Kaminsky :slight_smile: