chrome browser cast extension clashes with facebook javascript sdk

[GoogleCodeExporter]

What steps will reproduce the problem?
1. implement facebook javascript sdk as stated here 
https://developers.facebook.com/docs/javascript/quickstart with xfbml parsing 
enabled (default) on the same page which uses the cast sdk
2. make a proper chrome.cast.initialize() call
3. observe javascript console

What is the expected output? What do you see instead?
I see the following javascript error:
Received message of type object from 
chrome-extension://boadgeojelhgndaghljhdicfkmllpafd, expected a string

from http://connect.facebook.net/en_US/all.js line 56, column 219

What version of the product are you using? On what operating system?
newest versions. os is os x 10.9.1

Please provide any additional information below.
looks like this error is triggered by "messages" coming from the cast 
extension/chrome stick

Original issue reported on code.google.com by p...@zattoo.com on 20 Feb 2014 at 2:35

[GoogleCodeExporter]

We've just released a Cast extension beta.  See this announcement: 
https://plus.google.com/+ShawnShen/posts/aVXSHyceNbR.

With this beta extension, you can load Chrome sender SDK using script loading 
that might help you get around this issue.

  window['__onGCastApiAvailable'] = (function(loaded, errorInfo) {
    if (loaded) {
      this.init_();
    } else {
      this.appendMessage_(errorInfo);
    }
  }).bind(this);

Original comment by shawns...@google.com on 20 Feb 2014 at 10:10

• Changed state: Acknowledged

[GoogleCodeExporter]

the error persists in the beta using __onGCastApiAvailable but the issue has no 
visible impact for the beta/public cast api to my knowledge

Original comment by p...@zattoo.com on 21 Feb 2014 at 10:50

[GoogleCodeExporter]

So is this still an issue?

Original comment by anad...@google.com on 23 Feb 2014 at 1:24

• Changed state: NeedInfo

[GoogleCodeExporter]

the warning message is still appearing every time the cast api is communicating 
with the chromecast which makes logging confusing

Original comment by p...@zattoo.com on 24 Feb 2014 at 10:21

[GoogleCodeExporter]

as best I can figure, the FB script isn't checking the source of the messages 
that it's watching for, so it complains when it sees other messaging going on 
inside the webpage.  

Original comment by paul.vic...@gmail.com on 2 Mar 2014 at 7:09

[GoogleCodeExporter]

how is it possible that the facebook sdk receives messages from chromecast? 
isn't this a privacy problem?

Original comment by p...@zattoo.com on 3 Mar 2014 at 9:28

[GoogleCodeExporter]

Talking to our engineers, it seems to not be an issue on our side.

Original comment by anad...@google.com on 17 Mar 2014 at 7:57

[GoogleCodeExporter]

this is odd because after quick googling it looks like this issue is caused by 
chrome extensions only:
https://www.google.com/search?q=%22Received+message+of+type+object+from+*+expect
ed+a+string%22
but unfortunately there are no qualified investigations on this

Original comment by p...@zattoo.com on 17 Mar 2014 at 9:09

[GoogleCodeExporter]

hello,
do you have new insights on this?

Original comment by p...@zattoo.com on 6 May 2014 at 7:04

[GoogleCodeExporter]

I don't know if this is related or not, but it is work for me to communicate 
with SDK 
http://brianmayer.com/2012/12/building-a-chrome-extension-that-connects-to-a-fac
ebook-app/

Original comment by k...@vatih.com on 19 Jul 2014 at 6:00

[GoogleCodeExporter]

Original comment by anad...@google.com on 20 Jul 2014 at 10:29

• Changed state: NotSDK

[GoogleCodeExporter]

k...@vatih.com,
this is not related.

anad...@google.com,
the original issue is actually sdk related

Original comment by p...@zattoo.com on 21 Jul 2014 at 7:56