1

I have a few permissions in my manifest:

<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.INTERNET" /> 

When I go to install my application, it says it has access to: "Phone calls - read phone state and identity." Which of these permissions is triggering that warning? I never read phone call information. Is it my use of PowerManager.isScreenOn() ?

gnychis
  • 7,289
  • 18
  • 75
  • 113

3 Answers3

1

By a process of elimination, I would suggest it was: ACCESS_NETWORK_STATE as none of the others are specifically to do with the phone.

Alex Wilson
  • 6,690
  • 27
  • 44
  • that's kind of lame. It seems to overscare the user, but all I'm doing is accessing WifiManager. That has nothing to do with phone calls. – gnychis Jul 07 '12 at 15:49
  • 1
    eek, it turned out to be this: http://stackoverflow.com/questions/1747178/android-permissions-phone-calls-read-phone-state-and-identity – gnychis Jul 07 '12 at 16:03
  • Ouch. Is it all fixed for you now? – Alex Wilson Jul 07 '12 at 16:07
1

It turned out to be an issue with a bug where you need to at least specify a minimum SDK of 4:

Android permissions: Phone Calls: read phone state and identity

Community
  • 1
  • 1
gnychis
  • 7,289
  • 18
  • 75
  • 113
0

none of these are related to read phone call info. As it should be like .READ_PHONE_STATE(read phone call). I think it must be because of ACCESS_NETWORK_STATE.

Sting Ray
  • 1
  • 4