Which part of the blame goes on Apple?
[1] https://www.ftc.gov/news-events/press-releases/2013/02/path-...
"Users can grant or deny access to contact data on a per-app basis. Any call to CNContactStore will block the app while the user is being asked to grant or deny access. Note that the user is prompted only the first time access is requested; any subsequent CNContactStore calls use the existing permissions."
> The operator of the Path social networking app has agreed to settle Federal Trade Commission charges that it deceived users by collecting personal information from their mobile device address books without their knowledge and consent.
Android didn't really close/tighten permissions until 2014 with Android 4 Ice Cream.
[1] https://www.ftc.gov/news-events/press-releases/2013/02/path-...
No they weren't
For instance you are playing a game and a call comes in, you needed them to allow that and to possibly not crash your game and save your data as well as for some analytics/social network integration.
Also if you allowed os level music to be played over game audio, you need that to handle music and app state when a call came in.
It was/is a default on many large app platforms including game engines like Unity and any social network app integration such as Google Play Game Services and Unity analytics [1][2]. When you have READ_PHONE_STATE you could get the number and more.
For games it wasn't such a big thing but for apps like Facebook that are always running and kept alive playing a silent sound [3], it could get every call that ever came in on record and apparently did. With these holes, apps could scrape everything and they did [4].
[1] https://forum.unity.com/threads/unity-5-1-adds-android-permi...
[2] https://stackoverflow.com/questions/39668549/why-has-the-rea...
[3] https://www.reddit.com/r/iphone/comments/3opxhm/facebook_app...
[4] https://arstechnica.com/information-technology/2018/03/faceb...
> Where's the reference that you needed READ_PHONE_STATE to suspend your app? Shouldn't the app be automatically suspended when the caller app goes into the foreground?
Mostly for analytics and social platforms to access unique identifier for analytics you needed it such as in Unity up to 2015 [3][4].
> The Android build enforces READ_PHONE_STATE if the code has references to SystemInfo.deviceUniqueIdentifier. INTERNET is added when any network classes are referenced. ACCESS_NETWORK_STATE is added when calling Application.internetReachability
Also, early on it was required for saving state and or ensuring the app didn't crash. Mobile OSes were moving fast and without it the apps didn't auto suspend which they mostly do now. You can see some of this discussion in the links I included above. Anything older than Android Ice Cream required it as well.
It is added in by many plugins as well such as Google Game Play Services or other Analytics packages that most people didn't check. There was a reason the market was and is flooded with analytics packages.
It seems to re-pop up in analytics packages quite a bit and many aren't checking close enough per this example 2016 [4][5][6][7].
Largely it is due to people just building and shipping fast, there are other things that trigger it but the most common are doing things on suspend when a call comes in or to help allow the music to play in your game/app and turn off when a call comes in or analytics packages.
For the most part it is not needed now but up to 2016 it still was in many areas since Android started.
[1] https://play.google.com/store/apps/details?id=com.facebook.k...
[2] https://play.google.com/store/apps/details?id=com.facebook.o...
[3] https://answers.unity.com/questions/987433/read-phone-state-...
[4] https://forum.unity.com/threads/unity-5-1-adds-android-permi...
[5] https://stackoverflow.com/questions/39668549/why-has-the-rea...
[6] https://github.com/facebook/facebook-sdk-for-unity/issues/58
[7] https://forum.unity.com/threads/read_phone_state-permission-...
There also seems a lot of pro-Apple bias that seems unwarranted/
The phone/call permissions, especially for Android, were needed for any app that wants to suspend when a call comes in and for analytics/social libs.
I always hated that about Android especially because even harmless games made it look like you were taking contacts and monitoring calls.
Of course this would be abused and it is all over the place. Unfortunately lots of apps/games are specifically built to harvest data and this was a major flaw in their permissions handling. You shouldn't need a monitor phone calls permission to allow a call to come in over your app while someone is using or playing it.