I guess there's no use for android:exported="false" when you specify an intent filter. So it seems logical to me that specifying an intent filter overrules the android:exported="false".
Do you need to know this for something more specific than just understanding? On 6 apr, 23:50, alexk-il <[email protected]> wrote: > On Apr 6, 11:24 am, a2ronus <[email protected]> wrote: > > > Maybe those examples use intent filters? > > > "The default value (of android:exported) depends on whether the > > broadcast receiver contains intent filters. The absence of any filters > > means that it can be invoked only by Intent objects that specify its > > ... > > Thanks for trying to help. > > My understanding of the documentation you quote, that it is related to > the "default value" of the android:exported. In other words, it > describes the default value of the <android:exported> when it is not > explicitly specified by the Manifest. > > I am not sure this explains why explicitly specified > <android:exported=false> works in case of the BOOT_COMPLETE. Or did I > miss it again? > > Best > Alex > > > > > exact class name. This implies that the receiver is intended only for > > application-internal use (since others would not normally know the > > class name). So in this case, the default value is "false". On the > > other hand, the presence of at least one filter implies that the > > broadcast receiver is intended to receive intents broadcast by the > > system or other applications, so the default value is "true"." -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en To unsubscribe, reply using "remove me" as the subject.
