Shared library missing in android.

Question

02-18 00:02:08.432: ERROR/PackageManager(57): Package com.example.brown requires unavailable shared library com.google.android.maps; failing!

I got this

Answer 1

In case with real device try remove from manifest file:

<uses-library android:name="com.google.android.maps" />

Answer 2

fiXedd (see above) is correct.

You can edit devices you have already created or create a new one. When you create or edit a device inside the AVD Manager, instead of selecting this kind of version target:

Android x.x.x - API Level x

Simply use this kind instead:

Google APIs (Google Inc.) - API Level x

Answer 3

I had the similar problem on a real device. After a loot of googling I found this answer

fixing missing shared library. It turns out that on some custom roms the comp.google.android.map library is missing, you have to install it manually.

• download googleapps
• extract two files
• system/etc/permissions/com.google.android.maps.xml
• system/framework/com.google.android.maps.jar
• remount the /system filesystem rw (mount -o rw,remount /system)
• copy the files in
• do a chmod 644 on them
• reboot

Answer 4

This error occurred to me on an actual device, not an AVD like the other answers. In my case I was running on a Nexus S with a custom ROM that did not have Google Maps installed.

I have read elsewhere that the com.google.android.maps shared library is bundled with the ROM itself and is not bundled as part of an APK.

Therefore the solution for me was to revert to the stock ROM which had Google Maps installed.

BTW, the title of this thread refers to an error that is found in the DDMS LogCat. The first error most users will see (before checking LogCat) will be in the console of Eclipse:

Installation error: INSTALL_FAILED_MISSING_SHARED_LIBRARY 
Please check logcat output for more details.

Answer 5

Your emulator is missing the Google APIs. Create a new AVD that contains the Google APIs, and this error should go away.

Answer 6

I've experienced this error after the AVD was set up properly and working okay. The AVD was still using the Google APIs and I could see the reference to the maps library in Eclipse. The only way I found to resolve this was to delete the AVD and create a new one, as advised by fiXedd.