[android-developers] Re: Optional permissions
is there a difference between declaring uses-feature android:name=android.hardware.nfc android:required=false / and not declaring any nfc specific uses-feature at all? Dominik -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Optional permissions
On Thu, Aug 25, 2011 at 6:58 AM, Dominik dominik.gru...@fhnw.ch wrote: is there a difference between declaring uses-feature android:name=android.hardware.nfc android:required=false / and not declaring any nfc specific uses-feature at all? Possibly. With other hardware-related permissions (e.g., android.permission.CAMERA), asking for the permission implies uses-feature android:name=... android:required=true. While android.permission.NFC is not listed in the table for this in the uses-feature documentation, it might be a documentation bug and has the same behavior as the others. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in Oslo: http://bit.ly/fjBo24 -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Optional permissions
Thanks Dianne, I will have a try! On Aug 25, 12:09 pm, Dianne Hackborn hack...@android.com wrote: Permissions don't prevent your app from being available. Required features may be inferred from permissions you request. If you don't actually require the feature, then explicitly request the feature with uses-feature setting the attribute android:required=false. You can always see the features your app is requesting with aapt dump badging path-to-apk. Be sure to use the most recent aapt; that is the one Market uses to analyze your app when it is uploaded. On Wed, Aug 24, 2011 at 8:40 PM, Alex Xin xinxi...@gmail.com wrote: Hello experts, I have a app that could use NFC as one of the communication methods. Bu that is optionally, users still could use other alternative ways to communicate. To use NFC my app needs to add permission android.permission.NFC on my manifest.xml file. But if I do this I believe that users who doesnt has a NFC-enabled phones cannot access my app on the market because market has a filter mechanism to prevent those devices to see the apps. So I need a solution that will allows users to see my apps, but my apps also need NFC permission. I want to know: 1. Is there a way to add a permission dynamically at runtime? 2. If there's no such a method to add a dynamic permission, is there a way to declare a permission as Optional Permission so that users still could see download this app from market even if they dont have a NFC hardware on their phone because NFC is just a optional requirement? Thanks, Alex -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Optional permissions (revisited)
Other opinions? I agree absolutely. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Optional Permissions
This has been kicked around the #android irc channel off and on for a while, and the basic answer from Google devs seems to be no, thats not how we want it to work. (Which leads to only one alternative really - ship multiple versions of your app into the marketplace, with different security requests and a shared uid..) Not to pick on anyone specific, but the various webpage apps (wikipedia.. bank of america.. etc) that require gps are perfect examples here. Sure, SOMETIMES I might want to know what pages (or branches) are nearby. But usually, I just want to use the app. And sometimes I explicitly might -not- want the app to be able to suck up my location... On Wed, Dec 10, 2008 at 2:03 PM, Brad Gies [EMAIL PROTECTED] wrote: Is there a way to make a permission optional for the user? I would like my app's user to be able to send emails to their contacts if they want, but don't want them to have to approve the Contacts permissions when the app is installed. What I'd like to do is have a button in the app that they could click on, the app would check to see if it had that permission, and if it didn't popup a dialog box to ask the user if they want to give that permission, and only continue if they agreed, and disable that feature if they don't want to. Obviously this would have to be built into the framework for it to work, but is it there now? Is there a way to grant an application additional permissions after it is installed? Sincerely, Brad Gies - Brad Gies 27415 Greenfield Rd, # 2, Southfield, MI, USA 48076 www.bgies.com www.truckerphone.com www.EDI-Easy.com www.pricebunny.com - Moderation in everything, including abstinence --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: Optional Permissions
I don't think the answer is that it's absolutely not how we want it to work, but as of today you are granted all permissions you request at install time. It is certainly possible for the user to be able to pick which permissions they want to grant at install time, I actually had a change I was doing to allow for this at the package manager level, but never had time to finish it. Even so, just adding the facility raises more questions than it answers: how to you modify the current permissions UI to allow for this without making things even more confusing for the user, how to you give the user a facility to change this decision later on in some kind of way most users can understand, etc. There maybe are a few things that are more desireable and understandable to the user, such as getting location information, that could be done as a special case. Again, I've answered questions about this, and have not said we don't want it done, but it just isn't a high priority for us to work on right now vs. a number of other things. Btw I realize that IRC is a favorite thing for discussion on open source projects, but a lot of the android engineers find it to be much more of a distraction than it is worth, so I would suggest not drawing significant conclusions from any discussion there. :) You are much more likely to have more people involved in such discussions on the android-platform/android-framework/etc groups. On Wed, Dec 10, 2008 at 1:05 PM, Disconnect [EMAIL PROTECTED] wrote: This has been kicked around the #android irc channel off and on for a while, and the basic answer from Google devs seems to be no, thats not how we want it to work. (Which leads to only one alternative really - ship multiple versions of your app into the marketplace, with different security requests and a shared uid..) Not to pick on anyone specific, but the various webpage apps (wikipedia.. bank of america.. etc) that require gps are perfect examples here. Sure, SOMETIMES I might want to know what pages (or branches) are nearby. But usually, I just want to use the app. And sometimes I explicitly might -not- want the app to be able to suck up my location... On Wed, Dec 10, 2008 at 2:03 PM, Brad Gies [EMAIL PROTECTED] wrote: Is there a way to make a permission optional for the user? I would like my app's user to be able to send emails to their contacts if they want, but don't want them to have to approve the Contacts permissions when the app is installed. What I'd like to do is have a button in the app that they could click on, the app would check to see if it had that permission, and if it didn't popup a dialog box to ask the user if they want to give that permission, and only continue if they agreed, and disable that feature if they don't want to. Obviously this would have to be built into the framework for it to work, but is it there now? Is there a way to grant an application additional permissions after it is installed? Sincerely, Brad Gies - Brad Gies 27415 Greenfield Rd, # 2, Southfield, MI, USA 48076 www.bgies.com www.truckerphone.com www.EDI-Easy.com www.pricebunny.com - Moderation in everything, including abstinence -- Dianne Hackborn Android framework engineer [EMAIL PROTECTED] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
