adview

I am trying to show a adview in my android application, but it shows an InflateException. This terminates the app and I cannot do anything. Here is my logcat - 05-06 14:09:09.428: E/AndroidRuntime(928): FATAL EXCEPTION: main 05-06 14:09:09.428: E/AndroidRuntime(928): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.kodspider.parkon/com.kodspider.parkon.HomeActivity}: android.view.InflateException: Binary XML file line #18: Error inflating class com.google.ads.AdView 05-06 14:09:09.428: E/AndroidRuntime(928): at android.app.ActivityThread.performLaunchActivity

Following the suggestions provided in this question I modified my AdMob code to be compliant with the recommendations, that effectively worked reducing the number of exceptions that were appearing. However a new exception is rising. The code is the following: @Override protected void onDestroy() { if ( adView != null ) { adView.destroy(); adView = null; Log.i(ApplicationData.APP_TAG, TAG + ": OnDestroy, destroying the Adview"); } super.onDestroy(); } The method adView.destroy() appears to work well as the LogCat message is published. Just after this message I am getting the following exception

I just found a problem with Adview when screen orientation changes and multi-threads are running. I think this might be a bug of Adview. And this problem impacts all the webviews in the application. The webviews stop loading any content, i.e. they either show blank or the content that was shown before. The test environment is Platform: Google Nexus S + Android 4.1.2 (not only this platform, a lot of other platforms, even the emulators are affected) Ads SDK: 6.4.1 (we also tested Ads SDK 4.1.1 which has the same problem) The way to reproduce this issue is construct an android project using the

I have a test project which demonstrates a memory leak caused by Admob 4.1.1. The basic scenario is I have two activities and I switch back and forth between the main and the sub activity several times. I then switch to DDMS and force a few GCs. Then dump the HPROF and look at the historgram filtered by com.test* to see how many instances of the main and sub activity there are. My screenshots of the histogram are attached: A leak! I then commented out the ads in the xml and reran and there were no leaks: No leak now I have found some relevant posts to Admob leaks such as here: Android AdMob