Open GoogleCodeExporter opened 8 years ago
I found that this problem only happens when signed with multiple Gmail accounts.
Original comment by eug.bara...@gmail.com
on 7 Sep 2010 at 6:58
How many accounts ? Haven't seen this - looks like a bug on google auth ( or
chrome too small max URI len), we may be able to fix this by switching to OAuth
and not using the browser cookies.
Original comment by cos...@google.com
on 7 Sep 2010 at 7:17
When I created this issue I had three accounts (one default on two linked --
maximum allowed by Google).
But I just tried:
1. Signed out in Chrome to Phone extension;
2. Linked another account in GMail (so I have two now in total);
Tried to sign in Chrome to Phone extension as got the same "Request-URI Too
Large" error message.
Original comment by eug.bara...@gmail.com
on 7 Sep 2010 at 7:36
Yes I confirm. At work I have no problem because I'm logged in to only one
address. At home I'm logged in to two addresses and I can't login to Chrome
to phone.
Original comment by damien...@gmail.com
on 7 Sep 2010 at 11:11
Yes, the possible fixes are to use OAuth or have the auth done without using
cookies - not sure if extensions can do this. Both fixes will also solve the
problem of multiple accounts.
I can take this, but I'm pretty short on time.
Original comment by costin
on 9 Sep 2010 at 6:31
I have just cleared browser history and was finally able to sign in and send a
page. When trying to sign in the account offered was not the one currently
logged in so clearly was logged in "twice" in the background. Used the correct
log in and all was sorted.
N
Original comment by neville...@gmail.com
on 18 Dec 2010 at 8:13
I get the same "Request-URI Too Large" message. I've tried clearing browser
history and logging out of all google accounts (and disassociating my other
gmail account from my main one) but none of this has helped.
Original comment by mjc1...@gmail.com
on 2 Jan 2011 at 8:44
I too have this problem. I am logged into both of my gmail accounts, and I
can't get this working either - just wondering if this is being worked on.
Original comment by ber.fa...@gmail.com
on 16 Jan 2011 at 5:49
I have always used a few accounts. This error has just started, so I can only
imagine it is a new bug that should be fixed.
Original comment by Mark.Che...@gmail.com
on 13 Feb 2011 at 9:57
Original issue reported on code.google.com by
eug.bara...@gmail.com
on 12 Aug 2010 at 11:12Attachments: