Can I connect to a WebSocket server in 2021 using WatchOS and StarScream on a real device?
I found information that it is impossible to connect on a real device, but the information is old
Unfortunately, I can not check on a real device, but it works on a simulator!
You can connect to a websocket server with StarScream on real devices. The issue you mentioned is fixed.
But be aware, your watch should be connected with your paired iPhone which has active internet connection. Otherwise, your socket connection won't connect.
Related
First of, I can see on traffic coming through when I browse on my desktop.
I have set the IP in network settings along with the port but when I connect I do not get the do you want to connect this phone message from Charles.
I have:
deleted all certificates and tried to go to chls.pro/ssl but get no internet message and the certificate doesn't download.
tried ios and android both with the same result.
tried to manually add it to the access devices in Charles.
The only difference is from two weeks ago when I last did this successfully is the VPN I am on (I open the Charles before connecting to the VPN, to rule that out).
Any suggestions? I am going crazy!
There are various issues that can cause this issue: I collect here and you can verify each step to solve it: https://docs.proxyman.io/troubleshooting/my-ios-devices-couldnt-connect-to-proxyman-via-proxy
I would like to summarize:
Check if your Firewall is blocking all incoming traffic -> Turn it OFF
Stop all VPN app from your iOS device
Make sure your iOS devices and your macOS are in the same network.
Disclaimer: I create the Proxyman app, which is a modern version of Charles-Proxy. Hopefully it helps you resolve the problem.
I am trying to implement send messages from the apple watch to an MQTT server using the MQTT Paho client library.
I am able to send messages from the emulator to the server but I am receiving errors when I try to run the app on an actual watch.
I am getting an error saying that it has attempted to connect to the server 3 times followed by "Socket: 5 Err: -1 Ernno: 1 Operation not permitted".
BSD sockets are not supported on watchOS (though I'm not sure why they work in the simulator). In watchOS 6 you'll be able to use Network.framework, but there aren't any MQTT libraries written using that yet. (I've started my own but it isn't usable yet.)
I'm developing an iPhone app that connects to a server. For now, the server is running locally. In the iPhone simulator, I can connect to localhost and test it that way. However, this doesn't work running it on an actual device, because then localhost is the device itself.
Is there an easy way for the device to connect to the server running on the host computer? Or do I have to resort to putting the server somewhere else?
Rather than using localhost, replace that with your computer's IP address. That should work for both the simulator and device.
I bought an Bluetooth ELM327 to read codes out of my cars diagnostic ports
I connect to it via Bluetooth in windows and it makes a serial-over-bluetooth com port 4
which any application running on my windows will connect quite happily.
I then found a few apps for the iphone and android etc that connect to these ELM gadgets via WIFI and not Bluetooth (because for some reason you cannot pair to these devices of iphone)
Now obviously I can buy a WIFI enabled ELM327 - but it costs £130 and my Bluetooth one cost £15
So after reading about this a bit I found out that the WIFI enabled ones you connect up as ad-hoc network and the smartphone(iphone) app tenets in port 23 that relays normal serial commands.
So obviously in the WIFI enabled one there must be some processor that runs an nano-os with telnet and some rs-323 translators and not sure what else.
How, using Windows 7 will i be able to relay any incoming WIFI requests for Telnet port 23 to my COM 4 that is connected to my Bluetooth ELM327 ..
As this is surely all that is needed by the Smartphone app.
You dont have to connect using a Bluetooth library like suggested ... because you are already connected to the device and have COM4 exposed to you. SO all you have todo is use a telnet library and translate and handle the handshake then realy the infomation as serial data.
There's no feature built in to Windows (or any other platform I know of) for such a scenario.
It would be fairly straightforward however to write a program to listen on port 23 and open a bluetooth connection when connected to, and then forward the data received on each connection out onto the other.
For instance one could use my .NET library 32feet.NET (e.g. http://32feet.codeplex.com/wikipage?title=General%20Bluetooth%20Data%20Connections etc etc) along with TcpListener from the .NET framework class libraries.
I am experiencing a strange issue with connecting to my web server from my Iphone4.
I have an app that connects to my web serer and downloads a chunk of JSON. This works fine when i'm connected via WIFI, but fails through 3G. I don't think it's my app, as Safari also fails to retrieve any page on my web server when using 3G.
My web server has a fixed i.p and is running apache/Centos pretty fresh out of the box, I have not messed with the firewall or iptables settings.
The error obtained from the iphone is "The network connection was lost"
It feels like a firewall issue, but i have not explicitly denied any ips. Is there some aspect of a 3g connection that gets denied by default on Linux?
I realise this is all vague at this time, but does anyone have any wisdom to offer?
Many thanks in advance.
Here is a topic related to iphone connection loss through 3G cellular data whereas WiFi works fine, also giving the error "The network connection was lost"
Couple suggestions:
Ensure that your web server is
responding in a timely fashion. If
it is taking a little too much time,
the 3g connection might give up.
Check your web server logs and see if the connection is reaching
your web server at all, and if any
errors are being recorded. If so,
investigate.
There isn't anything special about a 3g connection wrt you web server. Only difference would be that it is less reliable or slower.
How are you actually trying to connect to your web server? When its over wifi you are local on your network and the name of the server will probably work. But when its over 3g its on the interwebs and will probably not respond to the name of the server.