Closed GoogleCodeExporter closed 9 years ago
Original comment by aml...@gmail.com
on 16 Aug 2011 at 5:51
Sorry for my English - I'm from Belarus :(
I have this problem too, and I think it's doesn't depend from Android phone
(HTC Desire, CyanogenMod 7 Nightly, Android 2.3.5). In place, where I work,
Chrome to Phone working correctly (Win 7, Chrome 13), but at my home (WinXP
SP2, Chrome 13)I have OAuth Redirect Page with Redirecting... on it, when I
trying to Log In :(
Original comment by karlsonb...@gmail.com
on 24 Aug 2011 at 5:59
Same problem here. Extension is installed on Chrome 14.0 and app on Android
2.3. I can log into and read every other Google page, app and extension BUT
this one. Help?
Original comment by LauraMSa...@gmail.com
on 1 Oct 2011 at 1:14
The decision is found. Time zones on the computer and phone should coincide.
Original comment by karlsonb...@gmail.com
on 8 Oct 2011 at 9:54
Same problem here. Stays on redirect page. Can't login.
Original comment by surround...@gmail.com
on 12 Oct 2011 at 4:01
The time zone on my phone and computer coincide, yet this continues to be a
problem. Can use every other Google app and extension but this one.
Original comment by LauraMSa...@gmail.com
on 12 Oct 2011 at 4:58
Hello,
Same problem for me. The time zone on my phone and computer coincide, yet this
continues to be a problem.
Could you help me ?
Original comment by kox0...@gmail.com
on 20 Oct 2011 at 1:08
I have the same issue, and I've tried every suggestion I've seen, to no avail.
Help!
Original comment by mdunsmor...@gmail.com
on 21 Oct 2011 at 3:18
This ticket has been closed as duplicate of ticket 319. If you're replying here
I'm not sure that you have really tried all the suggestions.
For example, does FoxToPhone work for you?
It uses the same authentication method, so if it works, then it can point to a
problem with your Chrome or a bug in the extension. If it fails, then it can be
something wrong in your computer or your account.
Original comment by aml...@gmail.com
on 21 Oct 2011 at 5:18
I got it fixed.. I had the wrong time on my laptop. Update to internet time!
Cheers!
Original comment by ffch...@gmail.com
on 16 Nov 2011 at 12:12
Same here, Windows 7 and chrome version 16.0.912.63 pairing with android 2.3.3.
Please fix, this is why I switched to android
Original comment by jda...@gmail.com
on 15 Dec 2011 at 2:40
Problem arises because of the browser, append to the label browser
--ignore-certificate-errors
Example: C:\Users\name\AppData\Local\Google\Chrome\Application\chrome.exe
--ignore-certificate-errors
P.S.: I apologize for my English, I'm from Russia ))
Original comment by zh.go...@gmail.com
on 30 Mar 2012 at 4:48
I had the same issue on my linux machine. I had some trouble syncing with
internet time and I never fixed it and had a work-around which included setting
the time zone to iceland. I changed it back to amsterdam (like my phone) and it
still didn't work. I then fixed my linux so that I automatically updated to
internet time (installed ntp and edited /etc/ntp.conf to dutch time server). I
tried it again and had no trouble. I tried the --ignore-certificate-errors but
it didn't work (maybe linux version of chrome doesn't have this option). If you
have this error make sure you are synced with internet time and that you have
the same time zone as your phone.
Original comment by samoverd...@gmail.com
on 10 Aug 2012 at 8:57
Here is a solution (what I did to fix it).
- Close all chrome windows.
- Adjust Date / Time, check time zone and then synchronize it with
time.windows.com
- Open Google Chrome or in my case, Chromium Dev-m (16.xx)
- Click the chrome to phone icon and sign in.
- Grant access and it should just work from here.
Hope it works for you all. Good luck.
Original comment by gerk...@gmail.com
on 16 Aug 2012 at 10:36
spread the words people!! this worked for me and i hope it will for many more
so yu know.. ctrl+c + ctrl+v ;D
Original comment by gerk...@gmail.com
on 16 Aug 2012 at 10:39
sooo i take it there is no hope then?because I am having the same problem
Original comment by shawnybo...@gmail.com
on 19 Jan 2013 at 8:40
Original issue reported on code.google.com by
samosagv...@gmail.com
on 13 Aug 2011 at 10:56