I'm pretty sure the answer is Yes to both of those questions, but I'm not 100%. Would rather not post the URL publicly, can I email it to you at the address in your post? Thanks!

I was trying it with NSURLSessionWebSocketTask on WatchOS. Looks like NWConnection isn't available in Objective-C. Would this work the same? NSURL * url = [NSURL URLWithString:@"wss://domain.com:443"]; NSURLSessionConfiguration *conf = [NSURLSessionConfiguration defaultSessionConfiguration]; NSURLSession * URLSession = [NSURLSession sessionWithConfiguration:conf delegate:self delegateQueue:nil]; webSocketTask = [URLSession webSocketTaskWithURL:url]; [webSocketTask resume];

I was able to connect to 'wss://echo.websocket.org' in my WatchOS app and send/receive messages with the code above. What is different about my website that it's not letting me connect? Thanks

I'm not doing audio streaming. I understand I can't do low level network programming on WatchOS, but the post you linked to said to use NSURLSession, which is what I'm trying to use. I was able to get it to communicate with the test server URL I posted, but what is different about my server that it's not allowing the connection? Thanks

Thanks for explaining, that saved me a lot of time debugging something that was never going to work. Is there any reason Apple hasn't added more robust networking to WatchKit? Either full fledged WebSockets and/or regular Sockets would make a world of difference. Our app is severely stifled by having to route our data through our iPhone app, both in terms of unusable performance and the fact that we can't make a standalone Watch app without it. We have so many cool features that we have been wanting to add since WatchOS 1 that still aren't possible because of the lack of sockets. Keeping my fingers crossed for WWDC 2021. 🤞🏻 Thanks for your help!

This is what it looks like. I'm running it in Portrait

Any updates on this? Been dealing with it for years. Every time I press a key there is a .5-1 second delay. Impossible to code like this!! Come on Apple, fix this please!

The javascript response I get when I add the image is: { "errors" : [ { "id" : "778abcb3-8491-443e-000c-c42366e703d0", "status" : "409", "code" : "STATE_ERROR", "title" : "The request cannot be fulfilled because of the state of another resource.", "detail" : "Screenshot Set with type APP_WATCH_SERIES_3 Already Exists!" } ] } Not sure what that means, I don't have any Apple Watch screen shots in the update.

I do both, but for testing purposes I am just running this: NSString* results = [NSString stringWithContentsOfURL:[NSURL URLWithString:@"https://google.com"] encoding: NSStringEncodingConversionAllowLossy error: nil]; NSLog(@"Content: %@", results); It works in the simulator and in OS 8, but not on my physical watch. Is there anything I need to add to my .plist file like I do for iOS? Thanks

Thanks. Doesn't look like there has been any resolution yet? Do we think this is a bug or Apple removed this functionality? Mine is also failing just loading regular URLs, not even using WebSockets

I already tried, ActivityKit is not available for WatchKit, just wondering if there is another way to do it.