-
Notifications
You must be signed in to change notification settings - Fork 120
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
GetMapObjects cells contain no forts or pokemon #68
Comments
Hi, did they change their API ? |
looks like it. Few other repos are also reporting issues mchristopher/PokemonGo-DesktopMap#621 |
As I said in https://github.com/PokemonGoF/PokemonGo-Bot-Desktop/issues/65
|
What does it mean, change API? Why cant this app simply be updated to the new API (whatever that is)? |
@obamaphone most of these apps are using a third-party API which has been put together by reverse engineering PoGO itself. When Niantic decides to change things, it's a fairly complicated process to understand what and how exactly those things were changed. Re-implementation is a different issue entirely. |
i'll copy myself hoping it helps clarifying problem source PokemonGoF/PokemonGo-Bot#2540:
|
Niantic made a change in their api. There detecting if the request came from a mobile device. All trackers / bots are affected. |
Indeed, they have changed it, I noticed errors last night, and wrote another bot using another project - this is also affected. Boo :-( |
well, not likely changed the api. If they changed the network protocol, then the client part should be updated too, however, this did not happen. |
They seem to have enabled server side verification of something the client was sending for a while already. -------- Ursprüngliche Nachricht -------- well, not likely changed the api. If they changed the network protocol, then the client part should be updated too, however, this did not happen. You are receiving this because you are subscribed to this thread. |
Niantics Labs (the company of Pokemon Go) has made changes to how the internal API works (the system of communications between server and phone apps). |
sorry I just copy pasted from a comment I made on a different Bot issue so some of the things might be irrelevant to discussion, main idea holds though |
did they resolved the issue ? edit : https://github.com/pkmngodev/Unknown6/wiki |
please close. |
!!! There is a new type of ban, which seems... temporary.. (still) After a while, it starts working again. I confirm this by using multiple bots, all have the same issue, when I go to VPN or use proxy, it starts working again. Switch back, same issue. After a while, it works again. |
@dnsBlah That's a softban. |
@checkplys This type of ban is in since last night. Even with a complete inactive account, you have the same symptons. |
This issue has already been solved by almost every other major API, see keyphact/pgoapi. It has to do with a new encryption on RequestEnvelope, took those working on it over at POGOProtos about 5 days to fix. Requires a native encryption library to be installed and a small change to be made to request envelope building. |
@IamCarbonMan already implemented |
Still getting a "no forts found" error on running demo.py, exactly like it was a week ago before unknown6 was discovered. |
With master? Demo makes a lot more calls than the keyphact one, upping delay times works pretty well. Checkout trainer https://github.com/rubenvereecken/pokemongo-api/tree/trainer if you're still having issues. About to merge this in, should have best chance |
The trainer branch currently doesn't work at all, no demo to run. |
It's been pulled out into root |
Oh, obviously. Sorry about that, however demo.py in the trainer branch does have exactly the same behavior. |
Try solution to #87 ? |
Okay, specifying |
thats just weird |
@dmasisetti I found a other project that supplies all variants |
Providing compiled encrypt libraries is dangerous since they're made with copyrighted code. However, autodetecting the library by os should be trivial to implement. |
guess so ye |
This just started happening today. I think something changed on niantic's end.
Edit: looks to be an issue with protobuf structure
AeonLucid/POGOProtos#131
The text was updated successfully, but these errors were encountered: