Open infinitewarp opened 8 years ago
Getting this consistently as well.
I wonder if Niantic has already caught on to us. š
It seems like other bots are having issues as well. This seems like a problem bigger in scope than this project.
On the other hand, people are reporting results with longer api rest times. Something on the order of 15 secs seems to work.
FWIW, my affected account in question appears to be OK in general. After waiting a bit to "travel" to my real-world location, I logged in with the real client on my phone, and things appear to be just fine. The only item of interest was that I instantly got my latest level-up items when logged in there.
Maybe it's the level-up items that's holding up the requests? I know before, a person could just level up without accepting the level-up rewards. It may be that the client has to accept them before doing anything else?
That's what I was suspecting too. It looked like I had a couple of level-ups hit that account simultaneously when I logged in. I need to let my location "travel" for a little bit again before I can try this account in the bot. Will report back with my findingsā¦
As another point of reference, a different account I'm testing with is not affected by this problem, and I don't think it's leveled up recently (or at least not multiple times).
https://github.com/j-e-k/poketrainer/issues/448
Also came across this
Experiencing the same here as well. I'm stuck for an hour traveling home.
After acknowledging the level-ups in the real game on a real phone, disconnecting and "traveling" a bit, and logging back in with the bot, all is good for me again. Evidence points in the direction of the unacknowledged level-ups causing this problem.
Would you guys try the same and see if that solves it for you too?
Logged in to check that as well, haven't leveled up. Still getting the same error. Tried running it with cached forts and still got the same error. What do you guys have for step size, just curious, I'm doing 100.
Was getting the same with 15 - 30 step size.
Hmm
@cryzies jesus christ you realize that step size 100 is 223.694 MPH.... slow it down and bit and be smart about this
Finally back "Home" I did have a level up pending.
I got the same error earlier tonight. I just let the bot cool off for about an hour and it's working again now, though I didn't mess with my level ups at all. As OP said, maybe this is the new "softban."
PS: not sure how it all comes into play, but I'm using stepsize: 6, extra wait: 5, sleep multiplier: 1
@HibikiFox haha as long as I'm not getting soft banned.
Traceback (most recent call last):
File "pokecli.py", line 166, in main
api.main_loop()
File "/home/bober/poketrainer/pgoapi/pgoapi.py", line 1175, in main_loop
self.spin_all_forts_visible()
File "/home/bober/poketrainer/pgoapi/pgoapi.py", line 655, in spin_all_forts_visible
res = self.nearby_map_objects()
File "/home/bober/poketrainer/pgoapi/pgoapi.py", line 740, in nearby_map_objects
cell_id=neighbors).call()
File "/home/bober/poketrainer/pgoapi/pgoapi.py", line 271, in call
response = request.request(self.get_api_endpoint(), self._req_method_list[id(gevent.getcurrent())], player_position)
File "/home/bober/poketrainer/pgoapi/rpc_api.py", line 132, in request
response_dict = self._parse_main_response(response, subrequests)
File "/home/bober/poketrainer/pgoapi/rpc_api.py", line 362, in _parse_main_response
response_proto_dict = self._parse_sub_responses(response_proto, subrequests, response_proto_dict)
File "/home/bober/poketrainer/pgoapi/rpc_api.py", line 379, in _parse_sub_responses
request_entry = subrequests_list[i]
IndexError: list index out of range
Getting this on only some of my bots, all are botting in the same location.
I also noticed this question. Step size:6, do not experience any level-up.
New update apparently makes step size max out at 5 (due to the driving warning, we will get this fixed soon...)
First I've seen one of these, but now it's happening consistently with one of my accounts. Looks like a possible protocol issue or a new manifestation of soft banning?