Request inaccuracy #907

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

1 of 7 tasks

Gegy opened this issue Apr 13, 2017 · 0 comments

Labels

Collaborator

Gegy commented Apr 13, 2017 •

edited

Loading

Confirmed:

In the official app, messages (GMOs) are still sent while a challenge is active.
DOWNLOAD_SETTINGS is only sent as a common request with login requests.
GET_ASSET_DIGEST is paginated and response should be handled
GET_STORE_ITEMS is sent after LEVEL_UP_REWARDS

Unconfirmed:

After the auth ticket expires, the login requests are resent.
If incense is active on login, GET_INCENSE_POKEMON is not sent as a common request until the first GET_PLAYER_PROFILE is sent.

Not understood

After a challenge has been solved, the CHECK_CHALLENGE common request moves to the end of the common list until the next login occurs. (Occurs on the VERIFY_CHALLENGE message and continues after)

Gegy added the discussion label

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