Why do You need READ_PHONE_STATE
See original GitHub issueI’m submitting a … (check one with “x”)
- question
- any problem or bug report
- feature request
If you choose ‘problem or bug report’, please select OS: (check one with “x”)
- Android
- iOS
After installing this plugin app needs READ_PHONE_STATE
permission.
I get feedback - people doesn’t like it 😕
My app is getting low score only because of that permission.
Is it necessary? What is it for?
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (10 by maintainers)
Top Results From Across the Web
Why do so many applications require permission to read ...
I would guess that half of the apps don't access those values at all. The problem is that for a lower version up...
Read more >Why READ_PHONE_STATE is turned on by default? what ...
In project properties, I have READ_PHONE_STATE set to false, and yet we still get the phone state warning when we update to the...
Read more >What is the "Read Phone State and ID" permission for ...
One of the permissions it requires is "Read Phone State and ID" ... Hope the Facebook guide and the answer are of some...
Read more >Why READ_PHONE_STATE permission asked "make and ...
READ_PHONE_STATE permission is listed as Dangerous permission and provides access to read phone state. It comes under the Phone permission ...
Read more >Permissions updates in Android 11
That's because, as the user interacts with features in your app, you should verify that the features have the permissions that they need....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@wf9a5m75 @battika @piernik It is fixed maybe with 12.0.1?
@piernik & @battika
It looks to be a play services issue according to this stack overflow thread. You should read all of this, even the replies, and a potential workaround for now:
EDIT: In particular google play services 12.0.0