Post: ISSUE FIXED: Niantic API changes & Why the Pokemon GO bots are not working!
Options
08-03-2016, 09:42 PM
#1
Sloth
Banned
ISSUE: Niantic API has added new checks, the data sent is encrypted or signed
STATUS: Fixed Release here: You must login or register to view this content.
ISSUE BEGAN: Around 4PM EST 8/3/16
ISSUE RESOLVE
Around 7PM EST 8/6/16What's going on?
Issue has been fixed the Python request code has been released here now just wait on your bot devs to implement the code
You must login or register to view this content.
Necrobot: You must login or register to view this content.
Compiled Release: You must login or register to view this content.
Pokesniper2: You must login or register to view this content.
Note: I will probably release my web based sniper later on today as well
Final Post - Update 5:00PM 8/5/16
Since I cant make updates to this thread constantly these two links are the main source for updates
Reddit Live Updates: You must login or register to view this content. (Non technical Users)
Github Technical Update (Latest): You must login or register to view this content. (Technical Users)
If you want to try and keep track of the issue more
Reddit Live Updates: You must login or register to view this content.
Unknown6 Github: You must login or register to view this content.
List of users working on API & decompiled subs: You must login or register to view this content.
Google Doc: You must login or register to view this content.
Reddit: You must login or register to view this content.
NextGenUpdate: You must login or register to view this content.
PokemonGoDev: You must login or register to view this content.
PokeMobBot: You must login or register to view this content.
NecroBot: You must login or register to view this content.
Fifth Post - Update 4:00pm EST 8/4/16
We know most of the payload that goes in to the Unknown 6 hash, we are waiting on the rest and the encryption/signature algorithm.
Read 4th Post for more info.
Fourth Post - Update: 8:00AM EST 8/4/16
Basically Niantic API now checks Unknown6 on each request this field is signed or encrypted (with multiple layers I believe) before being sent off with the request.
Reverse engineers have figured out the functions that generating the signing or encryption or hash (not confirmed which yet) and are now looking in to functions that create the data that is unknown6
Also they are trying to find the signing or encryption key used.
Originally posted by another user
Unknown6 is a field within the RPC call, it contains a timestamp, a hash (unconfirmed) and some other unknown data that the official PoGo client sends with its RPC call,
up until recently sending Unknown6 as empty had no effect on the data you received from the server,
yesterday this changed and if you don't send a valid Unknown6 field then the server will return all of the map data as being empty.
So the devs who are reverse engineering are trying to find what data goes into Unknown6 so we can replicate it.
We currently have a good idea of the functions that might be generating the hash, but as of yet, we don't know what goes into Unknown6 ..
Third Post - Update: 4:00AM EST 8/4/16
So it seems like the changes made to the API are to do with the request possibly being cryptographically signed thus explaining why no information is coming through.
Devs are working on trying to reverse engineer this and "crack" the signed request , I don't want to say too much on the topic since it is something I do not understand.
Also the minimum map object refresh rate has been upped again, from 5 seconds to 10 seconds. This means the rate at which you can query for new pokemon successfully has been cut in half.
Second Post - Update: 8:00PM EST 8/3/16
So it seems that as well as changing the map objects part of the API Niantic has also decided to start obfuscating their API answers.
Necro is working with some others in an attempt to bypass the security measures Niantic has implemented in to there app & API.
Quote from Necro
Originally posted by another user
Necronomicon - Today at 6:23 PM
@everyone Final Status Update:
Niantic has now began to obfuscate the API answers. This means that we will need to update the POGOProtos and implement the new hash b1f2bf509a025b7cd76e1c484e2a24411c50f0612.
Reverse Engineering an App with SSL Pinning is hard to do, thanks to git user rastapasta & cstrachan88 we able to bypass these security measures.
Niantic took a big step to block Bots. But we are sure this is bypassable.
Sorry for the inconvenience.
Original Post - Update: 4:30PM EST 8/3/16
So around 4PM EST today Niantic made some changes to their API, from what I can gather from looking at the response I received from my own Sniper and also what other bot devs are saying is that Niantic have changed the way the API sends map objects (Pokestops, Gyms & Pokemon).
The way to fix this issue obviously is to try and figure out the new way Niantic is sending Map Objects to the game, this however requires reverse engineering of the API which takes time, I know bot devs are currently attempting to work on this but there is no ETA.
Map Object Response
As you can see from this response I am not getting any information about pokestops, gyms or pokemon
You must login or register to view this content.
Last edited by
Sloth ; 08-07-2016 at 02:18 PM.
The following 12 users say thank you to Sloth for this useful post:
08-05-2016, 11:57 PM
#17
Sloth
Banned
Originally posted by infinityredDot
any ideas when bot will be rdy?
Originally posted by Kellis
Great thread Sloth, keep the updates coming! Your hard work is much appreciated!
Originally posted by infinityredDot
any updates when it will be working?
Originally posted by jblaze519
No they r working on it till then play for real n stop sitting around ur house
Since I can't as one person constantly update this I have now just linked to the reddit live page for non technical users and the github for the technical users these are the most reliable sources.
Copyright © 2024, NextGenUpdate.
All Rights Reserved.
