Quote:
Originally Posted by sgmoore
Sorry for the delay in responding, but I missed this message.
The forbidden/missing_chip message simply means you need to manually refresh your token.
I'm still using simon-techkid's extension to get the token : see https://github.com/ping/libby-calibr...ent-2305881945
The bad news is that unfortunately we are going to have to do this a lot more regularly (probably every week)
The token contains an expiry date and stops working after a week. What used to happen was when you synced successfully, the response you got back contained a new token with an updated expiry date and ping's code saved this token back for use the next time. So simply opening this plugin regularly would keep refreshing the token and it did not expire.
Now the response from libby website no longer returns a new token and so the token we have will expire after a week. |
I also found installing
mitmproxy was an invaluable tool in capturing the token. This also lets you see all the requests and responses inb what I found to be an easier format to read than the chrome internal network logging.