-
Member
Pokemon Go Bots Not Working?
No Pokemon Go bots are working for me today, they've been fine now everytime I log in on them it shows a massive red error, I've been doing it manually today so its not my account or internet.
Anyone else have this problem or is there a fix?
Thanks.:confused:
-
Member
Niantic made some changes, possibly an all new API, about this time yesterday.
They did something pretty massive, since even tools like Ivy don't work, and Ivy doesn't run on the API
-
Active Member
It's not a new API, it's extra checks when you login to see if you play from a legit mobile phone device, this check was already implemented in 0.55 API but just activated yesterday.
So it somehow finds out this way, you are not playing from a legit mobile phone device and shuts you out.
From what i read, the only bot that had a fix already for this was PokeFarmer.
Other bot makers are working on a fix, so stay tuned and don't bot till a fix is out for your bot.
(Or don't bot at all untill everything is fixed for the new api 0.57 that's rolling out now and GEN2 pokemon)
[EDIT]
- Eternal Bot also fixed the login problem.
Last edited by pogotrainee; 02-15-2017 at 01:54 PM.
-
Post Thanks / Like - 1 Thanks
welshroxy (1 members gave Thanks to pogotrainee for this useful post)
-
Member
Thanks
Went in the shower
-
Member
Originally Posted by
pogotrainee
It's not a new API, it's extra checks when you login to see if you play from a legit mobile phone device, this check was already implemented in 0.55 API but just activated yesterday.
So it somehow finds out this way, you are not playing from a legit mobile phone device and shuts you out.
From what i read, the only bot that had a fix already for this was PokeFarmer.
Other bot makers are working on a fix, so stay tuned and don't bot till a fix is out for your bot.
(Or don't bot at all untill everything is fixed for the new api 0.57 that's rolling out now and GEN2 pokemon)
[EDIT]
- Eternal Bot also fixed the login problem.
Slightly off with the information. All they did was validate the signature (uk6) on the initial request (the one that sends a provider). It was always there, but never required. I changed type 8. That isn't required on the initial request. My bot (GoManager) already had that implemented. When I rebuilt the API, I didn't get a valid response without it, so I added it. The panic from it even reached my Discord causing people to think they had to stop botting.
There was another change that happened about a day prior to that. They cleaned up their backend requests to remove PlayerUpdate (hasn't been used for a long time). May have been a couple bots that went down due to that.
If you were using a bot that did go down for either reason, there's a possibility the account is now flagged. I heard reports of bans from Ninja, but I not sure if they were true.