-
Notifications
You must be signed in to change notification settings - Fork 29
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
Seems like google is refreshing my access token every few minutes 😥 #114
Comments
Hi, first I would ask how are you getting your cookies. If you are using an account that you are actually using then you might be getting new cookies often. It is suggested to use a third account that is not in everyday use and share your location to that one. When you export the cookies use a cookie deleting add on so the session does not terminate if you close your browser. That's what I can think of right now. |
Thx for your feedback, I guess it's time for a new account, I was using one especially for this - whereischagai 😂 but I guess I used it too often... |
Good luck with a new account. Please feel free to close this if you think that your question is answered. |
Yep it works great! Just wanted to wait a few hours to see if it still works 😎 |
Hey, I need to reopen this, I just opened a new account and the cookies are invalidated again... I'm going to open another new account just to make sure this is actually happening consistently, or maybe it's related to me having shared my location with this account? |
it's been working for an hour, I'll keep this updated |
It's still working so I'm gonna close this, I think it might be related to not having verified some security measure before sharing the location with my main account. |
I am having this issue again so I'm going to re-open... I tried creating two new accounts already and it still invalidates the caches after a few minutes/hours.... |
Did anyone else experience this? Is there anything I can do?
I have it behind this API:
https://api.chagai.website/location
The text was updated successfully, but these errors were encountered: