Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Answering "move too fast" dialog #4356

Closed
Gurzeh opened this issue Aug 20, 2016 · 3 comments
Closed

Answering "move too fast" dialog #4356

Gurzeh opened this issue Aug 20, 2016 · 3 comments

Comments

@Gurzeh
Copy link
Contributor

Gurzeh commented Aug 20, 2016

Short Description

Quite interesting: After botting a while in some area 5km away, and waiting some reasonable (so I thought) time, I opened the leg application at home. Then I got the message "you're moving too fast" and I had to acknowledge I was the passenger.

related to #4004 especially: API (not this project directly)
Complete "non-essential" API request/response analysis (any remaining unknowns)

Possible solution

How is it possible to handle that, especially with teleportation which will always trigger that dialog.
I saw some discussion about it somewhere, but could not find it anymore?
The query (and what it is waiting) is in the packets exchanged. Does PokemonGo-Map has something about this?

How it would help others

anti ban

@net8q
Copy link
Contributor

net8q commented Aug 20, 2016

After checking MITM dump while triggering the warning in the app, there is no evidence of API call triggered by acknowledging the warning nor specific reference to the warning in the traffic dump , so it is client side only, except if you have specific info about this.

@glennvgastel
Copy link
Contributor

There are no API calls indeed. The warning you got on the app was because of an inaccurate GPS fix, causing you to move fast.

@mjmadsen
Copy link
Contributor

I'm going to agree with @net8q and @Calcyfer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants