I'm currently going through the codelab Enable local fulfillment for smart home Actions. I managed to get (mostly) everything working.
But when I try to debug the typescript app Chrome using the Chrome Dev Tools (chrome://inspect/) I do sometimes see my Google Nest Mini to which the "local execution app" is deployed. But most of the times I do not. All my devices (Dev notebook and Google Nest Mini) are in the same IP subnet.
Any hints or ideas how to troubleshoot that?
The problem is solved. I cleared the list of " Target discovery settings", added the Google Nest Mini IP again and rebooted a few times. Since then it works always.
Related
I am writing an app in React in order to make a beautiful UI for my API. When I run it in Arch Linux's Firefox it works well. However, when I run it in my Android device, it seems like the initial API call (inside the useEffect of the App.js) is not done, not in Firefox neither in Chrome.
I am serving the app in the computer and then opening it with my local IP address (not localhost, obviously) with my phone.
Does anyone know why isn't that working in the phone even though it is working in my Linux machine?
The source code (of the UI and of the API) is in my Github (https://github.com/ToniIvars/Localdrive).
Thank you in advance.
I suffer a similar problem recently, may relate to unreachable IP address or some security problem.
I recommend using the chrome remote debug tool to make everything clear, in short that's how to do that:
First, open your phone debug mode, connect it to the PC with adb debug enable
Open chrome on your phone
Open chrome on your PC, go to 'chrome://inspect#devices'
Wait for a second and you should see your device, click inspect on it
Soon you can find out what cause the problem
Here's a full tutorial: https://developer.chrome.com/docs/devtools/remote-debugging/
Not sure where to go with this one as I am not sure if it is code related or something else. I have a working React Native app that works great on the simulator and also on the device when connected to the wifi or plugged into the Mac.
Now I have noticed that when I remove the device and place it on 4G/3G the app does not load and hangs on the loading screen. It may take a number of re-opens of the app before I can get it to run once. Funny thing is that at the minute the app only has the UI built so there are no calls to remote servers etc that may be causing it to hang.
Any ideas?
For iOs, in Xcode you can go Product > Scheme > Edit Scheme... > Run & set the Build Configuration to Release. Then run it on your device & it will be a release build that won't try to connect to your packager, but won't have the sometimes useful developer options at your disposal.
I used to have X3D-Edit 3.3 downloaded and working on my Netbeans IDE but I updated my laptop to Windows 10 and some of my files got deleted such as X3D-Edit and when I go onto https://savage.nps.edu/X3D-Edit/X3D-Edit.html, I get
This web page is not available
ERR_CONNECTION_TIMED_OUT
Google Chrome could not load the web page because savage.nps.edu took too long to respond. The website may be down or you may be experiencing issues with your Internet connection.
Check your Internet connection
Check any cables and reboot any routers, modems or other network devices you may be using.
Allow Chrome to access the network in your firewall or antivirus settings.
If it is already listed as a programme that is allowed to access the network, try removing it from the list and adding it again.
If you use a proxy server...
Check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server: Go to the Chrome menu > Settings > + Show advanced settings > Change proxy settings... > LAN Settings and deselect "Use a proxy server for your LAN".
I've tried that same site on two separate networks and I've tried it with and without a firewall. And I'm still getting the same problem, so I was wondering where I'd get X3D-Edit from?
Happy to announce that upgraded X3D-Edit 4.0 now available
https://savage.nps.edu/X3D-Edit/X3D-Edit.html
Update: installers and help video now available on SourceForge
https://sourceforge.net/projects/x3d/files
Downloadable zip includes runnable versions for Windows, Mac and Linux. Build environment is Apache NetBeans 12.6 and openjdk 19. Beta testing in progress, adding features and X3D4 nodes with special focus on validation, HTML5 integration and Web Audio API.
All test and usage reports welcome. Have fun with X3D4!
I'm hosting my website using Google App Engine. It's a pretty simple website, but I've got some javascript drawing to a canvas element, which I'm trying to test on my iPhone. I'd also like to take a crack at reworking my CSS for mobile. However, I can't access http://localhost:8080/ (which is the url that GoogleAppEngineLauncher spits out when I run the app locally) from my phone. This seems obvious.
Unfortunately, it seems that Mountain Lion has removed the web sharing preference from system preferences. I found at least two different sites with "solutions" for re-activating web sharing (Apache server?), but none of them seem to work in conjuction with Google App Engine... I also tried this preference pane, which also doesn't work. I keep getting "Safari cannot open the page because it could not connect to the server."
Sorry if this is a stupid question, I'm a relative noob to this stuff. Also, I see a lot of questions here on SO which seem related, but I think I'm still too uninitiated to understand how they're releated. Is there an extra step here that's GAE specific which I'm missing?
This isn't anything specific to your OS. By default, the App Engine dev server binds to the loopback interface, making it accessible only to your machine. If you want to access it from other machines, you need to pass the --address=0.0.0.0 flag to the dev server - which you can do in the launcher's preference pane.
As of March 2013 - the "address" argument has been renamed to "host" - (at least for Python version of the app engine)
--address=0.0.0.0 argument not working after upgrading to App Engine 1.7.6
I know there are a LOT of blog posts on this. But I can't seem to find an answer. I'm trying to debug an application that communicates with some services I have running locally. Right now, I have two services. One of them works. One of them does not. Both are running in http://localhost:90. To help me resolve this, I turned to Fiddler.
Oddly, Fiddler shows traffic in Internet Explorer in the emulator, but it does not show traffic from my application. With my application running, I launch Fiddler and nothing appears. I do not see any traffic. I have been able to confirm that I am successfully accessing the one service. However, no traffic appears in Fiddler. To see if Http traffic is running, I exited my Silverlight application and started Internet Explorer on the emulator. When I visit websites in IE on the emulator, I see traffic being written to Fiddler.
I'm totally confused. What am I doing wrong?
You need to actually configure Fiddler to be able to access localhost. Here is a workaround that needs to be done in the application.
Basically, what you need is the extra dot when accessing the location. So in your case it will be:
http://localhost.:90
Also, you might want to try some additional config settings.