"[Bug Fixed!] Ampersands in search queries no longer cause searches to run abysmally slow"

#PokemonGO: Seven months ago I reported a bug where search queries ran slower and slower the more ampersands you added. As an example, I provided the query 1&1&1&1&1&1&1&1&1 which is functionally equivalent to the search query 1 — it just shows you all Bulbasaur. Consequently, you would expect a query like 1&1&1&1&1&1&1&1&1 to run very fast. But as I reported at the time, running that query caused my phone to lock up for 66 seconds while it executed.I'm happy to report that as of the latest version, the search query 1&1&1&1&1&1&1&1&1 completes almost instantaneously on my phone. This is significant because (along with the newly added negation operator, !) excessive use of ampersands can be used to create very precise (albeit very long) "search" and "trash" strings. via /r/TheSilphRoad http://bit.ly/2RGJmUV