Hi Rob,
Thanks for the suggestion. I removed both Firebase plugins but got the same result.
One detail that might help. The consent screen is shown twice in the first time the game runs. First it asks for the player’s Google Play Games profile. After granting this permission, a few moments later, a second consent screen is shown asking for the player’s Google Plus profile.
A few more attempts:
Removed all ads plugins: same result
Removed Photon plugin: same result
Removed gpgs plugin: both consent screens are gone
So, it seems it’s really in the GPGS plugin. But if you are not adding the Google Plus Scope in code, then is there any other way I can be doing that?
Maybe look through your Google Play Games console and go to the Google API’s and make sure you don’t have Google+ turned on somewhere.
Rob
Did it. Google+ API was indeed enabled in my account, but I think it shouldn’t be the cause for the consent screen if I’m not requesting, somehow, to use it. Nevertheless, I disable it and the result is the same. I will repeat the test in the next hour just to make sure there isn’t some cache issue.
Retested after 2 hours and I got the same results.
Rob, Kirill
Do you have any other suggestion?
Never used the gpgs plugin but I would remove the hogs plugin for now until fixed I guess
Hopefully there is the way to fix the issue by using Auth.GoogleSignInApi but it will take a while for implement and test. I’ve already started working on it and will inform you here about the process.
Kirill
Thanks Kirill.
I’ll be waiting for the fix. Please let me know if you need any assistance, maybe with tests. For me this issue is really critical because it’s blocking the game to be featured by Google. I hope you understand why I keep asking for updates.
Hi Kiril,
Do you have any update on this?
He is still working on it. Unfortunately, it’s not a simple “change a constant and rebuild” situation. We are having to do some refactoring to get this change in.
Rob
Hi Rob,
I know it’s not a simple fix, but it’s really hard to keep waiting and waiting. Is there anything concrete about this topic? Any forecast (days, weeks…)?
Again, sorry for keep pushing. I’m trying not to come here and ask the same thing over and over.
I wish there was a more concrete answer on an ETA. I know an engineer is working on it. I don’t have the exact details, but it sounds like we have to implement a completely different login method and needless to say, it’s not an easy change. I’m trying to get a better answer.
Rob
Hi Rob,
Well, me again, 10 days have passed, so…
Just received another email from Google asking for an update, but there’s nothing I can say. Should I give up?
I’m hoping we have a solution soon. I’m sorry this is taking so long, but it’s taken us a lot of effort to implement this. An engineer is actively working on it.
Rob
16 days more…
Any news?
If I understand the engineer working on this correctly, he is having to completely rewrite the plugin from scratch. Apparently to change the login process requires using a completely different GPGS library. This is a huge plugin with the sheer number of API endpoints.
It’s going to take time.
Rob