Salesforce web_accessible_resources manifest key

[Paul Q]

So are you suggesting changing the url to developer.force? Sandbox logins go through test.salesforce?? I didnt have any issues when i tested the service, it returned the correct json, it just the data wouldnt display in the page (control didnt even appear). Is there any way i can just let you into my appery set up?

[maxkatz]

Maybe it's the right URL, but I'm not able to sign in to test why the service is not working.

When I run my app, my URL is this: https://login.salesforce.com/

[Paul Q]

That's used for production environments and the free trial version rather than sandbox development orgs. If its any help this is the message iget when clicking on the Invalid GET on the network tab:

Request URL:chrome-extension://invalid/
Request Headersview parsed
GET chrome-extension://invalid/ HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.66 Safari/537.36

[Paul Q]

also getting this error in chrome developer tools:

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

[maxkatz]

Do I need to be added to your organization to be able to login?

I don't think those errors causing the service not to invoke.

Do you see any red entries in Network tab? Specifically, the one where you invoke the service.

[Paul Q]

No, couldnt see any. Could we do a GoToMeeting?

[maxkatz]

If the service is invoked, there will be a line in Network tab for that request. Do you see it at all?

I'm traveling this week... so doing GoToMeeting won't be easy.

Another thing. if you can find out how we can sign in into your app, that would also help.

[Paul Q]

can provide a login, do you have a private email? slightly concerned about posting the info on a public board...

[maxkatz]

Yes, send it to a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a and tell us how to reproduce the problem.