Hiding view before the pop animation completes is ugly about gtm-oauth2

[GoogleCodeExporter]

Hiding the view immediately is important because the server typically displays 
some inappropriate instructions for the user once sign-in has completed.

I'm not sure which flow you are saying is ugly. Dismissal of the view 
controller without completing sign-in will not go through the popView method. 

Original comment by [email protected] on 7 Aug 2012 at 6:07

[GoogleCodeExporter]

Dismissal after signed-in is ugly.

Original comment by [email protected] on 7 Aug 2012 at 3:42

[GoogleCodeExporter]

When the user has signed in, the server will display an html message asking the 
user to copy an auth token. In the context of the sign-in controller, this 
messages does not make sense for the user, so the controller is trying to hide 
the message as quickly as possible.

Original comment by [email protected] on 7 Aug 2012 at 5:01

[GoogleCodeExporter]

Then I think we can let the web view to show a more user friendly message such 
as "You've Signed In Successfully", instead of hiding the whole view.

Try presenting and dismissing GTMOAuth2ViewControllerTouch as a model view, 
you'll see it is really ugly to hide the view before the dismissing animation 
completes.

Original comment by [email protected] on 7 Aug 2012 at 5:13

[GoogleCodeExporter]

We do not have control over what text the server displays in the html following 
sign-in.

Original comment by [email protected] on 7 Aug 2012 at 11:25

[GoogleCodeExporter]

No but you have absolute control over what the webview shows up.

Original comment by [email protected] on 20 Apr 2013 at 3:53