I have 2 apps that have been running fine. Did a rebuild this evening and all network.request calls timeout now on both. I can browse with Chrome and hit everything I try. Running the app from the simulator works fine so it appears to be pointing to something within the build.
Still happening. It works fine in the simulator. The problem is when it is on the device. I can browse in chrome, so I was able to rule out a physical device error. I can hit the url browsing from my iphone, so it is either something in the apk or somehow a specific url is being blocked on multiple devices (though not all) by my network. I made my iphone a hotspot, and attached the 2 devices to it, and the calls went through, though that brought up an interesting caching problem (which I solved by brute forcing the url).
I have a call into Comcast to see if they are blocking a mac address/url combinaton in the router.
Thanks for your help, Rob. This was a strange one. Long story short - it started with a wild-card A record in our DNS, redirecting to a dead IP address and ended being something in the wifi router blocking the site, affecting only mobile devices.
Hi, same thing for me. Now in my app (on the store) all request are always wrong (not with chrome)… are you really sure that networks calls don’t get routed through your servers ? Any ideas ?
Still happening. It works fine in the simulator. The problem is when it is on the device. I can browse in chrome, so I was able to rule out a physical device error. I can hit the url browsing from my iphone, so it is either something in the apk or somehow a specific url is being blocked on multiple devices (though not all) by my network. I made my iphone a hotspot, and attached the 2 devices to it, and the calls went through, though that brought up an interesting caching problem (which I solved by brute forcing the url).
I have a call into Comcast to see if they are blocking a mac address/url combinaton in the router.
Thanks for your help, Rob. This was a strange one. Long story short - it started with a wild-card A record in our DNS, redirecting to a dead IP address and ended being something in the wifi router blocking the site, affecting only mobile devices.
Hi, same thing for me. Now in my app (on the store) all request are always wrong (not with chrome)… are you really sure that networks calls don’t get routed through your servers ? Any ideas ?