Skip to content

Conversation

@krzys-h
Copy link
Contributor

@krzys-h krzys-h commented Jul 31, 2016

Endpoint change requests (status code 53) can happen not only during login sequence, but also on normal requests. This often happens with START_GYM_BATTLE.

Endpoint change requests (status code 53) can happen not only during login sequence, but also on normal requests. This often happens with START_GYM_BATTLE.
@Nostrademous
Copy link

Nostrademous commented Aug 3, 2016

@krzys-h I think the reponse you are checking for == 53 is the HTTP/HTTPS response and not the actual response of the contents returned (which I believe is your intention).

@krzys-h
Copy link
Contributor Author

krzys-h commented Aug 3, 2016

@Nostrademous This is the response code, see very similar code here: https://github.com/tejado/pgoapi/blob/master/pgoapi/rpc_api.py#L113-L118
I have tested this and it works correctly.

@Nostrademous
Copy link

@krzys-h sorry, you are correct. I forgot he uses the protobuf_dict stuff which parses the http_response into the ResponseEnvelope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants