Admob Interstitial crashing

I'm getting a consistent crash when dismissing Admob interstitials. I'm sure everything is set right, because I've copied and checked against the sample scenes. Plus, the setup isn't rocket science: 1) Make interstitial request, 2) On Interstitial Ready, show interstitial, 3) On Dismissed Screen destroy interstitial and jump to next frame (it crashes even without the "jump to next frame" bit). The debug log shows an error on dismissing the screen:

libEGL - eglMakeCurrent:740 error 300d (EGL_BAD_SURFACE)

At least I think that's the location of the error; I'm not experienced with log reports. The above line comes right after two AdMob "onDismissScreen" entries.

Any ideas? Anyone else encounter this? I'm using the 281.3 beta Android exporter.

Fred

Hi.

I found that interstitial is killing the surface of some device which have Adreno GPU, this is not all the time (you may notice when the left-top X to close the ads appears then there is no problem), for now please use interstitial in a single frame and restart the frame when resume activity.

please can you test

https://dl.dropboxusercontent.com/u/...Mob_FUSION.apk

please test in several device type to detect which device fails with interstitials (second frame)

As per request the Google admob, we are going to migrate the admob object from sdk 6.4.1 to Google play service, unfortunately device with android 2.2 will not be covered. That is a limitation by Google and no from Clickteam.

more info here:

https://developers.google.com/mobile...play-migration

Locks up here. Nexus 5 with 4.4.2.

Do you have any rough idea when the Google Play Service version will be ready? Is it like weeks or months? I know that with development there's no way to know exactly, I'm just wondering what the hope is.

Hi,

please stay tune with a new beta that i will post, have a fix for this (please don´t build using min/max 2.2/2.2 need 2.2/4.1 at least).

Tried the new beta and it still crashes after dismissing & destroying the interstitial.

please try this example again and let me know, work ok here in nexus 7.

use latest api 18 or 19 to build

https://dl.dropboxusercontent.com/u/...Mob_FUSION.mfa

It works here on the Nexus 5. Haven't gotten to try it on the 7 yet. One thing that's happening lately though is that sometimes the text on buttons doesn't display properly. They're set to use the system font and system colors.

The font problem happens without system fonts too.

i test here with several game using dialog and seems ok, please try to make a step list for recreate it here, to test!

thanks in advance.

I will try to make a simple project that has the problem. It's weird that it only happens sometimes. That makes it hard to test, because I can run it on my phone one minute and it's fine, then try it later and it's not.

I would like to use the settings button (android ver. 2.2). Is there any possibility to use it when you fix this issue?

Thanks.

I think you will want to use at least Android version 2.3

I don't remember all the details (Fernando could comment more) but Google is doing some changes and isn't going to support Android 2.2 anymore with some of its features. (Not to forget the newer version just run a lot better)

As Jeff, mentioned correctly, Google is using now Google Play Services for AdMob and they (Google ) drop android 2.2 from it, this is considering that lees than 1% of devices still are 2.2, so please set version 2.3 as min target, it still a Froyo version but without the size limitation and other limitations, that not come to my mind at the moment.