Linkedin HTTPS error

Wed Jul 23, 2014 7:45 pm

Hello - my LinkedIn plugin from Appery was working fine until a few days ago. If I'm logged in to LinkedIn from elsewhere, there are no issues. If I'm not, the console logs the following error:

Uncaught SecurityError: Blocked a frame with origin "http://appery.io" from accessing a frame with origin "https://www.linkedin.com". The frame requesting access has a protocol of "http", the frame being accessed has a protocol of "https". Protocols must match.

Is there a way to fix this or set the Appery site to use the https protocol on mobile preview?

Wed Jul 23, 2014 8:47 pm

Hello Anton,

Could you please provide us with screenshot of error and steps to reproduce it?

Wed Jul 23, 2014 9:09 pm

Sure - I just made a fresh new app, imported the LinkedIn plugin, filled out my api keys, and tested the plugin to get the error. This was working a few days ago.

Wed Jul 23, 2014 9:12 pm

Sure - I just made a fresh new app, imported the LinkedIn plugin, filled out my api keys, and tested the plugin to get the error. The console logs this error when trying to open the LinkedIn login window. In the standard plugin LINKEDIN_api.js code:

performPoll = function(popup) {
var pollForUrl = function() {
var url = popup.location.href; <--- this throws the error
var result = checkPopup(url, popup);
if (result) {
clearInterval(handle);
retreiveToken(result.code);
}

Thu Jul 24, 2014 6:57 am

Hi Anton,

This should work.
Could you please share the app with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a or post a public link?

Sun Jul 27, 2014 2:45 pm

I just shared the app called LINKEDIN_PLUGI_TEST. When not signed in to LinkedIn already, clicking the Login button opens a new window to enter my credentials but also throws the error as described above. This is the default linkedin plugin with nothing modified except my api key and secret code.

Sun Jul 27, 2014 3:28 pm

Hi Anton - we see your shared app, we'll take a look.

Wed Jul 30, 2014 10:27 am

Hello Anton,

Sorry for delay. We tested your app, you may not pay attention to the error. The error is not critical. In a hybrid application they shouldn't appear at all, only in the browser

Thu Jul 31, 2014 1:08 am

Perfect, thank you. I did notice it ran fine on my Android phone as well.

Thu Nov 05, 2015 12:38 am

I am having this same issue with my app. --The frame requesting access has a protocol of "http", the frame being accessed has a protocol of "https". Protocols must match.--
I do not see this issue resolved and I do not see a useful solution to it here. Why leave these things posted forever if they are unresolved and no one is working on the issue or giving a complete solution? It serves no purpose and only confuses the user community searching for answers.