Don't have an account yet? Then register once and completely free of charge and use our wide range of topics, features and great options. As a registered member on our site, you can use all functions to actively participate in community life. Write posts, open topics, upload your pictures, put your videos online, talk to other members and help us to constantly improve our project and grow together! So, what are you waiting for? Become a part of us today!
Login or registerTo get support for a technical issue such as installing the software, to query a purchase that you've made/would like to make, or anything other than using our software, please visit our Customer Service Desk:
Open a Ticket
this problem get more complicate now with android 9, it is good practices not to ask for them at the same time.
you can simply avoid this kind of issue asking for an Ad when the user is authenticated or not.
BTW you are asking for ads when a touch start always in this type of action ask when you release or end it is better.
this problem get more complicate now with android 9, it is good practices not to ask for them at the same time.
you can simply avoid this kind of issue asking for an Ad when the user is authenticated or not.
BTW you are asking for ads when a touch start always in this type of action ask when you release or end it is better.
Yeap each android update is a challange for developers 
I can ask for ad on authenticated is true, but the problem is when authentication is failed.
X is player authenticated is calling always first before login UI
After that UI appear
and if GPG is installed but user do not log in, then On Login Failed and On Error no happens. He can close an UI and I do not know about that
I'm not sure what is In-Box UI closed because I never received this event, but this sounds like somethink what I need 
I'm testing it currently and I've got a log with events order to investigate how it exactly works
Thanks for BTW advice i will improve that
What is consider a good practices for google
from this link [FONT=Verdana,Arial,Tahoma,Calibri,Geneva,sans-serif]Please login to see this link.]
1. Sign-in
The following checklist tasks apply to implementing player sign-in functionalityin your game. For code examples of how to implement sign-in on mobile games,see Please login to see this link..[FONT=Roboto][TABLE='width: 0']
[TR='bgcolor: #78909C']
[TH='align: left']ID[/TH]
[TH='align: left']Importance[/TH]
[TH='align: left']Description[/TH]
[/TR]
[TR='bgcolor: #78909C']
[TD='align: left']1.1[/TD]
[TD='align: left']Required[/TD]
[TD='align: left']Provide players with a sign-in option to Google Play games services. Your game must implement one of the following ways for players to sign in:
1.1.1. Automatically prompt the player to sign in when your game launches General audience apps should implement Please login to see this link. to help players get quickly authenticated and authorized to use the full set of features provided by the Google Play games services. If silent sign-in fails, your app should prompt players to Please login to see this link..
If the player chooses not to sign in, remember this and do not prompt the player again. Instead, provide a Please login to see this link.. The sign-in button should be easy for players to find (for example, it should be accessible from your main screen and not buried multiple levels deep in your game menu).
1.1.2. Provide a sign-in option in your game If not auto-prompted, players must have the option to login via a Please login to see this link., or from a contextually relevant trigger (for example, during multiplayer match initiation, when submitting a high-score, or when unlocking an achievement). The sign-in button must incorporate the Play Games icon.[/TD]
[/TR]
[TR='bgcolor: #78909C']
[TD='align: left']1.2[/TD]
[TD='align: left']Required[/TD]
[TD='align: left']Do not request unnecessary scopes when creating your sign-in client. Remove any unneeded scopes from your Please login to see this link. construction along with any APIs you no longer use.
For example, you should not request G+ scopes when creating your Google sign-in client. This will avoid requiring new users to unnecessarily (1) create G+ accounts, and (2) review additional consent screens.
// This way you won’t get a consent screen
GoogleSignInOptions signInOption = GoogleSignInOptions.DEFAULT_GAMES_SIGN_IN;[/TD]
[/TR]
[TR='bgcolor: #78909C']
[TD='align: left']1.3[/TD]
[TD='align: left']Required[/TD]
[TD='align: left']Allow players to stay signed-in. After the player signs in successfully to your game, connect them automatically whenever your game starts, until the player explicitly signs out.[/TD]
[/TR]
[TR='bgcolor: #78909C']
[TD='align: left']1.4[/TD]
[TD='align: left']Required[/TD]
[TD='align: left']Provide players with a sign-out option. After signing in, the player must always have the option to sign out. The default Achievements and Leaderboard UIs provided by the Play Games SDK already include a sign-out option, so you don't need to implement a sign-out button for these UIs.
Consider providing a sign-out option in other game screens in your app. For example, your sign-out button can look like this:
Please login to see this picture.[/TD]
[/TR]
[TR='bgcolor: #78909C']
[TD='align: left']1.5[/TD]
[TD='align: left']Required[/TD]
[TD='align: left']Remember if players declined signing-in. If the player declines to sign in when your game initially starts the sign-in flow (for example, if they clicked Cancel in the sign-in UI), you should still allow the player to proceed with gameplay.
When the player launches your game again, don't invoke the sign-in flow automatically. This saves players from having to repeatedly decline signing in whenever they start your game.
One exception is if players are trying to access a gameplay feature that is dependent on being signed-in (for example, starting a multiplayer match). In this case, prompt them to sign in before continuing with gameplay.
[/TD]
[/TR]
[/TABLE]
[/FONT]
you must track user selection, you can use Quicksave for this, teh error from GPG report those change of status
Today I made an update with memory of user selecion. More less, I just do not ask again if previously login failed
But this is nice, short info. G+ hihihi....
I should make a log-out option (however I've never see log-out in other games... but maybe I've never looking for that)
Don’t have an account yet? Register yourself now and be a part of our community!
Almightyzentaco (Fusion 2.5 Tutorials)
Captain Quail (Firefly Tutorials)
