Make sure Google Provider is compatible with Google Sign-in about socialite

[rajjanorkar]

• Just pull 3.0.x-dev
• No need to change anything in google developer console
• No need to change/create new api key/secrete etc.
• No other changes if you are not adding any additional scope (other than what package have)

It should just work fine.. i Tested it and it worked.

[eaverdeja]

@No148 I'm not using a custom provider, but upgrading to 3.0.x-dev and changing the scopes seemed to work out for me. The Google+ API Dashboard stopped tracking the requests, so all seems fine. However, how can I be sure the migration was complete and correct?

[No148]

@eaverdeja I don't really know for sure at the moment... I've changed api key and created a specific api key for google sign-in. (which was only possible from this page https://developers.google.com/identity/sign-in/web/sign-in) After using it I just have my fingers crossed... But everything seems to be working fine right now. I wish I knew more, mate!

[No148]

@driesvints I tried to migrate to google sign-in using version 3 of socialite. I read the documentation and found this notes https://developers.google.com/identity/sign-in/web/quick-migration-guide
I have a custom socialtite provider so I was able to override methods from standart providers of socialite.
I created new api keys google sign-in, disabled google+ api in console and it worked as usually.

[cincauhangus]

how can i make this compatible with laravel 5.2.x?

[driesvints]

@cincauhangus 5.2.x isn't supported anymore. Please upgrade to the latest version.

[Casperhr]

Any plans for a 2.x fix?

[driesvints]

@Casperhr we actually pushed a 2.0 fix a couple of days ago. Use 2.0.x-dev to pull it in.

[driesvints]

Friendly reminder to not rely on -dev versions too long and to upgrade your apps eventually.