2.0.2 has cross-frame request issues

[GoogleCodeExporter]

Account is/is not set up and chosen:
Android version:
Android device has/has not been rooted/modified:
Android device:
Carrier:
Country:
Version of android2cloud Android app:
The server I'm using:
The Google Account name that I logged in with:

What I am doing, step-by-step:

What I expect to see:

What I see:

Original issue reported on code.google.com by LyonsPa...@gmail.com on 7 Jan 2011 at 3:32

[GoogleCodeExporter]

Can confirm this issue. Chrome extension won't open links after a while. 
Disabling and re-enabling the extension seems to make it go again. Links remain 
as 'received=False' in the datastore. Console shows this:

2Unsafe JavaScript attempt to access frame with URL 
chrome-extension://hkelgkihphkegiaagbcgglfidabmgkgp/background.html from frame 
with URL 
http://talkgadget.google.com/talkgadget/d?token=AHRlWrp4mgfhxOeYRZpLJ7JxNyMpOjwM
m85Hdun1ISVDVSTqbnD0c09niNNM9nsqATiwBLiQ_aH_IUM70wpu60v2b6LOu0A8Qxkf4KOb7i1FFmtf
8HgOPeUvSZh4ucUz_s6mo1rpZHAx&xpc=%7B%22cn%22%3A%22tJ52hRsS6F%22%2C%22tp%22%3Anul
l%2C%22ppu%22%3A%22http%3A%2F%2Ftalkgadget.google.com%2Ftalkgadget%2Fxpc_blank%2
2%2C%22lpu%22%3A%22http%3A%2F%2Fandroid2cloud.appspot.com%2F_ah%2Fchannel%2Fxpc_
blank%22%7D. Domains, protocols and ports must match.
www.google.com/images/cleardot.gif?zx=2k4g9536ns3lFailed to load resource
functions.js:202Error (401): undefined
functions.js:202Error (401): undefined
functions.js:202Error (401): undefined
functions.js:202Error (401): undefined
functions.js:202Error (401): undefined
functions.js:202Error (401): undefined
functions.js:202Error (401): undefined
7functions.js:223
Object
functions.js:202Error (401): undefined
talkgadget.google.com/talkgadget/d?token=AHRlWrrS3RXG9dtHeDsbMn71NcXbMwXSUuo0vQS
5pSkHqPFkQeMKd2nU7oCEAIqNGLmZvNpS59e_N_IOOi4sTCmUHhdfOawpKENnWnRNZV7rPZ_HcXkzS1O
wQ5zYL3IlaoYDfMgMeLxo&xpc=%7B%22cn%22%3A%22E0X4OqKZyj%22%2C%22tp%22%3Anull%2C%22
ppu%22%3A%22http%3A%2F%2Ftalkgadget.google.com%2Ftalkgadget%2Fxpc_blank%22%2C%22
lpu%22%3A%22http%3A%2F%2Fandroid2cloud.appspot.com%2F_ah%2Fchannel%2Fxpc_blank%2
2%7DFailed to load resource
functions.js:223
Object

Followed by lots of errors like these:

