The READ_PHONE_STATE permission has cropped up before, but this is a variation that relates specifically to the Unity Facebook SDK.
Installing any Unity Facebook SDK version later than 7.9 will prompt Unity to auto-include the READ_PHONE_STATE permission in the manifest, which in turn translates to a permission message in Google Play requesting “Device ID & call information”. The full description of this in Google Play is as follows: “Allows the app to determine the phone number and device IDs, whether a call is active ant the remote number connected by a call”.
For many, if not most developers using the Unity Facebook SDK, this permission does not align with the permissions actually required, and given its invasive nature is likely to turn away users at the point of installation.
Unity Facebook SDK versions of 7.8 and below do not appear to trigger the permission’s inclusion. It seems that recent changes to the Facebook SDK have included items that are auto-flagged by unity when compiling the manifest. Although using earlier versions of the SDK will ‘resolve’ the issue, doing so is clearly not a long-term solution.
Given the SDK’s popularity, it would be greatly appreciated by myself (and the many others scattered throughout the forums who have suffered through resolving this permission issue) if the Unity team could interface with Facebook to find a way to either prevent the auto-inclusion of the permission in later versions altogether, or to facilitate some way of allowing devs to exclude those components that do require the permission.