Able to reproduce the issue on 31.0.1650.34 (Official Build 230433) beta-m

Version 32.0.1700.6 beta seems to still have this problem.

I'm not sure yet how this used to work, since it looks like a bug in the tutorial. I got the contacts sample to mostly work by putting this section in its manifest:

  "web_accessible_resources": [
    "chrome_ex_oauth.html",
    "chrome_ex_oauthsimple.html"
  ],

The response page from the server is attempting to redirect back to these extension pages, but those navigations are blocked and then redirected to about:blank. 

Able to reproduce on 31.0.1650.57 (Official Build 235101) m Windows 7

XP SP3, Chrome 31.0.1650.57 m here, same result.

Adding the web_Accessible_resources manifest entry fixed this for me.  wasted my sunday night, though.  Thank you all for posting and replying to this so I could find a solution.

Should update the tutorial page ASAP

Confirmed that this is a bug in the sample. It was working before M31 because of a bug in Chrome which is now fixed. The solution is to add the manifest fragment from comment #4.

Keeping in mind I know next to nothing about Chrome's inner workings...

I have located the manifest file and inserted the code from comment #4, disabled/re-enabled the extension, rebooted, and confirmed the changes persisted, but I'm still getting the same behaviour. Is there anything extra I need to know? Does the code need to be inserted in a certain order? Is there more than one copy of the manifest files (ex: one pristine/source, one altered/in use)? 

Apologies, disregard my previous comment - I just caught on that this thread is about OAuth in general and not the Chrome to Mobile extension, which utilizes it and currently has the same issue. Someone linked here from a thread about the extension and the rest is obvious. 

That said, if anyone has any thoughts on applying the above fix to the C2M extension there are a lot of people who would appreciate it.

Added the mainfest fragment given in Chrome  issue 310870 . But, still able to reproduce the issue.

Checked in chrome stable version 31.0.1650.57 and beta version 32.0.1700.19.

Is there any other workaround on this?

This issue has been corrected in Chrome to Phone v2.3.3, so an answer can probably be found there. From a quick glance the mechanism appears quite different, or at least laid out quite differently, I did not have any luck figuring it out.

https://code.google.com/p/chrometophone/issues/detail?id=504

I have tried the manifest change listed in the bug but its still not working.

Any updates?

atanwar@, what code are you applying the change to? What errors/behavior do you see?

The contacts sample works for me with the manifest change applied, so I don't know what else might be going wrong for you.

Shouldn't chrome provide some sort of feedback (console log) when it blocks based on this (like it does with permissions and security policy)? That could have saved me a few hours.

 Issue 328757  has been merged into this issue.

This seems to have been resolved. Extension is working for me now.

Slated to an old branch and no activity in the bug in over a year suggest that this can be archived.