search

herususanto10121980 / chrometophone

Automatically exported from code.google.com/p/chrometophone
0 stars 0 forks source link

Browser extension cannot log in... #319

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Please answer the questions about build version and network, will save
developers a lot of time !

What steps will reproduce the problem?
1. Installing the extension succesfully (No problems)
2. Clicking the Extension icon selecting log in.
3. Stuck forever on "OAuth Redirect Page" with only content "Redirecting..."

What is the expected output? What do you see instead?
I expected to be logged in and it would just work. Did that on my windows xp 
netbook, no problems at all. This is running windows 7 home premium. Chrome 
fully updated.

What version of the android, in Settings -> About phone -> Build number (ex. 
FRFxx ) ? If less than FRF50 - see the FAQ.
Running 2.3.3 Gingerbread. No problem with the phone.

Is the phone using WiFi or mobile network when problem occurs ? If Wifi, are 
you behind a firewall that blocks outgoing connections ?
Mobile network - Again only a problem with login in chrome browser.

Can you open "Gmail" application ? Do you see new messages without hitting 
'refresh' ? Yes my google account works perfectly fine, both Youtube, Picasa 
and Gmail and both on phone and desktop.

Please provide any additional information below.
It workls perfectly fine on the phone and with my netbook, I just can't log in 
on my desktop computer. The browser extension fails. Not a phone issue since it 
works fine with my other computer.

Original issue reported on code.google.com by zeb...@gmail.com on 30 May 2011 at 10:00

GoogleCodeExporter commented 8 years ago 
I have the same issue

Original comment by akshayda...@gmail.com on 8 Jun 2011 at 12:43

GoogleCodeExporter commented 8 years ago 
I also have the same exact problem..

Original comment by jae...@gmail.com on 9 Jun 2011 at 12:49

GoogleCodeExporter commented 8 years ago 
I should note after formatting and reinstall mine works. You guys might try to 
reinstall xhrome...

Original comment by zeb...@gmail.com on 9 Jun 2011 at 6:54

GoogleCodeExporter commented 8 years ago 
I have the same issue.  Chrome can sign in fine at work, but not at home.  I 
haven't gone so far as uninstalling Chrome, but I did clear cache and history 
to no avail.

Original comment by rjs...@gmail.com on 9 Jun 2011 at 6:33

GoogleCodeExporter commented 8 years ago 
I've started to notice this since the update to Chrome 12. Wonder if this is 
related. 
Chrome to Phone stopped working totally.

I also recently install Google Tasks Extension (by Google), having the exact 
same error of stuck on "OAuth Redirect Page". But at least Google Tasks seems 
to work.

Original comment by bryan....@gmail.com on 10 Jun 2011 at 3:07

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
After having the same issue and looking for a solution, I found this place.  I 
then noticed my time and date were wrong.  This machine is a new build and I 
guess I need a new CMOS battery.  I manually corrected the time and date and 
just for kicks, I tried to sign into chrome2phone again.  It allowed me to log 
in and a successful test was conducted.

Original comment by alanrk...@gmail.com on 13 Jun 2011 at 8:03

GoogleCodeExporter commented 8 years ago 
Might have not anything to do with the time and date settings, because mine was 
correct and it didn't work.
And I just tried to sign in an hour ago, it just worked.
Maybe google did something changes at their server side.
Seems to be working fine now.

Original comment by bryan....@gmail.com on 13 Jun 2011 at 10:38

GoogleCodeExporter commented 8 years ago 
OP here I tested mine last night on the computer with problems and it worked as 
well. Guess something was fixed somewhere. :)

Original comment by zeb...@gmail.com on 13 Jun 2011 at 12:05

GoogleCodeExporter commented 8 years ago 
Tested mine this morning using Chrome 12.0.742.91 for Linux, and I am still 
having the same problem.  Still getting stuck on the OAuth "Redirecting" page.  
Whatever fix was implemented does not seem to have affected my OS/Browser 
combination.

