On Wed, Oct 20, 2010 at 5:16 AM, horatzica <[email protected]> wrote: > My second one: Is there a nicer way to address this issue other than > have 2 builds/apks, one that uses the library, with <uses-library > android:name="com.google.android.maps" /> added in the manifest, and > the other one, without the use of the library?
There is an undocumented android:required attribute on <uses-library>. If you set that to false, it should allow your app to load even if the Maps are not available. You would use Class.forName() or something to determine if you have Maps capability, so you could disable the UI that leads to a map (e.g., disable a menu option). As I mention, this is undocumented, and ordinarily I don't encourage that. However, Dianne Hackborn (Google engineer) is the one who pointed it out, and I consider her to be a veritable extension to the docs... :-) -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android App Developer Books: http://commonsware.com/books -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
