Page 1 of 1

Capturing zones not always working

Posted: 18 Aug 2012 14:30
by Redman684
I've now captured 6 zones, but 2 of them didn't register.
I enter a zone, the bar fills green and the zone is captured. But also a screen "capturing zone, please hold" appears.
Hold what? Hold, as in "don't close the app"? Or hold your position and don't leave the zone? Hold a button? Wait until the server has been contacted (which is impossible as I don't have a data plan on my mobile) Wait until all wifi networks in the area have been scanned? Hold your breath?
Anyway, it doesn't seem to matter if you ignore this message, there is a hide button, but the message will re-appear after 10 seconds (very annoying)

I've had 2 zones where when I left the zone after the bar filled completely, still the "leaving zone" message sounded.
That's the only difference Ive notice between the zones that did register and the zones that didn't.

What goes wrong here?

Re: Capturing zones not always working

Posted: 19 Aug 2012 22:29
by Arthemax
The app needs to contact the server to notify it that you have taken the zone. It's not yours until the server knows. Therefore, you'll need a data plan or have access to a WiFi-network in the area where you capture zones.

The message "capturing zone, please hold" appears between the time the app tries to contact the server until the server responds with a confirmation that the zone is taken. However, if the server is notified without being able to reply that the zone is indeed taken, the app will keep waiting for confirmation from the server indefinitely. Obviously, that is annoying. If you restart the app, it will contact the server and see that the zone was indeed taken, and hopefully stop giving you the message.
Also, if you feel pretty sure that the app successfully notified the server, you can go and take the next zone, because then the app will be notified when it contacts the server about the next zone capture.

Re: Capturing zones not always working

Posted: 09 Feb 2013 09:27
by TBIT
This issue has been corrected. If it happens repeatably again, please file an issue at http://issues.turfgame.com/

Thanks!