Having some spotty internet connectivity lately (weather, and provider is doing some maintenance)... I've just noticed that if I try my pdc/launch Simulator dev cycle that the Simulator won't come up (hangs) if there's not a network connection (I expect it's trying to 'phone home' to see if there's an SDK update or something).
This is annoying, as if I can't brows the intarwebs etc. I might as well be developing - but the Simulator hangs!
I don't recall this being an issue before - or maybe I'm just remembering incorrectly.
Regardless, this seems like a bug... I'd expect a timeout of some sort, rather than just hanging (for what seems like?) forever.
I’ve timed it with the stopwatch on my phone - when it does this, it seems to then ‘time out’ at almost exactly 45 seconds.
This doesn’t happen all the time, but when it does happen it happens for quite some time - it’s like it’s trying to phone home (I’m assuming to check for SDK updates) on every startup, and for some reason if it doesn’t get a connection it keeps trying until it hits that 45 second limit.
I can understand checking for updates, but when it’s doing this constant delay in my build workflow is very, very frustrating.
I don’t know what is going on here. Do you have internet access when this happens? It should 1) be pretty much instant 2) timeout immediately if you don’t have internet access.
It’s not doing it right now… and usually doesn’t do it. But when it does it is for a ‘block of time’ - like, for a period of 15 minutes to an hour it’s constant, but then things ‘go back to normal’.
Can confirm that problem is real. I am living in the country that tend to block a lot of sites and ddos protection services, and simulator for sure hangs for like a minute when you run it. It not about NOT ABLE TO connect get connect to server, it about no loading WHOLE content of the server, in my case, I get like first 16 bytes and that it, it hangs because it waits when rests of the content will be delivered, but obviously it’s not going to be, that why time out hangs for longer than expected
I also just reproduced this in a case where my computer thought it was connected to the internet (ie was on a wifi network) but in fact all traffic was getting dropped. The simulator hung for a long time (I didn’t measure but at least 20-30 seconds) before opening.
This should be resolved in the 3.1 SDK. I’ve identified a network task that would run on launch that could block the main thread without internet access (but with an IP, etc).
It seems to be happening on at least 75% of launches today, even with an otherwise solid internet connection, so I don’t know if whatever you’re pinging is getting blocked by my ISP all of a sudden, or is otherwise having bad connectivity.
