Serious pain trying to get some services to show up in api explorer

[Dewey Gaedcke]

I've literally spent 3 days trying to figure out what's wrong with my config and I can't get anything (other than that stupid red banner) to show up in api explorer.

Can someone please give me some hints?

Thx
D

[Lewis Rodgers]

I've had trouble getting the api explorer to show anything recently in chrome (on localhost). Firefox on the other hand will display it.

Also, I've noticed that sometimes it takes a minute for the services to show up when accessing the api explorer on appspot.

--

Lewis Rodgers    User Interface Designer lewis....@cloudsherpas.com direct: 404-850-6795   Cloud Sherpas is now part of Accenture. Learn More.

[John Taranu]

Hi Dewey,

If you're using the local development server, note that Google Chrome blocks access to the API explorer because it is served via http and not https.  To get around this:

1. Click on the little gray shield icon to the right of the browser's URL bar in the top-right corner
2. Click Load unsafe scripts
   

John

[Dewey Gaedcke]

Switching to Firefox worked......I have no idea why......actually, I suspect it's related to the OAuth config in Chrome.....

But I never could get Chrome to work.....and yes, I did enable "load unsafe scripts" for every one of my tests.....that made no difference...

But Firefox is working......go figure???

Thanks,
Dewey

[Dewey Gaedcke]

OK guys.....I finally found docs on how to get API-EXPLORER (AE) working with Chrome....

You have to start a separate Chrome session with some security features disabled.

This worked for me.....from the terminal (OSX) run this:

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=test --unsafely-treat-insecure-origin-as-secure=http://localhost:12080

you of course will have to change the port (and possibly your path to Chrome)

from this article:

https://developers.google.com/explorer-help/#hitting_local_api

This became necessary because as soon as I allowed Firefox to upgrade itself, AE stopped working in Firefox.....

[Lewis Rodgers]

Nice work Dewey, thank you for sharing!

On Tue, Feb 16, 2016 at 12:44 AM, Dewey Gaedcke <de...@pathoz.com> wrote:

OK guys.....I finally found docs on how to get API-EXPLORER working with Chrome....

You have to start a separate Chrome session with some security features disabled.

This worked for me.....from the terminal (OSX) run this:

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=test --unsafely-treat-insecure-origin-as-secure=http://localhost:12080

you of course will have to change the port (and possibly your path to Chrome)

from this article:

https://developers.google.com/explorer-help/#hitting_local_api

--

Lewis Rodgers    User Interface Designer lewis....@cloudsherpas.com direct: 404-850-6795

Two leaders, one vision: Cloud Sherpas is now part of Accenture. Learn more