search

remulasce / metroapp

Realtime arrival notification utility for LA Metro
2 stars 0 forks source link

IOS: requestStatusTrip is all #213

Closed nighelles closed 9 years ago

nighelles commented 9 years ago

I get a requestStatusTrip, present a loading beachball, and then that's it. I never get a multiArrivalTrip from the SRDA

remulasce commented 9 years ago

Suggest you try debugging. On Apr 22, 2015 3:32 PM, "Nighelles David" notifications@github.com wrote:

I get a requestStatusTrip, present a loading beachball, and then that's it. I never get a multiArrivalTrip from the SRDA

— Reply to this email directly or view it on GitHub https://github.com/remulasce/metroapp/issues/213.

nighelles commented 9 years ago

Ugh, TCP snooping claims that we're getting no response from the server to the request sent from the ios app.

-Nighelles

nighelles commented 9 years ago

Ok, what the hell? The server responded to a different request from the app like 30 s later. Is there a difference between one request and the next?

nighelles commented 9 years ago

Status trip thing didn't disappear when we got an update, and also we only have like one XML response from like 5 min of running the app on the snooper. What's up with that, org.internet.whatever

nighelles commented 9 years ago

So it looks like the GET requests are getting out fine, but there's no response from the network. Which is odd, cause doing the same GET request that wireshark says the ios version is sending in chrome gives the intended XML. So WTF? Did nextbus intentionally cripple this particular thing? Lol.

nighelles commented 9 years ago

Now it looks like old working code won't return good network on the ios simulator either, though it's still working on my phone. Did nextbus actually change something?

nighelles commented 9 years ago

Lol, ok, now it's working. It was apparently a problem with the network adapter in the IOS SIMULATOR.

Issue closed.