android – Utilize both Play Services and AdMob SDK-ThrowExceptions

Exception or error:

As MH. pointed out in this question, one no longer needs to include GoogleAdMobAdsSdk-x.x.x.jar in their Android project if they include Google Play Services (see the migration guide). However, I want to, and I’m having trouble.

The problem: the google-play-services_lib project includes a definition for that is deprecated, and has a private constructor. It ends up in the classpath in front of the AdMob jar (within the “Android Private Libraries” entry), so when I try to use it in my code it end up trying to use the deprecated one, resulting in the error: The constructor AdRequest() is not visible. I see no way to re-order the entries inside “Android Private Libraries”.

Why do I want to use both, you ask? I have a single library project with many useful classes, including some utility classes for dealing both Play Services and AdMob. Some of my apps that use that library project use the AdMob utility classes, but not Play Services.

How to solve:

I’ve been testing this, and some changes are required in order to get this working through Google Play Services.

In first place you should remove all imports referencing to old* , since they are now located on*.

As you mentioned, some more changes need to be done:

You cannot instantiate an AdRequest the way it used to be done, but using an AdRequest.Builder as follows:

AdRequest adRequest = new AdRequest.Builder().build();

Also, make sure you replace the name of the package on all layouts, so they call < instead of <

I think that’s all. Good luck!


You can use Google Play Services v12 which does not include the overlapping namespaces. It can be downloaded using the Android’s SDK Manager under “Extras” -> “Google Play Services for Froyo”. This version will co-exist with AdMob stand alone SDK.

Over time Google will probably deprecate both.

Update: Google has announced the deprecation of the stand alone AdMob SDK, you must move to Google Play SDK:

On August 1, 2014, Google Play will stop accepting new or updated apps
that use the old standalone Google Mobile Ads SDK v6.4.1 or lower. You
must upgrade to the Google Play version of the Mobile Ads SDK by then.


Detailed Google Play Services Migration for AdMob is available here:


I think i got the attention of Google/Android for the issue,

Leave a Reply

Your email address will not be published. Required fields are marked *