Google sign loopback authorization system deprecated

[cdecron]

Google sign loopback authorization system deprecated

[elringus]

No idea. If someone happen to know, please share.

[elringus]

I've just checked and loopback is working fine for me in editor and in Windows standalone build. The article you've mentioned is only about mobiles. We've been using native auth libs on mobiles from the start, so this change doesn't seem to affect the plugin at all.

[elringus]

[DavidJH2]

I also am able to Authorize through Windows with Chrome

I don't remember the specifics, but I believe that Android, Web, and Windows each have a different way of Authorizing. I believe that when you connect your app to Google Cloud, you have to set one up for iOS (not Android even if your using Android) and another for Windows. It's in the setup procedure for this UnityGoogleDrive API package.

Maybe there is a mistake in the setup for Windows.

---

Another thing to consider is maybe you should go back to the Older oAuth;
I'm still using 0.7.+ / 1.3.0 and it works fine, maybe it's only depreciated in the new oath

---

[cdecron]

Hello,
Excuse me, you're right! There was a problem with my setup on Windows, the json used was the wrong one.
However, this rises another question: every time you switch platform, do you have to go to "Projet settings" > "Google Drive" and modify information?
There isn't any automatic system which recognizes on which platform you are and uses corresponding Goole API information?

Thank you

[DavidJH2]

Awesome!

You don't have to switch the settings each time you change platforms..

You set up both iOS AND Windows and it picks the right one

I had to go through the set-up procedure 2 or three times before I got it right.

[cdecron]

Thank you for you answer, however I'm not sure to understand.
I have two OAuth ID clients, one for Android and one for desktop app.
If I put the one for desktop app in Unity Google Drive settings, you say that it keeps in memory the one for Android if it had been entered before?

[github-actions]

This issue is stale because it has been open 14 days with no activity. It will be automatically closed in 7 days.