Skip to content
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.

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

API v0.55.0 - API check fail #5900

Closed
camnomis opened this issue Feb 6, 2017 · 5 comments
Closed

API v0.55.0 - API check fail #5900

camnomis opened this issue Feb 6, 2017 · 5 comments

Comments

@camnomis
Copy link

camnomis commented Feb 6, 2017

Ran a fresh install of the bot (master branch, commit 7c2722d) on a brand new VM (ubuntu 16.4.0 LTS) after trying Pogarek's for a while, bought a brand new hash key (and according to buddyauth it's gone from "UNUSED / INACTIVE" to "ACTIVE" so that bit is OK), tried to follow @pogarek's adivce in #5882 and ran

pip2 install --upgrade -r requirements.txt

But am still getting the API check fail, is this expected behaviour, is there something in the bot that will need to be updated to work with 0.55.0?

@MerlionRock
Copy link
Contributor

MerlionRock commented Feb 6, 2017

in Config, set "check_niantic_api": false

Don't worry, if you have done the upgrade, it should be on API 0.55

Also, you can do a ./setup.sh -u to do the upgrade.

I do have a updated version for checking niantic api, however, whenever there's a version change, changes have to be done on github, which is not dynamic. Nevermind, I'll do a pull request for a afterall.

@camnomis
Copy link
Author

camnomis commented Feb 6, 2017

Will spin up a dummy account and see if it comes up with the captcha warnings

@pogarek
Copy link
Contributor

pogarek commented Feb 6, 2017

My repo should be quite close to master repo. Make sure to run 'git pull' from time to time.
Or backup config files , delete data and take te main repo/

@MerlionRock
Copy link
Contributor

MerlionRock commented Feb 7, 2017

Do a ./setup.sh -u

API check updated #5901

@pogarek
Copy link
Contributor

pogarek commented Feb 19, 2017

closing because pgoapi is on 0.57 now. Reopen if this still happens

@pogarek pogarek closed this as completed Feb 19, 2017
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

No branches or pull requests

3 participants