Admob interstitial black screen

[master123]

Hi!

I am having some problems with interstitials on some devices. The interstitials are showing correctly, but when the user presses close, the screen turns black and the only solution is to close the app. This does not, however, happen in all devices. In my test device (android 6) and in the emulators, it works fine. However, some users with KitKat report this problem.

Any suggestions?

Edit: In the phone of a user (friend of mine), the screen does not go black. The interstitial closes but the app freezes (except the banner on the bottom, that continues to work).

[Perry]

Hi,
What version of Fusion are you using.

Admob is working fine, so it's hard to see what's going on without any specs and maybe an example

[kiko]

The Admob extension have problems with some devices using interstitials, I'm testing from 2 years and i have changed all ads in my apps from Interstitials to banner and to Intersticials several times. The conclusion is that there are some problems in the Interstitials with many devices (probably with GPU models and OpenGL compatiblity), with banner I haven't any problems, but with Interstitials advertising the revenues don't grow only decrease from 2 years, and increase the users uninstalls.

[master123]

I just changed something in my code:
- Before, I add an event: On return from Ad => Destroy Interstitial
- Now, I added another one (so I have both): On dismissed Screen => Destroy Interstitial

With this change, now the users with Kitkat experience another problem: the add closes, and you return to the game screen. You can then run the game, but the screen won't update. You can hear the sounds and such, but the screen is unchanged.

Why? I am pulling my hairs off!

[Perry]

Without any example of how your settings are in the MFA , there is not much we can do.
I tested many devices and never ran into this behavior.

[mozg]

i had same problem. I solved it. The way to avoid black screen - put interstitial in 1 frame, not between frames. You need just set *next frame* on *return from ad*. It works fine for me