LOG:
Necronomicon - 15 hours ago
@everyone If you're running a lot of accounts, Niantic has started limiting IPs so those accounts who have excessive requests / multiple accounts from the one location are temporarily blacklisted and receive empty map objects, which leads to what you see.
@everyone Servers are unstable / down right now. Please check
Is Pokémon GO down or not? No one was banned!
@everyone NO ONE WAS BANNED. The Servers are really unstable / down right now.
@everyone It seems like the Servers are getting stable again.
@everyone It seems like Niantic changed the way they provide MapObjects. We are working on a fix as FeroxRev is offline right now.
Necronomicon - 14 hours ago
@everyone The fix is being deployed right now, thanks for waiting.
@everyone Seems like its taking a bit longer, thanks for waiting.
@everyone Doing last minute Tests!
@everyone Tests are failing, you gotta hold on! ❤
Necronomicon - 13 hours ago
@everyone Okay so these are pretty big changes that go to protos level. We gotta work some more
@everyone #off-topic is now open. using this chat for anything necrobot related will result in a mute!
@everyone These are pretty big changes, might take up to 24-48hrs
Necronomicon - 12 hours ago
@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 inconvienience.
Posted by Eddarak - 9 hours ago
@everyone ATTENTION There is currently an issue with the API. The Necro team are working hard to fix this issue. For now the bot will not work, any issues you have regarding Pokestops, is a direct link to this issue. Any errors you see in your client, is 90% a direct link to this issue. Please do not spam the chat with your issue as they are already being addressed. Estimated time is not yet clear. As soon as a fix it brought out, you will see it within the #announcements tab. Once again, please refrain from spamming the chat with questions regarding your client. For any other issues, please navigate to the #support tab. Thanks for your patience
Posted by ! Kisaragi ! - 1 hour ago
@everyone We haven't got the news regarding the issues and we will announce once there are some significant development/status about the API and the NecroBot. Also, we will give an ETA once we found the function that encodes requests unknown6 in the API. You can check the current API status of Pokemon Go in this Reddit thread:
https://www.reddit.com/r/pokemongode...nt_api_status/
Necronomicon - 30 minutes ago
@everyone There are many users working together to fix the API change. Thanks to everyone! Currently figuring out when unkown6 is being sent.
EDIT: NEW UPDATES FROM DISCORD
Necronomicon posted:
@everyone Unkown 6 was finally resolved. Thanks to all api debuggers! We now have to start work on implementing things into code and wait for a decryption.
@everyone Don't thank us, thank all API Reverser over at /R/pokemongodev !
@everyone Just to make sure. We just found the Unkown 6 Chunk nothing else. Its still takes more work. The api guys just know where to look now. Sorry for false Information!