I am trying to debug my javascript application while running on iPad Safari using Vorlon.
In the application HTML-code I have implemented the script link:
<script src="http://192.168.1.134:1337/vorlon.js"></script>
The IP is the IP of the Vorlon server, which is on my laptop. Running the app on the laptop - the same as the server is on - results in a new client connection in the Vorlon console. But on the iPad the app does not connect to the Vorlon server.
On my Galaxy Tablet the result is the same, no connection. No matter what browser. Tried Chrome and Firefox on the tablet.
I have checked the firewall on the laptop and made sure the 1337 port is allowed.
The laptop runs Ubuntu 17.04
Timothy was right. But to be a bit more exact: the WLAN router I got from my internet provider has a WLAN interface and four LAN interfaces. It turns out that nodes on the WLAN can not see each other, but they can see the machines connected to my LAN interfaces, like my NAS, my PC and the printer.
So the iPad - connected to the WLAN - is able to connect to the Vorlon-server on my PC and I now can start debugging.
Related
My websocket connection works:
When testing on localhost on Desktop Chrome, Desktop Safari, and iOS
When testing on production on Desktop Chrome and iOS.
It DOES NOT work:
When testing on production on Desktop Safari
There are no console errors in the browser. I can see the websocket is created, but it never fires "open" event on Desktop Safari. On the server side, the connection comes through fine everywhere other than from Desktop Safari, where I don't see anything come in.
The websocket is on the exact domain as the origin, and both are using secure connection (https/wss)
There are a lot of moving parts on production (e.g. load balancer). I've looked at and configured things like "stickiness" and TLS versions on each layer in production.
Again, it works most places.
I'm thinking there must be something like TLS, CORS, etc that I'm not fulling understanding that is causing the breakdown.
This is what happens on iOS (and about the same in Chrome desktop, etc):
This is what happens in Desktop Safari on Mac:
Well. After many hours of spinning my wheels I solved it:
There is a setting in AWS Load Balancer attributes called "Client port preservation". Once I checked this, websockets started to flow from Desktop Safari:
I have an Android device connected to a PC via USB.
The Android device is not connected to the network.
Is it possible to communicate between the Android device and a javascript web application running on internet explorer on the PC?
requirements:
We need to avoid installing anything new on the PCs, hunderds of PC are already deployed.
The Android devices are not deployed yet, we are free to add anything.
The WebApp will be running on Internet explorer, as per client's requirements.
I thought about using javascript web sockets on my web app on internet explorer (on PC) to listen to any incoming connection from the device, and then in my android app connect to that port and keeping the connection alive.
Is this possible? Are there other ways to do so?
I'm building a simple video conferencing system.
I'm using the following code as my base -> https://www.webrtc-experiment.com/video-conferencing/
It works perfectly on Windows and OSX, they can connect and chat with each other, but I cannot connect or see the video from an Android device.
I'm wondering what the best way of getting this working on Android so that an Android client and a Desktop client can chat together.
The android client seems to connect, but it just doesn't show the video to the PC user and vice versa.
Any help would be greatly appriciated!
I'm working on WebRTC using Visual Studio 2015 to create audio peer connection. It works fine when I deployed the solution on both Android and local machine (Microsoft Edge on PC), but on Windows phone has an error which said that RTCSessionDescription() is undefined. It occurs in adapter.js file.
Does WebRTC support on Windows Phone?
Note:
Edge on Windows phone version is 25.10586.0.0
Edge HTML on Windows phone version is 13.10586
The device is Lumia 730
I am having an unexpected result with my hybrid app(ionic framework) and the problem only replicates it self when i deploy the apk on an android phone. It works perfectly in a browser.
Is there a way i can see the logs when it is running on the phone? so i can try to understand what the problem is and where its coming from.
I have tried to run the app on my phone using ionic run android -l -c. But when i do that the app works perfectly like it does on the browser. i realised it basically just plugs itself to my local server and serves it on my phone from there (i alerted the index url. as an app it shows android_assets/www/index.html but when running with the above commant it shows http://192.168.XX.XXX/#/index)
How can i see logs when installed as an apk? Please Help
PS: im a newbie at ionic/AngularJS.
Here is a life saver for you and many others.
Install the app on the device.
Make sure you have USB debugging on on the real device.
On your desktop open Chrome, and in the URL address bar type
chrome://inspect
Here you'll be able to see the list of devices that are connected and are using WebView. Click on inspect and you will be able to use Chrome Dev Tools on your running APK.