I have no solution, but it may lead you in the right direction.
The problem may be in the document document.location of the extension document. For javascript running in the extension area, the protocol is "chrome-extension: //", while many JS libraries expect either "http" or "https".
From looking at the next line in the jssdk file, it seems that FB also makes this assumption:
var k = typeof j == 'undefined' ? location.protocol.replace(':', '') : j ? 'https' : 'http';
Try debugging these cases by replacing the line above:
var k = 'http';
Hope this helps.
source share