Edit: For a detailed how-to, check out my answer.
I\'m struggling with it for two days now, hope someone can help.
I\'m trying to use the ne
Deprecated: I guess the problem goes away with Google Maps Android API v2. If you decide to use deprecated v1, the solution is below.
So Jake answered the exact problem, but I thought that it would be useful for someone to have a more or less detailed how-to. So how to make ActionBarSherlock work with maps?
I assume you have ActionBarSherlock set up and working as a library project, you can find lots of tutorials on how to do it.
If you just want to use MapActivity with ActionBarSherlock - it's easy:
If you would like to use MapView with Honeycomb features like Fragments or Loaders:
protected void supportInvalidateOptionsMenu()
and change its visibility to public
(this step is not needed in new version of ABS)<uses-library android:name="com.google.android.maps" />
in the application tag of your Manifest fileimport android.support.v4.app.LoaderManager;
insted of import android.app.LoaderManager;
It's the best workaround for now, until Google puts maps in the compatibility library. I hope they'll do it before 4.* devices outnumber 2.*...
You need to use the loaders from the support library rather than the ones from the platform. Since those are only available on Android 3.0+ and the fact that you've included them in your class definition will cause the pre-3.0 classloader to reject your class outright. Switching your imports to the support library variants should be all that's needed for that.
If you look above the exception in Logcat you should see one or more VerifyErrors which will outline specifically what it took issue with.
You also can only use the android-support-v13
library on Android 3.2 and up (hence the v13
in its name).