Original comment by Jackie.R...@gmail.com on 13 Jun 2011 at 2:58

GoogleCodeExporter commented 8 years ago 
I was running an older version of Chrome, but have now updated to 12.0.742.91 
for XP and I'm still getting the same issue.

Original comment by rjs...@gmail.com on 14 Jun 2011 at 2:13

GoogleCodeExporter commented 8 years ago 
Yep, i also have a same problem. Can not sing in. I have Chrome 12. On 11 works 
perfect. Have a nice work dude. Anyway great job, keep going.

Original comment by krza...@gmail.com on 14 Jun 2011 at 5:58

GoogleCodeExporter commented 8 years ago 
Same Problem

Original comment by jonppou...@gmail.com on 15 Jun 2011 at 8:21

GoogleCodeExporter commented 8 years ago 
Same problem here. C'mon Google, get your ish together.

Original comment by jsch...@gmail.com on 16 Jun 2011 at 11:24

GoogleCodeExporter commented 8 years ago 
helpppppp
im having the same problem and chrome to phone is a must app for me.

Original comment by Theipodn...@gmail.com on 19 Jun 2011 at 6:31

GoogleCodeExporter commented 8 years ago 
same

Original comment by chengcho...@gmail.com on 19 Jun 2011 at 11:42

GoogleCodeExporter commented 8 years ago 
same here

Original comment by jorge3...@gmail.com on 22 Jun 2011 at 6:37

