Installed application: Page not found after successful grant through LocalServerCodeReceiver

[JiriWalter]

There is frequent error when authenticating user through GoogleWebAuthorizationBroker.AuthorizeAsync method. The authentication page is correctly displayed but after confirming application access the browser hangs on "Page Not Found" (localserver:portnumber). But, both tokens are successfully transmitted back to the application. This problem is more frequent when authenticating through proxy.

Hotfix: I did some research and replaced the code with my own copy of LocalServerCodeReceiver. The problem is that HttpListener closes before the response is delivered. I've made quick hotfix by placing Thread.Sleep(10) on the line 99 in the original file (after closing the response stream and before returning instance of AuthorizationCodeResponseUrl). There is probably more elegant way how to fix this but I have no more time to search for correct fix.

[chrisdunelm]

Closing as stale, please reopen if still an issue.

[chrisdunelm]

Re-opening, looks like this is still as issue: http://stackoverflow.com/questions/43357777/gmail-api-net-googlewebauthorizationbroker-authorizeasync-leaves-browser-waitin

[chrisdunelm]

Closing, as I cannot reproduce this.
Please re-open if this still occurs. It would be very helpful if instructions for a reliable reproduction can be given.

[mbeiley]

I can still reproduce this. The source code I'm using is shown here:

https://stackoverflow.com/questions/43357777/gmail-api-net-googlewebauthorizationbroker-authorizeasync-leaves-browser-waitin

I just tested it again now, and it does provide the code okay, but the browser stays spinning, with the URL:

http://localhost:50331/authorize/?code=4/<redacted_code>

I tested it using Chrome as my default browser (Version 59.0.3071.115 (Official Build) (64-bit)).

You can also test it with our product that is using this code. It is Remind-Me. If you install the trial and create a new event, and go to the "Email" tab, and press "Configure..." you can choose to use OAuth2.0 and then press "Get Authorization..." to reproduce the issue.

I don't know how to "re-open" this issue? Apparently, just replying doesn't automatically re-open it, and I don't see any link to re-open?

[jskeet]

Reopening.

What kind of application are you running (console? WinForms? WPF?)? If you could reproduce this in a minimal sample app, that would really help. Do you see any exceptions at all? I'd expect it to spin if it hasn't managed to create the local server properly, for example.

[rolshevsky]

@chrisdunelm @jskeet also reproducible for me.

I temporarily added small workaround with using custom LocalServerCodeReceiver.cs and calling StopListener manually. Task.Delay is required here:

private async void StopListener(HttpListener listener)
{
    await Task.Delay(2000);
    listener.Close();
}

If you could reproduce this in a minimal sample app, that would really help.

I can even reproduce it with this Google OAuthDesktopApp sample:

[jskeet]

@rolshevsky: It's not clear why you'd want to call StopListener manually. We'll try to reproduce with the sample though, thanks.