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

Add re-auth reminders for trackers #1700

Open
4 tasks done
mm12 opened this issue Feb 4, 2025 · 2 comments
Open
4 tasks done

Add re-auth reminders for trackers #1700

mm12 opened this issue Feb 4, 2025 · 2 comments
Labels
Feature request New feature or request

Comments

@mm12
Copy link
Contributor

mm12 commented Feb 4, 2025

Describe your suggested feature

When the app opens, it should check how long it has been since the trackers were logged in. If it is nearing the time for the token to expire, the user should be asked to log out and back in.

Other details

Low priority. Anilist just cuts it off after 1 year, and returns error 500 instead of error 440.

Acknowledgements

  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
  • I have written a short but informative title.
  • I have updated the app to version 0.17.1.
  • I will fill out all of the requested information in this form.
@mm12 mm12 added the Feature request New feature or request label Feb 4, 2025
@MajorTanya
Copy link
Contributor

MajorTanya commented Feb 4, 2025

AniList offers no way to renew auth after that one year expiry. No endpoint in their auth for that. We'd have to prompt users to do that, best case scenario we'd do it before expiry actually happens.

Edit: 440 would be a Microsoft specific code. More correct would be a 401 Unauthorized.

@mm12
Copy link
Contributor Author

mm12 commented Feb 4, 2025

AniList offers no way to renew auth after that one year expiry. No endpoint in their auth for that. We'd have to prompt users to do that, best case scenario we'd do it before expiry actually happens.

Edit: 440 would be a Microsoft specific code. More correct would be a 401 Unauthorized.

Yes, that is what I was intending to say. I was unaware that 440 was MS specific, but the fact that they use 500 is quite annoying. Not only does it give no good information, it gives BAD information ("server at fault" when it isn't). Though not a lot we can do about that, is there...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants