[bug] Encounter failed with result: ENCOUNTER_NOT_FOUND

[Casual-User]

Description: Multiple occurrences: Found pokemon X results in failed encounter for reason of 'ENCOUNTER_NOT_FOUND'

Steps to reproduce:

all my bots show this behavior since some hours

Stacktrace (If it's a crash): no further info given in stacktrace. Even those pokemon that have not already been caught are out of a sudden not found anymore.

Version: precompiled built alpha.4

Operating System: MacOSX

Java version: recent

[Arihiza]

This happened to me when my GPS cords were in the ocean... when I changed back to land it was fine again. 0.4.3

[Casual-User]

Hm, plausible, but I didn't change my GPS coords – so definitely not ocean for me ;-)

[Venome]

yeah it happen to me after i run it around 15 - 30 minutes

[langerhans]

Does that still happen on the latest versions? If not, please close here. Thanks :)

[Mixone-FinallyHere]

this is normal though it happens in the real app too sometime the pokemon disappears like that (this is supposed to happen if you take too long I think and make it more realistic) in the bot it logs found and starts the process of catch the moment it appears on map, but if it was busy on concurrent threads, so a catch at the same time or something like that, it might just happen that when it starts the catch process of the pokemon it already found, the pokemon is no longer there so it is NOT_FOUND