I'm glad they involved google to make sure the change happens to anyone and also to verify their claims about access. This is the type of response we should expect/demand from other companies. Well done.
This is the same message that was released to the press yesterday.<p>I'm surprised Google itself has not said anything, as they are also at fault for not showing the permissions workflow in the first place.
Isn't this a bit: "Accidentally left open gate to castle. Now closed. No fix in place to make sure other people working closely with Alphabet/Google won't leave door open again. Share and enjoy." ?<p>On another note, from the "privacy policy":<p>1. REVISIONS TO THIS PRIVACY POLICY<p>Any information that is collected via our services is covered by the privacy policy in effect at the time such information is collected we may revise this privacy policy from time to time if we make any material changes to this privacy policy, including any change that we propose that will have retroactive effect, we’ll notify you of those changes by posting them on the services or by sending you an email or other notification, and we’ll update the “last updated date” above to indicate when those changes were made<p>So, they'll <i>let you know</i> if they apply <i>retroactive</i> changes to the policy? How is that any different from "lol, you give data, we do what we want, ok?"
On Android, Pokemon Go requests permission to access your contacts. I declined this access, and the app still seems to work (modulo the crashes & bugs that others have reported).<p>Accessing the camera and location I can understand, but I don't want to give Pokemon Go access to my contacts.
This update completely broke login for people with Pokemon Trainer Club accounts. It doesn't even send the HTTP request: <a href="https://www.reddit.com/r/pokemongo/comments/4sjbeq/ios_users_who_login_using_pokemon_trainers_club/" rel="nofollow">https://www.reddit.com/r/pokemongo/comments/4sjbeq/ios_users...</a>
I'm slightly curious how we prove the statements to be true.<p>There wasn't the normal "this app wants ___ permissions, is that cool?" message from the Google OAuth dialog. I had not idea I'd authorized Niantic to go scrape all my emails, access Google's own processing on them for advertisement system training or review my location history, for example.<p>I'm not so sure why I should believe they didn't do that.
I didn't think they were doing anything nefarious but you never know. I think I will install it now, to see what my grandchildren have been talking about.
Take a look at this list of potential things you can ask for as a developer:<p><a href="https://developers.google.com/identity/protocols/googlescopes" rel="nofollow">https://developers.google.com/identity/protocols/googlescope...</a><p>And most folks will click "Approve" without really reviewing the list. That said, Twitter and Facebook (two other popular OAuth providers) heavily restrict certain "full" access to only trusted applications that they either have a business relationship with or otherwise review the application before allowing those scopes to be requested or used. This incident may prompt Google to do more of that, which isn't entirely great news for the more responsible developers with purpose-built apps.
Great. Although this is really a left-pad situation: it's good that they fixed it, but that fact that it was a problem in the first place is pretty damn disturbing.
Inital thought:
Wow that company is so great... that they did the right thing...<p>...Wait a second do i think a company is great just cause they do things the way they should do them.
It is indeed fixed but updating iOS app alone does not change the permissions. I had to sign out of the app, revoke the permissions on google and then sign back in.
Bit of OT<p>Played Pokémon GO yesterday (iOS 1.0 version) and it was very buggy. Many bugs looked like they were server side (requests freezing), but there were strange rendering errors (like seeing only waves on the ground where Pokémon are, and not the actual Pokémon on them) that could be fixed by restarting the app several times. The phone also got absurdly hot, I never play on it, I don't know if it's normal for it to get like that, but I could barely hold it in my hand.<p>I literally couldn't understand all the fuss about the game, it was unplayable for me...