Closed alexrrouse closed 11 years ago
Cool, I ran everything through a few latency tests and it looks like the timeout issue resolved itself.
I'm still not going to put a timeout on the first auth call because that should take as long as it needs to communicate with AppBlade. The second confirm call can still have a timeout, though.
@andrewtremblay @joe-goullaud Can you guys look over this.
I was getting a crash when a web request from Appblade would timeout. It looks like we never implemented the actual timeout method, just the Perform Selector for it.
Tested it by reducing the timeouts down to 5 second and then using the Network Link Conditioner to force a timeout.