Incomprehensible speedlock behavior needed to be fixed yesterday
Device: Pixel 2
OS: Android 10
App Version: 2.33.1
At this point, this is an old, tired issue, but to recap:
- Stop at Location A. Open Prime. Take some actions.
- Put Prime and device away.
- Stop at Location B, some distance away. Open Prime. Try to take some actions.
- Observe nonsensical error messages for minutes or hours(!) in the flavor of
Scanner communication error (1)and
The idea that legitimately traveling between two locations, coming to a stop, and being locked out due to some poorly communicated issue is beyond ridiculous. I cannot begin to describe how frustrating it is when the two locations are airports and the lockout lasts for hours.
So, I have a simple question:
What is the date and time (with timezone) when we can expect a release of Prime that resolves this issue?
<start snippy commentary>
Niantic: You're impeding and frustrating the gameplay of numerous, legitimate agents. Meanwhile, you're giving location spoofers free reign to do what they will. iBotPeaches tells one such story, and more elegantly than most: https://community.ingress.com/en/discussion/5328/the-bad-actor-darkness-return.
Take a step back. You're developing a location-based game. Your one job is to interpret the player's location in some reasonable fashion and to provide feedback accordingly. If after six? seven? years of experience across three games (Scanner [REDACTED], Pokémon GO, Harry Potter: Wizards Unite), this is still a problem in search of a solution, then an Insights post on the topic is in order. Walk us through the thought and engineering processes, in detail.