I'm surprised that, in *this* case, there's not a check within lint (I haven't seen one) that warns about this, it seems like a commonly used permission would have a simple check for misspellings applied.
kris On Wed, May 23, 2012 at 8:38 AM, Mark Murphy <[email protected]> wrote: > On Wed, May 23, 2012 at 8:31 AM, guich <[email protected]> wrote: >> Hi, >> >> I added this: >> >> <uses-permission >> android:name="android.permission.WRITE_MEDIA_STORAGEa" /> >> >> (note the leading 'a') >> >> ... and android compiler didn't complain about the wrong permission. >> This leads me that he is silently ignoring permissions that he doesn't >> handle. How can i make android compiler/builder warn me about them? > > I doubt that you can, as valid permissions are not knowable at compile > time. There is nothing stopping a third-party app from defining the > permission that you tried to use. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > Android Training...At Your Office: http://commonsware.com/training > > -- > 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 -- 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
