Admob Error in Eclipse for android:configChanges

Asked 26/10, 2011 at 7:21 Answered 11/4, 2015 at 11:58

132

Eclipse is giving me an error on the android:configChanges line in my AndroidManifest.xml:

<activity android:name="com.google.ads.AdActivity"
              android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize"></activity>

the error is:

error: Error: String types not allowed (at 'configChanges' with value 'keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize').

If I leave only keyboard|keyboardHidden|orientation there's no error, but compiler asks for the 4 remaining ones when I try and build.

I'm using GoogleAdMobAdsSDK-4.3.1.

Any ideas?

EDIT: I got it working by changing my project.properties (default.properties on SDK's lower then 14) file to:

# Project target.
target=android-14

and in my SDK Manager having the SDK Platform Android 4.0 - Revision 14 installed.

It should also work for SDK Platform android 3.2 - revision 13, so you just have to change the project.properties target to android-13 if that is the case. Basically you just have to make sure that the SDK revision is 13 or above, and that you have that SDK installed in the SDK manager and the project target in default/project.properties pointing to it.

Gewgaw answered 26/10, 2011 at 7:21 Comment(5)

which android version do you use? – Macruran 26/10, 2011 at 7:29

Min SDK version 7 - Android 2.1 – Gewgaw 26/10, 2011 at 7:31

I tried changing the target to 13, but it is not working .. what could be the reason ? – Plier 11/10, 2012 at 3:53

@gurcan15 yup its working now. – Plier 15/1, 2013 at 4:24

Simple answer: the mentioned config changes are not support in Android 2.1, have a look here:

http://developer.android.com/guide/topics/manifest/activity-element.html#config

e.g. uiMode needs API Level 8.

From the official AdMob Documentation:

Requirements

The Google AdMob Ads SDK for Android requires Android 1.5 or later. Make sure you have the latest copy of the Android SDK and that you're compiling against at least Android v3.2 (set target in default.properties to android-13).

have a look here: https://developers.google.com/admob/android/quick-start

So I think your tools version is not updated to at least Version 13.

Macruran answered 26/10, 2011 at 7:33 Comment(16)

I changed <uses-sdk android:minSdkVersion="7"/> to version 8, 9, 10, 11, 12... still have the error... also tried removing the line and it still gives me the error. – Gewgaw 26/10, 2011 at 8:4

screenSize and smallestScreenSize are only supported in API Level 13, which means Honeycomb, are you sure you need them? As they are quite Honeycomb specific. – Macruran 26/10, 2011 at 8:8

Well if I don't declare them I get this in LogCat:

The android:configChanges value of the com.google.ads.AdActivity must include screenLayout. The android:configChanges value of the com.google.ads.AdActivity must include uiMode. The android:configChanges value of the com.google.ads.AdActivity must include screenSize. The android:configChanges value of the com.google.ads.AdActivity must include smallestScreenSize. You must have AdActivity declared in AndroidManifest.xml with configChanges.

And where the ad is meant to be I get a black box with the last error message written in red in it. – Gewgaw 26/10, 2011 at 8:21

I've added a quite important note from the SDK to my response above. – Macruran 26/10, 2011 at 8:40

Okay my default.properties target is android-7, I change to 13, and it says Unable to resolve target 'android-13'. I have "Android SDK Tools, revision 13" installed in my SDK manager though... – Gewgaw 26/10, 2011 at 8:59

you need to have the 3.2 target installed also. – Macruran 26/10, 2011 at 9:28

Got it working with the new revision 14 for IceCreamSandwich. Thanks – Gewgaw 26/10, 2011 at 13:49

Can I asked you to post just how you got this working so far the only luck I've had is setting the project api level to Android 3.2 or is this what you did? – Farflung 28/10, 2011 at 3:3

Hopefully my EDIT in the original post gives enough extra detail on getting it working to help you. – Gewgaw 1/11, 2011 at 8:17

So AdMob will only work on newer phones? I would be cutting out any users with older phones, including me. – Marucci 21/12, 2011 at 3:41

No, you only need to compile at least against Android 3.2, but that doesn't lock out older devices (this is configured in the manifest). – Macruran 21/12, 2011 at 13:21

i have simple Question Can i use google GoogleAdMobAdsSdk-6.0.1.jar to show ads on android 2.2 ,Because our application need to run on android 2.2 and higher. – Enhanced 17/6, 2012 at 13:42

If i set target=android-13 then i see that it can only run with android 3.2 ,am i right? if any thing wrong let me known. – Enhanced 17/6, 2012 at 13:45

Can You please answer this question #25916336 ? – Jonathonjonati 18/9, 2014 at 14:54

I have an admob question: #36390229 – Sera 3/4, 2016 at 18:56

The link is broken – Thelma 6/4, 2016 at 16:22

Easy solution: (and NO you don't need to to change the min-sdk value !!)

Step 1: Change "project.properties" file

# Project target.
target=android-13

Step 2: In Eclipse

Project > Clean... > (select your project) > Clean projects selected below > OK

For a complete explanation with real example use this tutorial http://www.monkeycoder.co.nz/Community/posts.php?topic=1121

Cheers !

Thorwald answered 6/2, 2012 at 22:17 Comment(1)

Excellent! I too was using sdk7 albeit the google api version. So I used # Project target. target=Google Inc.:Google APIs:13 in my properties file. – Juttajutty 4/4, 2012 at 0:21