Handle server-side endpoint change requests#161
Open
krzys-h wants to merge 1 commit into
Open
Conversation
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.
Open
|
@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). |
Contributor
Author
|
@Nostrademous This is the response code, see very similar code here: https://github.com/tejado/pgoapi/blob/master/pgoapi/rpc_api.py#L113-L118 |
|
@krzys-h sorry, you are correct. I forgot he uses the protobuf_dict stuff which parses the http_response into the ResponseEnvelope |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.