Failed to load resource
cleardot.gifFailed to load resource
cleardot.gifFailed to load resource
functions.js:202Error (-1): undefined
cleardot.gifFailed to load resource
cleardot.gifFailed to load resource
cleardot.gifFailed to load resource
cleardot.gifFailed to load resource
talkgadget.google.com/talkgadget/dch/bind?VER=8&clid=B39BCCA56EC49D12&zd=qa&prop
=data&token=AHRlWrrfSXgy84jYPRJmmxADA-JVySA6ELHEpUg5OM-GxL2aM5KksXSLrkT_k1QHu-d5
0nFFiigVSrRl_Cv_2AtAsEP7SUbpHhdoKNAdrgElz0bHEIVna4Hh_Roz9vhx8n6Z9nVtwIdG&SID=105
D1F62E5EBDE4C&RID=66770&AID=1&zx=lnmpptui1hul&t=1Failed to load resource
talkgadget.google.com/talkgadget/dch/bind?VER=8&clid=B39BCCA56EC49D12&zd=qa&prop
=data&token=AHRlWrrfSXgy84jYPRJmmxADA-JVySA6ELHEpUg5OM-GxL2aM5KksXSLrkT_k1QHu-d5
0nFFiigVSrRl_Cv_2AtAsEP7SUbpHhdoKNAdrgElz0bHEIVna4Hh_Roz9vhx8n6Z9nVtwIdG&SID=105
D1F62E5EBDE4C&RID=66770&AID=2&zx=c3l22lvtdvtb&t=2Failed to load resource
talkgadget.google.com/talkgadget/dch/bind?VER=8&clid=B39BCCA56EC49D12&zd=qa&prop
=data&token=AHRlWrrfSXgy84jYPRJmmxADA-JVySA6ELHEpUg5OM-GxL2aM5KksXSLrkT_k1QHu-d5
0nFFiigVSrRl_Cv_2AtAsEP7SUbpHhdoKNAdrgElz0bHEIVna4Hh_Roz9vhx8n6Z9nVtwIdG&SID=105
D1F62E5EBDE4C&RID=66770&AID=3&zx=oocrw959sbie&t=3Failed to load resource
talkgadget.google.com/talkgadget/dch/bind?VER=8&clid=B39BCCA56EC49D12&zd=qa&prop
=data&token=AHRlWrrfSXgy84jYPRJmmxADA-JVySA6ELHEpUg5OM-GxL2aM5KksXSLrkT_k1QHu-d5
0nFFiigVSrRl_Cv_2AtAsEP7SUbpHhdoKNAdrgElz0bHEIVna4Hh_Roz9vhx8n6Z9nVtwIdG&RID=rpc
&SID=105D1F62E5EBDE4C&CI=0&AID=1&TYPE=xmlhttp&zx=o87vjluygvvx&t=1Failed to load 
resource

Feel free to contact me by mail or on Twitter (@Steltek) if you want me to look 
at anything in particular.

Original comment by lev.ar...@gmail.com on 7 Jan 2011 at 5:17

[GoogleCodeExporter]

Unfortunately, I think this is an issue caused by Google's Channel API. I'm not 
100% positive on that, but I'm fairly certain. I'm going to talk to Moishe, the 
guy behind the Channel API, and make sure everything's ok. This may take a much 
longer time to fix-- think weeks to months-- because it may necessitate 
changing Google's code. I'll do my best.

In the meantime, going to chrome://extensions and clicking the Reload link 
under android2cloud should fix the error. It seems to be a touch and go kind of 
thing.

Original comment by foran.pa...@gmail.com on 7 Jan 2011 at 9:34

• Changed title: 2.0.2 has cross-frame request issues
• Changed state: Investigating

[GoogleCodeExporter]

Just DL Android2Cloud. Went thru entire set up and the links just never get to 
the Chrome Browser. I tried sending the link in both the silent sending and 
regular sending with no success. Links never reach Chrome Browser. 
Thanks for your hard work,
Vinny

Original comment by LyonsPa...@gmail.com on 10 Feb 2011 at 3:22

[GoogleCodeExporter]

Not sure if this is relevant. Android2cloud 2.0.4 still gets stuck. This is 
what the console shows:

