On Sun, Jan 13, 2013 at 4:39 PM, William Ferguson <[email protected]> wrote: > @Mark @Kristopher really? the doco for android:exported seems to indicate > that setting it to false will produce the precise behaviour I am looking > for. > http://developer.android.com/guide/topics/manifest/activity-element.html#exported
IMHO, it is because the chooser is written poorly. According to Google, it is because having a non-exported activity with an <intent-filter> is poor coding. http://code.google.com/p/android/issues/detail?id=29535 http://commonsware.com/blog/2012/04/25/how-isolated-adobe-reader-activity-issue.html > And testing on a JellyBean device indicates that it is indeed so. The > Activity becomes available for selection via the IntentChooser when invoked > from within my app but is not visible when invoked from another app. > > What makes you think this is not the correct solution? Because they apparently just fixed it, if your statement is correct. I have no idea when. As I noted in the issue, it does not work at least Android 2.2 through Android 4.0.3. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Localized Android Question-and-Answer Sites: http://www.andglobe.com -- 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