GoogleCodeExporter commented 8 years ago 
same here( very disappointing

Original comment by kel...@gmail.com on 29 Jun 2011 at 7:43

GoogleCodeExporter commented 8 years ago 
Was about to post a new issue on this, decided to search first.

Exact same problem, questioneer :

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 extention (on desktop)
2.Click on chrome to phone logo (on desktop)
3.Choose "sign in" (on desktop)

(desktop, win 7 64bit, chrome web browser version 12.0.742.112, chrome 
extention)

What is the expected output? What do you see instead?

Expected to 'connect' to phone 

Instead, a new tab opens (probably normal?), wich says "redirecting...", but 
never redirects... 
Tab title bar is "0Auth Redirect Page".

What version of the android, in Settings -> About phone -> Build number (ex. 
FRFxx ) ? If less than FRF50 - see the FAQ.
GRJ22

Is the phone using WiFi or mobile network when problem occurs ? If Wifi,are you 
behind a firewall that blocks outgoing connections ?
Yes, Wifi. No, no firewall blocking.

Can you open "Gmail" application ? Do you see new messages without hitting 
'refresh' ? Gmail application on phone works like a charm. Synced within 4 
seconds.

Can you open "Talk" application ? Do you see incoming chats ?

Talk application opens, seems normal behaviour (no chats, but not using talk 
for chatting anyway)

Please provide any additional information below.
No additional info.

Original comment by bas...@gmail.com on 30 Jun 2011 at 11:47

Attachments:

GoogleCodeExporter commented 8 years ago 
same problem, 
Win7 32bit, chrome 13.0.782.41 beta-m
Google Chrome to Phone Extension - Version: 2.3.0
android gingerbread.

Original comment by semire...@gmail.com on 2 Jul 2011 at 8:28

GoogleCodeExporter commented 8 years ago 
same problem, +1 
ArchLinux
Chromium 12.0.742.100 (0)
Android GingerBread

Original comment by greg...@gmail.com on 7 Jul 2011 at 11:13

GoogleCodeExporter commented 8 years ago 
Please answer the questions about build version and network, will save
developers a lot of time !

What steps will reproduce the problem?
1. Most likely, enabling 2 step verification for Google accounts, IN CHROME.
2.
3.

What is the expected output? What do you see instead?
When trying to sign-in, all I got is the new Oath tab with 'Redirecting'

What version of the android, in Settings -> About phone -> Build number 
(FRG83G, LG Optimus 2X, but the issue isn't in py phone.
ex. FRFxx ) ? If less than FRF50 - see the FAQ.

Is the phone using WiFi or mobile network when problem occurs ? If Wifi,
are you behind a firewall that blocks outgoing connections ?

Can you open "Gmail" application ? Do you see new messages without hitting
'refresh' ? No, gmail, Agenda, Docs, everything works as normal, in the Chrome 
browser and on the phone.

Can you open "Talk" application ? Do you see incoming chats ?
I do not use GTalk.

Please provide any additional information below.

I'm using two PC's at home, and at work. At work, the Chrome to phone works as 
supposed, the links are being sent right away. 
At home, I'm also use Windows XP, SP 3, with the latest Chrome installed. but, 
CTP (Chrome to phone) keeps redirecting me. I noticed, it started when I 
enabled the 2 steps protection for my accounts. Disabling this operation DOES 
NOT help. I've tried wiping Chrome from documents and users, local, application 
data DOES NOT HELP. re-installing the .apk, also DO NOT work.

I found on the net, the earlier versions: they work: the links are being sent, 
but, after restarting my home PC, I guess, Chrome is checking the latest 
available versions ot the installed extensions, and finally, CTP stops working.

It's really annoying for me, because I'm using EVERY day this applicatins, and 
IMHO, the alternatives are not as good.

Best regards and hope to have some news from you very soon,
Alex.

Original comment by alexc...@gmail.com on 10 Jul 2011 at 4:25

GoogleCodeExporter commented 8 years ago 
When I click the google to phone arrow it asks to sign in. When I attempt to 
sign in the page redirect forever...what's the issue Google?

Original comment by tragi...@gmail.com on 18 Jul 2011 at 2:31

GoogleCodeExporter commented 8 years ago 
same problem, +1 
ArchLinux
Chromium 12.0.742.124 (0)

installed fine. clicked from the new button in the toolbar. stuck at an "Oauht 
Redirect page" which just says 'Redirecting...'

Phone details aren't relevant. This is a desktop problem. Gmail, gtalk, docs 
and google+ work just fine.

But fwiw, all these work just fine on my gingerbread phone as well and the app 
installed fine there as well and allowed me to log in.

Original comment by honore.a...@gmail.com on 20 Jul 2011 at 1:59

GoogleCodeExporter commented 8 years ago 
In FoxToPhone 1.2 we are adding also the OAuth support, so all of you that are 
having problems, could take a minute to check if the current beta is working 
for you, read more at 
http://www.foxtophone.com/2011/07/introducing-foxtophone-1-2-still-in-beta/ and 
with your help we can try to find out if there's a problem with the 
authorization in your accounts or it's a problem related just to Chrome.

Original comment by aml...@gmail.com on 20 Jul 2011 at 4:17

GoogleCodeExporter commented 8 years ago 
I had the same issue, I uninstalled and reinstalled chrome, worked right away!

Original comment by engella...@gmail.com on 24 Jul 2011 at 4:01

GoogleCodeExporter commented 8 years ago 
uninstall and reinstalling chrome did not work for me

Original comment by dave.pas...@gmail.com on 25 Jul 2011 at 10:16

GoogleCodeExporter commented 8 years ago 
TLDR: check your time zone

Uninstalled then re-installed Chrome for the 5th or 6th time (I lost count).  
Still no go.

Went back to this thread to re-read previous posts, to make sure I didn't miss 
anything.  I read comment 6 (again), checked my time (for the nth time), then 
for some unknown reason, decided to check my time zone, and it was wrong.

After correcting the time zone and forcing an Internet Time update, it worked!

So my advice: don't just check to see if you have the right time -- make sure 
you have the right time zone!

Original comment by dave.pas...@gmail.com on 27 Jul 2011 at 8:20

GoogleCodeExporter commented 8 years ago 
Windows Vista Ultimate
Chrome 12.0.742.122

Same issue. Uninstalling & reinstalling didn't work. Time & time zone are 
correct.

Still getting stuck on OAuth redirect. Please resolve.

Original comment by monkeym...@gmail.com on 28 Jul 2011 at 1:43

GoogleCodeExporter commented 8 years ago 
If it's helpful, here my console output for the redirect page:

chrometophone.appspot.com/_ah/OAuthGetRequestToken?oauth_callback=chrome-extensi
on%3A%2F%2Foadboiipflhobonjjffjbfekfjcgkhco%2Foauth_interstitial.html%3Fchromeex
oauthcallback%3Dtrue&oauth_consumer_key=anonymous&oauth_nonce=0hZ2m&oauth_signat
ure=WkOzzPGRKAyQNfnwmSeHPxaoF0o%3D&oauth_signature_method=HMAC-SHA1&oauth_timest
amp=1311861344&scope=https%3A%2F%2Fchrometophone.appspot.com&xoauth_displayname=
Chrome%20To%20

PhoneFailed to load resource: the server responded with a status of 400 (Bad 
Request)
chrome_ex_oauth.js:526

Uncaught Error: Fetching request token failed. Status 400

Original comment by monkeym...@gmail.com on 28 Jul 2011 at 1:45

GoogleCodeExporter commented 8 years ago 
Issue 348 has been merged into this issue.

Original comment by aml...@gmail.com on 30 Jul 2011 at 3:28

GoogleCodeExporter commented 8 years ago 
Issue 347 has been merged into this issue.

Original comment by aml...@gmail.com on 30 Jul 2011 at 3:28

GoogleCodeExporter commented 8 years ago 
Issue 329 has been merged into this issue.

Original comment by aml...@gmail.com on 30 Jul 2011 at 3:31

GoogleCodeExporter commented 8 years ago 
Issue 331 has been merged into this issue.

Original comment by aml...@gmail.com on 30 Jul 2011 at 3:31

GoogleCodeExporter commented 8 years ago 
Issue 339 has been merged into this issue.

Original comment by aml...@gmail.com on 30 Jul 2011 at 3:32

GoogleCodeExporter commented 8 years ago 
Issue 322 has been merged into this issue.

Original comment by aml...@gmail.com on 30 Jul 2011 at 3:33

GoogleCodeExporter commented 8 years ago 
How about fixing this issue once you've finished merging the 432 threads about 
it?

Original comment by jsch...@gmail.com on 30 Jul 2011 at 3:58

GoogleCodeExporter commented 8 years ago 
As I said previously, the beta of Foxtophone now uses the same authentication 
system, so you can test it to check if that one works for you or not. If you 
aren't interested to test it, I'm sorry but I can't do anything else to help 
you

Original comment by aml...@gmail.com on 30 Jul 2011 at 9:04

GoogleCodeExporter commented 8 years ago 
I got the same problem after setting up the two-step verification with Google.

Original comment by johnnybo...@gmail.com on 1 Aug 2011 at 6:16

GoogleCodeExporter commented 8 years ago 
I'm having this same issue. I've just installed Foxtophone, and it does not 
work for me either ("There was an error sending: (status 0)"). I do not use 
two-step verification.

Original comment by jritt...@gmail.com on 3 Aug 2011 at 5:02

GoogleCodeExporter commented 8 years ago 
Re, comment 40.
That message means that you are using the stable version of FoxToPhone instead 
of the beta that uses OAuth. Both should work, specially the stable as people 
didn't seem to have problems with the old authentication.

That status 0 probably means that you can't connect to the chrometophone 
server, can you open https://chrometophone.appspot.com in the browser and check 
what it shows?
It should be just "Error: NOT_FOUND" in big letters. If it's something else, 
then the problem is that something is blocking your connection.

I'll try to verify this theory and add a connection test if possible.

Original comment by aml...@gmail.com on 3 Aug 2011 at 8:23

GoogleCodeExporter commented 8 years ago 
Issue 351 has been merged into this issue.

Original comment by aml...@gmail.com on 4 Aug 2011 at 3:10

GoogleCodeExporter commented 8 years ago 
I have the same issue with chrome v13.

here is the console error:

failed to load resource: the server responded with a status of 400 (Bad Request)

<a 
href="https://chrometophone.appspot.com/_ah/OAuthGetRequestToken?oauth_callback=
chrome-extension%3A%2F%2Foadboiipflhobonjjffjbfekfjcgkhco%2Foauth_interstitial.h
tml%3Fchromeexoauthcallback%3Dtrue&oauth_consumer_key=anonymous&oauth_nonce=A7Ku
X&oauth_signature=96O5aYKaNFxyec%2BQBfuS7e6F6zM%3D&oauth_signature_method=HMAC-S
HA1&oauth_timestamp=1312989896&scope=https%3A%2F%2Fchrometophone.appspot.com&xoa
uth_displayname=Chrome%20To%20Phone" class="console-message-url 
webkit-html-resource-link" 
title="https://chrometophone.appspot.com/_ah/OAuthGetRequestToken?oauth_callback
=chrome-extension%3A%2F%2Foadboiipflhobonjjffjbfekfjcgkhco%2Foauth_interstitial.
html%3Fchromeexoauthcallback%3Dtrue&oauth_consumer_key=anonymous&oauth_nonce=A7K
uX&oauth_signature=96O5aYKaNFxyec%2BQBfuS7e6F6zM%3D&oauth_signature_method=HMAC-
SHA1&oauth_timestamp=1312989896&scope=https%3A%2F%2Fchrometophone.appspot.com&xo
auth_displayname=Chrome%20To%20Phone" style="max-width: 100%; " line_number="0" 
preferred_panel="scripts">chrometophone.appspot.com/_ah/OAuthGetRequestToken?oau
th_callback=chrome-extension%3A%2F%2Foadboiipflhobonjjffjbfekfjcgkhco%2Foauth_in
terstitial.html%3Fchromeexoauthcallback%3Dtrue&oauth_consumer_key=anonymous&oaut
h_nonce=A7KuX&oauth_signature=96O5aYKaNFxyec%2BQBfuS7e6F6zM%3D&oauth_signature_m
ethod=HMAC-SHA1&oauth_timestamp=1312989896&scope=https%3A%2F%2Fchrometophone.app
spot.com&xoauth_displayname=Chrome%20To%20Phone</a>

Original comment by m...@masociete.info on 10 Aug 2011 at 3:18

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I am having the same problem what can I do.

Original comment by brianfue...@gmail.com on 12 Aug 2011 at 10:58

GoogleCodeExporter commented 8 years ago 
My PC's run Debian stable with both Firefox 5.0 and the developer build (15.0) 
of Chromium installed. My Android phone has the ChromeToPhone app installed.  
FoxToPhone works great but ChromeToPhone on the other hand has the same OAuth 
Redirect Page" with only content "Redirecting..." problem as described above.

Thank you for this great app and please let me know if there is anything I can 
do to help solve this issue.

Original comment by jpsha...@gmail.com on 12 Aug 2011 at 11:14

GoogleCodeExporter commented 8 years ago 
Issue 361 has been merged into this issue.

Original comment by aml...@gmail.com on 16 Aug 2011 at 5:51

GoogleCodeExporter commented 8 years ago 
having the same problem right now

Original comment by Disney.F...@gmail.com on 21 Aug 2011 at 4:44

GoogleCodeExporter commented 8 years ago 
As noticed by comment 7 and comment 28 it's important that your clock is set 
correctly. I've written a little test, you can check here 
http://alfonsoml.blogspot.com/2011/08/is-your-clock-adjusted-correctly.html at 
the "Testing time" paragraph you should get a red warning if there's a problem 
with your clock.

Original comment by aml...@gmail.com on 21 Aug 2011 at 2:34

GoogleCodeExporter commented 8 years ago 
http://alfonsoml.blogspot.com/2011/08/is-your-clock-adjusted-correctly.html 
have do the trick for me

Original comment by alcap...@gmail.com on 26 Aug 2011 at 9:27