I have been using the Chartboost extension to show interstitial ads. I have not yet released my project, but occasionally I forget to re-set the ads to test mode (because it changes back after a while) and so I see an ad. I have seen a lot of test ads, and a few real ones, but for the first time, today I saw an interstitial ad that had NO CLOSE BUTTON and NO WAY OUT of the ad. Back button presses and other functions worked normally on the app, which was behind a dark overlay with the interstitial ad on top. The ad remained across all frames while navigating back and only disappeared when I left the app. There is nothing wrong with my code - it is all just very standard stuff and every way that the user could possibly get out of the ad has been covered - this is either a bug in the way it is implemented in Fusion2.5, or this is a bug in the Chartboost SDK itself. Either way, this will get apps banned from Google Play IMMEDIATELY if it gets reported or if it happens while Google is testing it.
I recall seeing someone else post recently about having an app banned because Google said their interstitial ads needed to have a close button, etc. but everything seemed fine in their app. I think I have just reproduced that problem, but I can not get it to happen again. This is a MAJOR FLAW and needs to be addressed immediately, even if it is just some sort of hacked safeguard against this. Unfortunately I haven't narrowed it down at all and it seems to be very sporadic since I have only seen it once, and as far as I know, it has only been reported one other time and only because that person had their app banned from Google Play. Google has a very, very screwed up policy for banning users based on little-to-nothing and 3 strikes of any kind, even all at once, will result in immediate account termination and you will be banned forever from making any new accounts. Will someone please look into this and let me know what is happening here or if there can be some kind of safeguard implemented in case it is the fault of the SDK? I will continue to be testing this, and I will update this with any information. If I find out this is a false alarm and I have overlooked something I will make sure to post that here also. I was building with Android API 15 when this happened, but I am using 19 now, hoping that will fix it.