Google Apis explorer is not working in local development server and it is showing no error just a redirect.
INFO 2016-02-01 06:19:42,645 module.py:787] default: "GET
/_ah/api/explorer HTTP/1.1" 302 - INFO 2016-02-01 06:19:45,206
module.py:787] default: "GET
/ah/api/static/proxy.html?jsh=m%3B%2F%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.en_GB.mX-Sl4wQAT8.O%2Fm%3D__features__%2Fam%3DAQ%2Frt%3Dj%2Fd%3D1%2Ft%3Dzcms%2Frs%3DAGLTcCNc6PXZbysb_U3xKZFWCKbDMDUETg
HTTP/1.1" 200 7933 INFO 2016-02-01 06:19:52,044 module.py:787]
default: "GET
/ah/api/static/proxy.html?jsh=m%3B%2F%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.en_GB.mX-Sl4wQAT8.O%2Fm%3D__features__%2Fam%3DAQ%2Frt%3Dj%2Fd%3D1%2Ft%3Dzcms%2Frs%3DAGLTcCNc6PXZbysb_U3xKZFWCKbDMDUETg
HTTP/1.1" 200 7933
Im able to view discovery doc for my app also without error. I can make calls from javascript client to my apis but cannot see them on apis explorer. I was able to see them last day and in the morning gone.
The problem persists in all apps running in the development server.
Specs :-
1.9.31 - sdk version
python - language
mac-os x
I'm new to google cloud endpoints and I can't understand how to trace the issue. Any guidance would be appreciated. Thanks
Update : Workaround
The issue is unfortunately related to the latest release of Chrome. You probably need to launch a new testing Chrome profile with arguments --user-data-dir=test --unsafely-treat-insecure-origin-as-secure=http://localhost:8080 as suggested by google https://code.google.com/p/googleappengine/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log&groupby=&sort=&id=12713
To create a new chrome profile on mac-osx follow this link :
https://www.chromium.org/user-experience/user-data-directory
Something changed, and now you must start Chrome in a specific way to use api explorer on localhost development server
here is a link to info from google.
But for me it still didn't fix using api explorer with localhost dev server.
I find that a possible workaround is to launch Chrome with the flag "--allow-running-insecure-content"
On MacOs in terminal run this:
/Applications/Google\ Chrome.app/Contents/Mac/Google\ Chrome
--user-data-dir=test --allow-running-insecure-content
It worked for me
I'm also facing the same issue. After fiddling on the local machine, we've deployed the app and the API explorer is accessible via the remote host.
In order to access the API Explorer remotely, open the following link in your browser
https://your-app-id.appspot.com/_ah/api/explorer
This is a work around till there is a solution available
I think this will do the trick as google has also changed the documentation and red banner message:
The issue is unfortunately related to the latest release of Chrome. You probably need to launch a new testing Chrome profile with arguments --user-data-dir=test --unsafely-treat-insecure-origin-as-secure=http://localhost:8080 as suggested by google https://code.google.com/p/googleappengine/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log&groupby=&sort=&id=12713
To create a new chrome profile on mac-osx follow this link : https://www.chromium.org/user-experience/user-data-directory
Related
I am using version 6.24.3 of jxbrowser, and there is a problem when accessing https://mail.163.com. I can confirm that there is no problem with the website. I have checked the official jxbrowser documentation, but there is no gain. I hope to get an answer here
The following is the error message given by version 6.24.3 of jxbrowser；
This site can’t be reached
The webpage at https://mail.163.com/ might be temporarily down or it may have moved permanently to a new web address.
ERR_SPDY_INADEQUATE_TRANSPORT_SECURIT。
I want to confirm what causes this, and if there is a solution on this version?
Exception screenshot
I suppose it's because of the old Chromium 69 used by JxBrowser 6.24.3. It's possible that the website doesn't work in such an old Chromium version. I can recommend that you try JxBrowser 7.11 based on Chromium 79 and see if it helps.
Browserstack has discontinued its chrome extension for local app testing and has moved to a desktop app/.exe that you have to download to do local testing.
I can't seem to get this working running Windows 10 and I'm wondering if anyone else has had this problem and resolved it.
When I download and execute their desktop app, it tells me local testing is enabled:
https://imgur.com/a/2ey7N3U
When I then use Browserstack Live to test local development I get an error message saying local testing is not enabled and it gives me the option to download their desktop app, which I have and says local testing is enabled:
https://imgur.com/a/YMd0LOj
I have tried uninstalling and reinstalling the desktop app/.exe, it gives me the same results.
I've confirmed with our network team that I am not behind a proxy which is an option to manage the desktop app (under "advanced settings" in the first screenshot above).
Our network team has also whitelisted all traffic from (asterisk).browserstack.com (the actual asterisk character is stripped here) and they're telling me "Additionally I watched his traffic on the firewall as he tried to use the browserstack software and no traffic was blocked
I've also been in contact with browserstack support but have basically been feeding their responses to our network team and our network team's responses back to browserstack. At the end of the day, I still can't get local testing working.
Does anyone have any ideas what might be happening and how I can resolve it?
I encountered the same behavior while setting up Local Testing with the BrowserStack Local Desktop app that was released after the announcement by Google about the end of support for Chrome apps (Click here). However, I was able to set-up Local Testing post configuring the proxy server details as mentioned over here.
I would suggest checking with your IT team if traffic for *.browserstack.com is being routed via a specific proxy at your end and configuring the proxy details in the 'Advanced Settings' for the desktop app.
In case this doesn't work, do contact BrowserStack Support
I have installed ANT Media Server Community Edition on a Digital Ocean Droplet (the one-click app installation). Then I created serveral streams in the LiveApp and WebRTCApp sections underneath the Applications menu item.
Now when I broadcast from OBS on Windows, I see the broadcast indicator in the media server dashboard, for instance, status "Broadcasting 1.05x". But, when clicking the play-icon on the same stream, I get "Stream will start playing automatically when it is live"
The console logs
13:51:36.652 No stream found
13:51:40.421 VM52 webrtc_adaptor.js:1082 sent message:{"command":"getStreamInfo","streamId":"766637165500264948292465"}
13:51:40.440 play.html?name=766637165500264948292465&autoplay=true:265 error callback: "no_stream_exist"
13:51:44.252 VM51 fetch.stream.js:18 HEAD https://<domain>:5443/WebRTCApp/streams/766637165500264948292465_adaptive.m3u8 net::ERR_ABORTED 404
https://<domain>:5443/WebRTCApp/streams/766637165500264948292465.m3u8 net::ERR_ABORTED 404
https://<domain>:5443/WebRTCApp/streams/766637165500264948292465.mp4 net::ERR_ABORTED 404
I have the same results with the embed-code, with or without SSL and in either of the browsers Chrome, Edge and Firefox.
What can be the reason for this behavior?
I also experienced similar issues with the Community Edition. I noted the references in your console log to the WebRTCApp. After reviewing the Ant Media documentation I stumbled upon "WebRTC Playing is available only in Enterprise Edition(EE)". As you are using the Community Edition WebRTC this may be why it is not working. It might be best contact their support. I ended up Running the Enterprise Edition and it worked out of the box. If you use their example source player code note the websocket path is different in the enterprise version vs the community edition.
I am working on an iOS app that connects to a web service. For development and testing, we use Bonjour to find servers on the local network, and during sign-in the app offers to connect to one of them instead of the production site.
Since upgrading to El Capitan, I am unable to connect from the Simulator to a web server running on the same Mac. I am able to reproduce this issue using Simulated Mobile Safari and the web server that comes with the stock Python in OS X.
Open Terminal, start a web server: python -m SimpleHTTPServer 8000
Open Safari inside the Simulator, enter URL: http://my-computer-name.local.:8000/
Simulated Mobile Safari displays "Safari cannot open the page because it could not connect to the server."
Additionally, the following message appears in the Console each time I try to load the URL:
assertiond[____]: assertion failed: 15A284 13A340: assertiond + 13207 [28CC4371-F3F9-3578-9436-310B23A2C638]: 0x1
Other possibly relevant facts:
Desktop Safari is able to connect using the URL http://my-computer-name.local.:8000/
Real Mobile Safari (on an iOS device on the same network) is able to connect using the URL http://my-computer-name.local.:8000/
Simulated Mobile Safari is able to connect using the URL http://127.0.0.1:8000/ (I need it to work with the Bonjour provided hostname, though).
Simulated Mobile Safari is able to connect to another machine with an URL like http://other-computer.local.:8000/
I'm using Simulator Version 9.0 (SimulatorApp-620 CoreSimulator-179)
OS X El Capitan 10.11 (15A284)
Amusingly, searching the web for the UUID 28CC4371-F3F9-3578-9436-310B23A2C638 yields only a handful of job posts. (You can make $15 for fixing this bug!)
This does not appear to be related to App Transport Security. My app behaves this way when ATS is disabled.
Are you able to reproduce this problem? Am I missing something?
I worked the issue around by adding an entry to the local OSX /etc/hosts file:
Append your FQDN after "localhost":
127.0.0.1 localhost mymachine.mydomain.local
I'm trying to use the latest Google NaCl SDK. Following the instructions at https://developers.google.com/native-client/pepper18/devguide/tutorial
I downloaded the naclsdk tool from their site, ran update, and got a pepper_18 folder.
I set NACL_SDK_ROOT to the pepper_18 folder, went in to 'examples' and ran make. Everything seemed to compile just fine.
I started Chrome, looked in about: flags and about: plugins, and verified that NaCl is enabled. I installed the SDK Examples app (from: https://developers.google.com/native-client/pepper18/sdk/examples) and that works just fine.
Then I tried to run my locally built and hosted examples, going to http://localhost: 5301. The HTML loads fine but the NaCl content does not load. In the hello world examples, it says "Status: LOADING..." forever.
I double checked the HTTP server logs and I don't see any errors there. Is there another place I should be looking for logged errors?
Check for version mismatch
In Chrome navigate to about:version and check that the major version of Chrome is at least that of the Pepper version you used to build your examples.
Check the JavaScript console in Chrome for any errors
You can find it by clicking the wrench icon in the upper right-hand corner in Chrome and selecting Tools -> JavaScript Console.
Inspect the NaCl module for further information
In the JavaScript console, you can also inspect the embed element of the NaCl module. E.g., if the embed tag has id="nacl_module" you can inspect it by typing
theModule = document.getElementById('nacl_module');
theModule.lastError;
Check Chrome's output to stdout/stderr
On Mac or Linux start Chrome from the terminal and look at the output on the console. E.g., on the Mac, you'd typically go
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-nacl
On Windows, Chrome does not write to the terminal if started from a command prompt. For this reason you need to redirect stdout/stderr from Chrome by setting the environment variables NACLLOG, NACL_EXE_STDOUT, and NACL_EXE_STDERR. Point them to different files, e.g.,
NACLLOG = c:\my_project\nacl.log
NACL_EXE_STDOUT = c:\my_project\nacl_stdout.log
NACL_EXE_STDERR = c:\my_project\nacl_stderr.log
Then (re-)start Chrome (making sure these environment variables are in effect).
Connect a debugger
Instructions on using the debugging support (currently only 64-bit Windows and 64-bit Linux) are available at https://developers.google.com/native-client/pepper18/beta-docs/debugging.
Restarting Chrome means closing all windows
When developing for Native Client one often restarts Chrome. It is important to close all Chrome windows; otherwise it hasn't actually restarted.
I muddled through a few issues which I will document in case they help others:
Neglected to 'make' the examples (got a clue to make them from the asker's description).
Chrome would not let me run non-store chrome apps. Went to chrome://flags and enabled Native Client and Native Client GDB-based debugging.
The JavaScript console said the demo's nmf file under .../debug/ was missing. I changed the make config to build Debug instead of Release based on this.
Chrome console complained NativeClient: NaCl module load failed: ServiceRuntime: failed to start; NaCl's GDB debug stub requires --no-sandbox flag on Windows. See crbug…. Tried running Chrome from cmd with --no-sandbox. This results in an alert You are using an unsupported command-line flag: --nosandbox. Stability and security will suffer. The aforementioned error went away, but the examples still would not run - no UI.
Went back to chrome://flags and disabled Native Client GDB-based debugging.
Then most of the examples worked. The Google Drive demo complains Error: must be run as a packged app.
have you confirmed that you've run httpd.py from the examples folder? This script creates the localhost:5103 server that the apps can be ran from.
Also, what OS are you using?
~Main