Can anyone please confirm this: "I realized that because I was installing the app directly from the .apk file instead of the market, the Phone Calls and Storage permissions always come up. When it is put on the Market, they are gone. Don't think this was intended, but setting targetSdkVersion does fix it. "
message from Jarcikon (4-th from top). Thanks and regards, Max. On Nov 29, 2:11 pm, Max Binshtok <max.binsh...@gmail.com> wrote: > Rachel, thanks for the extended explanation but I did understand what > Diane was saying. I just don't see how this can solve my problem. Or > better put how this problem can be solved. I might be wrong (I > probably am) but I remember that initially I wanted to get the IMEI or > something and without requesting PHONE_STATE the app crashed. But it > was on 1.0 and not 1.5. Doesn't matter now anyway. > > Diane, what would be the right place to put this? It was just before > <supports-screens ... /> in my manifest, which was the last tag in > the manifest. I tried removing it and adding through the "wizard" the > "wizard" placed it as the last tag in the manifest. I tried moving it > to the very top as the first tag after the opening <manifest .. > tag. > Did not work. > > Can you please confirm this: > > "I realized that because I was installing > the app directly from the .apk file instead of the market, the Phone > Calls and Storage permissions always come up. When it is put on the > Market, they are gone. Don't think this was intended, but setting > targetSdkVersion does fix it. " > > message from Jarcikon (4-th from top). That was my original intent in > the original post. > > If that's not the case - then what do I need to do - there must be > some way to overcome this problem since I don't need those > permissions. I don't want to put out a newer version to the market and > have this problem and then I can't basically go back. I have updated > my application to support various screen densities long time ago, but > this permission thing was holding pushing the update forever. > > Thanks, > Max. > > On Nov 29, 11:52 am, Dianne Hackborn <hack...@android.com> wrote: > > > Are you sure you are putting <uses-sdk> in the right place? > > > And thanks Rachel for the explanation. Trying to explain to the user some > > subtlety about old applications here seemed pretty difficult, and not to > > useful for a temporary situation. > > > On Sat, Nov 28, 2009 at 12:02 PM,Max Binshtok<max.binsh...@gmail.com>wrote: > > > > How do I overcome this? > > > > I have: > > > <uses-sdk android:minSdkVersion="3" android:targetSdkVersion="4"></ > > > uses-sdk> > > > > If that is what you mean by "explicitly targeting API 4 or latter" > > > then this does not seem to solve the problem. I don't need and don't > > > want those permissions. > > > > Thanks. > > > > Slightly OFF TOPIC: > > > I don't understand... Why do you want to tell people that my > > > application requires phone permissions when it clearly doesn't? This > > > is really, *really* bad! People are suspicious and hesitant to install > > > apps that require not needed permissions. Moreover, PHONE_STATE > > > permission has this weird interpretation in a smaller font - read > > > phone state and identity (Identity!? People are terrified by all > > > "identity theft" propaganda). At some point I asked for PHONE_STATE > > > permissions to access the serial number to be able to tell different > > > users apart. Do you know what this lead to? I had a real comment on > > > the market from someone who claimed that I stole his password > > > (whatever this means) and he had to spend 3 hours on the phone with > > > TMobile to gain control of his phone (with foul language all over the > > > comment) . I don't need those permissions and I don't want people to > > > be suspicious and write stupid comments and this is not only me as the > > > first message attests as well. > > > > Regards, > > > Max. > > > > On Nov 28, 1:44 pm, Dianne Hackborn <hack...@android.com> wrote: > > > > Yes, and I am saying this is the normal expected behavior for apps that > > > are > > > > not explicitly targeting API 4 or later. > > > > > On Sat, Nov 28, 2009 at 10:35 AM,Max Binshtok<max.binsh...@gmail.com > > > >wrote: > > > > > > Diane, it seems to me that you did not understand the problem. > > > > > > I (and I believe other people) do NOT ask for those permissions in the > > > > > manifest since I do not need them. But when the application is to be > > > > > installed they show up (it says that the app is asking for those > > > > > permissions). Please read the very first post. It says that "Hello > > > > > World" application when to be installed is asking for those > > > > > permissions although they are not present in manifest. > > > > > > Regards, > > > > > Max. > > > > > > On Nov 26, 1:46 am, Dianne Hackborn <hack...@android.com> wrote: > > > > > > These are new permissions added to 1.6. If an application is > > > targeting > > > > > > anything below API 4 (1.6), they will automatically be requested > > > because > > > > > in > > > > > > 1.5 and lower there was no restriction on these operations. As of > > > 1.6 > > > > > these > > > > > > permissions were added, and if you target API 4 or later you need to > > > > > > explicitly request the permission in your manifest to be granted it. > > > > > > > On Wed, Nov 25, 2009 at 10:17 PM,Max Binshtok< > > > max.binsh...@gmail.com > > > > > >wrote: > > > > > > > > I am having the same problem and I just want to confirm: > > > > > > > > You are saying that when you try to install over the air (just by > > > > > > > downloading APK file) you get asked those permissions, but when > > > your > > > > > > > application is installed through the Android Market - you are NOT > > > > > > > asked for PHONE_STATE and STORAGE? Is that correct? > > > > > > > > From my side I can add that I had targetSDK=4 and when installing > > > from > > > > > > > APK over the air those permissions come up... (I have been banging > > > my > > > > > > > head on the walls for quite some time now). On 1.5 they don't come > > > up! > > > > > > > Not on the emulator and not on the device. > > > > > > > > Regards, > > > > > > > Max. > > > > > > > > On Oct 8, 1:13 pm, Jarcikon <jarci...@gmail.com> wrote: > > > > > > > > Sorry about the double post. I realized that because I was > > > > > installing > > > > > > > > the app directly from the .apk file instead of the market, the > > > Phone > > > > > > > > Calls and Storagepermissionsalways come up. When it is put on > > > the > > > > > > > > Market, they are gone. Don't think this was intended, but > > > setting > > > > > > > > targetSdkVersion does fix it. > > > > > > > > > Mike > > > > > > > > > On Oct 5, 3:36 pm, Jarcikon <jarci...@gmail.com> wrote: > > > > > > > > > > Chris, > > > > > > > > > > I am having the same problem. This is due to the update to > > > Donut > > > > > (1.6 > > > > > > > > > SDK). According to the docs, if you set targetSdkVersion in > > > your > > > > > > > > > manifest file to "4" thesepermissionsshould not appear unless > > > > > > > > > specifically requested. However, I have tried this and it is > > > not > > > > > > > > > working for me. > > > > > > > > > > Does anyone have a solution? > > > > > > > > > > Mike > > > > > > > > > > On Sep 18, 8:54 am, ch13fw <ch1...@gmail.com> wrote: > > > > > > > > > > > I am working on a widget and have it pretty much how I like > > > it, > > > > > but I > > > > > > > > > > have one problem. When I package it and install it, it says > > > in > > > > > the > > > > > > > > > > "allow this application to" portion that it wants access > > > > > > > tophonecallsandstorage. I know this will be a no-go if I want > > > anyone > > > > > to > > > > > > > > > > ever use it. > > > > > > > > > > > I have not set up anypermissions. Same thing happens even > > > > > > > > > > if > > > I > > > > > make > > > > > > > > > > Hello World. > > > > > > > > > > > Sorry if this has been ask before, but I have searched quite > > > a > > > > > bit > > > > > > > > > > looking for an answer. > > > > > > > > > > > Chris > > > > > > > > -- > > > > > > > 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<android-developers%2bunsubscr...@googlegroups.com> > > > <android-developers%2bunsubscr...@googlegroups.com<android-developers%252bunsubscr...@googlegroups.com> > > > > > > <android-developers%2bunsubscr...@googlegroups.com<android-developers%252bunsubscr...@googlegroups.com> > > > <android-developers%252bunsubscr...@googlegroups.com<android-developers%25252bunsubscr...@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<android-developers%2bunsubscr...@googlegroups.com> > > > <android-developers%2bunsubscr...@googlegroups.com<android-developers%252bunsubscr...@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 > > ... > > read more » -- 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
