Please answer the questions about build version and network, will save
developers a lot of time !
What steps will reproduce the problem?
1. Install Chrome to Phone extension on PC browser and app on Android
2. Sign-in with mobile app
3. Click to sign-in with desktop browser
What is the expected output? What do you see instead?
Chrome to Phone should redirect to sign-in page. Instead, it shows a blank page
written "Redirecting..." with nothing in the address bar.
What version of the android, in Settings -> About phone -> Build number (
ex. FRFxx ) ? If less than FRF50 - see the FAQ.
Gingebread 2.3.5 build BOKK1
Is the phone using WiFi or mobile network when problem occurs ? If Wifi,
are you behind a firewall that blocks outgoing connections ?
3G or Wifi doesn't matter.
Can you open "Gmail" application ? Do you see new messages without hitting
'refresh' ?
Yes.
Can you open "Talk" application ? Do you see incoming chats ?
Yes.
Please provide any additional information below.
Chrome version: 17.0.963.56
Using F12 key in Chrome to inspect the "Redirecting..." page shows the
following problem in "chrome_ex_oauth.js" file on line 526:
https://chrometophone.appspot.com/_ah/OAuthGetRequestToken?oauth_callback=chrome
-extension%3A%2F%2Foadboiipflhobonjjffjbfekfjcgkhco%2Foauth_interstitial.html%3F
chromeexoauthcallback%3Dtrue&oauth_consumer_key=anonymous&oauth_nonce=Kjwtm&oaut
h_signature=aRvEgyGGP4bWxWUkLMXgCu6pDtE%3D&oauth_signature_method=HMAC-SHA1&oaut
h_timestamp=1329935754&scope=https%3A%2F%2Fchrometophone.appspot.com&xoauth_disp
layname=Chrome%20To%20PhoneFailed to load resource: the server responded with a
status of 400 (Bad Request)
chrome_ex_oauth.js:526Uncaught Error: Fetching request token failed. Status 400
Original issue reported on code.google.com by paulo.ivson@gmail.com on 22 Feb 2012 at 5:42
Original issue reported on code.google.com by
paulo.ivson@gmail.com
on 22 Feb 2012 at 5:42