AIR 3.9 - mobile app starling, pure as project and interstitial ads forces close

Forum|Forum|12 years ago
October 12, 2013
6 replies
8525 views

Hi there,

we have a pure as project in which we updatet the air version to 3.9.

The app uses starling and the admob extension - > http://www.adobe.com/devnet/air/articles/admob-ane-android.html

If an admob interstitial is shown the app crashes and starts again.

With AIR 3.8 there is no problem with this.

Perhaps it has also something to do with this bug:

https://bugbase.adobe.com/index.cfm?event=bug&id=3364803

The debugger shows nothing, the app only shows a black screen after closing the interstitial ad and restarts.

We also have interstitial ads in a project that is not pure as and we use AIR 3.9 in this app. No problem here.

We don't use starling in this non pure as project so perhaps the issue has something to do with starling. The strange thing is that it worked nicely with AIR 3.8.

Some ideas?

This topic has been closed for replies.

Jacowaco

Participant

I solved it by stopping my app when the event deactivated is called:

Starling.current.stop(true);

Jacowaco

Participant

I'm experiencing the same problem using Air 4.0.

Any update on this issue?

J

Jimmy_Slam

Participant

I have the same problem. And we need to use AIR 4 because it is a tea timer that needs to be running in the background... Please review that bug.

I tried with two ANEs and different versions of Starling and 3.8 is fine. Newer versions just crash the app.

X

xojltoh

Participant

I have similiar issue, when Starling.current.showStats = true;

if Starling.current.showStats = false; evetything works fine.

grosssmutttrAuthor

Known Participant

We still have this problem. Even if we set showStats to false...

This is really bad because we can't update the app...

Z

Zaebancija

Participant

Thanks for this post.

I just switched my game back to AIR 3.8 because of this bug. It was driving me nuts. I used AIR 4.0 previously.

With AIR 4.0, it sort of worked if I called Starling.current.stop(true) before showing the interstitial, and then after closing the interstitial I called Starling.current.start(). But I wasn't quite comfortable with that. I think it still crassed if you touch the screen before the interstitial showed up.