Problem with admob 4.1.1

[Vectory]

Hello.
I'm trying to make an App that use tabs with a minimal android version
1.6.

Everything works fine, and i even display ads with prior version of
admob.
Now i tried to update to version 4.1.0 of Admob first and the 4.1.1.

My app has a welcome activity with ads, these work fine.

When you enter on the tabs, the test ad appears and after around 20
seconds the activity exits, without error on Log Cat, no exception and
no warniing from phone.
i'm placing the ad on the tabHost layout, below the Frame Layout, on
android version 1.6,

I've tried both 4.1.0 and 4.1.1 and none of these works, the activity
just exits.
If i'm offline and no ad is loaded the app works just fine.

Any thoughts on this, is it a known bug?

Thank you in advance for your help.

Best Regards


Tiago Silva

[Eric Leichtenschlag]

Hello Tiago,

I have experienced a bug in Android 1.6 where the activity (not the application) sometimes exits when making an Ad Request.  The logcat did not return an error, but it did return a bunch of debug statements directly after the INFO/Ads: adRequestUrlHtml debug statement.  It wasn't deterministic for me though, it didn't happen every time.  Can you check logcat again if you reproduce your issue again and post these debug statements?

Also, try overriding the onDestroy method and destroy the adView, and see if that helps (using 4.1.1):

@Override

public void onDestroy() {

  adView.destroy();

  super.onDestroy();

}

Cheers,

Eric

[Eric Leichtenschlag]

Mick,

Are you using version 4.1.1 of the SDK?  Version 4.1.0 was not compatible with Android 1.5 because it used AsyncTasks.

Cheers,

Eric

[Steve]

I believe I was also getting this problem. I was getting crashes when
using Android 1.5 (HTC Hero) or Android 1.6 (Emulator). Android 2.0+
semed to work OK.

Basically the VM dies with a long message written to the log but no on-
screen message. It would normally happen after 2 or 3 page views (each
containing an ad) has been shown, but it was basically unpredictable.
Sounds similar to those reported above.

The solution for me was, as reported above, doing a
"adView.destroy()" *before* the view containing the ad got destroyed.

It's as though in those older Android versions, something doesn't get
cleaned up correctly after each ad view, eventually leading to the
crash.

Steve


On Aug 22, 6:02 pm, Eric Leichtenschlag <eleichtens...@google.com>
wrote: