On Mon, Jun 4, 2012 at 6:32 PM, Kostya Vasilyev <[email protected]> wrote: > Or it might be a missing mimeType attribute in the intent filter (since the > uri uses the content scheme).
Having consulted with some HTCians, the Linkify change they made simply blocks the appearance of a chooser. If there is more than one activity that handles a given Intent triggered by the Linkify link, they go with the default. So, while it's possible the HTC Linkify somehow fits, it seems less likely, unless there's a bug in their implementation. Hence, I agree that the <intent-filter> may be the problem. I'd first try: <data android:scheme="content" android:host="com.ctenophore.gso.help" /> which more accurately describes your scenario (right now, you claim to handle everything in the content:// scheme, and *also* claiming to handle everything with your specified host). If that does not help, add in android:mimeType="..." to the one <data> element, replacing ... with the appropriate value for whatever this activity handles. For example, if you are linking to HTML pages, use android:mimeType="text/html". -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.7 Available! -- 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