GET 
http://talkgadget.google.com/talkgadget/dch/bind?VER=8&clid=1C2108706EC49D12&gse
ssionid=PpWsPHsDK9jr7bvO8crrcA&prop=data&token=AHRlWrp021Llj8Kva-vU49dP_dstQHVoR
PNeR8MVVWT_zBtDpLgxRBmEyOxWZHigGe654K6CqGnb9vWohdU8zFUdb9azuvlTl63W0uhtJujcF3wuc
K1FpiJBJeCcFH-z0u9Z81ceveFA&RID=rpc&SID=9E3E587F27BD82DF&CI=0&AID=318&TYPE=xmlht
tp&zx=68sg1d2cfl6l&t=1 401 (Token timed out.)
bindGET 
http://talkgadget.google.com/talkgadget/dch/bind?VER=8&clid=1C2108706EC49D12&gse
ssionid=PpWsPHsDK9jr7bvO8crrcA&prop=data&token=AHRlWrp021Llj8Kva-vU49dP_dstQHVoR
PNeR8MVVWT_zBtDpLgxRBmEyOxWZHigGe654K6CqGnb9vWohdU8zFUdb9azuvlTl63W0uhtJujcF3wuc
K1FpiJBJeCcFH-z0u9Z81ceveFA&RID=rpc&SID=9E3E587F27BD82DF&CI=0&AID=318&TYPE=xmlht
tp&zx=68sg1d2cfl6l&t=1 401 (Token timed out.)
2Unsafe JavaScript attempt to access frame with URL 
chrome-extension://oifbcajohagkhnpkjjiniojjcaakmhda/background.html from frame 
with URL 
http://talkgadget.google.com/talkgadget/d?token=AHRlWrp021Llj8Kva-vU49dP_dstQHVo
RPNeR8MVVWT_zBtDpLgxRBmEyOxWZHigGe654K6CqGnb9vWohdU8zFUdb9azuvlTl63W0uhtJujcF3wu
cK1FpiJBJeCcFH-z0u9Z81ceveFA&xpc=%7B%22cn%22%3A%222RDbWsuzVd%22%2C%22tp%22%3Anul
l%7D. Domains, protocols and ports must match.
www.google.com/images/cleardot.gif?zx=j1h9346o5q3sGET 
http://www.google.com/images/cleardot.gif?zx=j1h9346o5q3s undefined (undefined)
functions.js:196Error (401): undefined
functions.js:196Error (401): undefined
2functions.js:218
Object
Channel: function (a){this.lc=a}
Socket: function 
(a,b,c,d,e){this.readyState=0;this.Qa=[];this.onopen=b.onopen;this.onmessage=b.o
nmessage;this.onerror=b.onerror;this.onclose=b.onclose;this.K=c||new 
Fd(a,"/_ah/channel/xpc_blank");this.qa=c?d:"wcs-iframe";this.vb=e||new 
Jd(a);document.body||h("document.body is not defined -- do not create socket 
from script in 
<head>.");Cd(this.K,document.body);Bc(this.K,"opened",y(this.$b,this));Bc(this.K
,"onMessage",y(this.Zb,this));Bc(this.K,"onError",y(this.Yb,this));Bc(this.K,"on
Closed",y(this.Ab,
__proto__: Object
functions.js:196Error (401): undefined
talkgadget.google.com/talkgadget/d?token=AHRlWrrIaz5stRyPkGl9ZJb40ZmfXRoPvcys6tk
QVdIQ80AgORI0oD2PDuxwGDbEtZZeYS9XnYf1bQBlarQA1w62jA5SZLKs5hRLvY3Er4S8rLVAt1p_R9I
DH-WxAS539Tnzh2ZKvljl&xpc=%7B%22cn%22%3A%22x551K7VgKm%22%2C%22tp%22%3Anull%7DGET

http://talkgadget.google.com/talkgadget/d?token=AHRlWrrIaz5stRyPkGl9ZJb40ZmfXRoP
vcys6tkQVdIQ80AgORI0oD2PDuxwGDbEtZZeYS9XnYf1bQBlarQA1w62jA5SZLKs5hRLvY3Er4S8rLVA
t1p_R9IDH-WxAS539Tnzh2ZKvljl&xpc=%7B%22cn%22%3A%22x551K7VgKm%22%2C%22tp%22%3Anul
l%7D undefined (undefined)
functions.js:218
Object

Original comment by lev.ar...@gmail.com on 1 Mar 2011 at 8:24

[GoogleCodeExporter]

I've let Moishe, the Google developer behind the Channels API, know about the 
issue. He's promised to keep me informed as they try to hunt down the cause and 
fix it. As it's not my code, there's very little I can actually do about it. 
I'm still examining a few things, but I'm not too hopeful. This is something we 
can only hold tight and wait for Google to fix.

Sorry. :( Wish I had better news.

Original comment by foran.pa...@gmail.com on 1 Mar 2011 at 9:03

[GoogleCodeExporter]

Recent investigations have shown that the Channel API (what connects our 
extension to our server) throws this error when some extensions are run. I'm 
not sure what extensions cause this issue, nor what property they have that 
causes this issue, but I'm working to isolate the problem.

Original comment by foran.pa...@gmail.com on 6 Jul 2011 at 4:27

[GoogleCodeExporter]

This issue has gone away since installing the latest beta.

Original comment by lev.ar...@gmail.com on 6 Aug 2011 at 6:12

[GoogleCodeExporter]

Thanks for the confirmation. :)

Original comment by foran.pa...@gmail.com on 6 Aug 2011 at 6:13

• Changed state: Fixed