26.08 - Cannot check for updates, "Email or password was incorrect"

Anki Help
1

The issue started when I installed 26.08beta2 and persists after updating to the 26.08 stable release. To be able to update, I downloaded the install package from the GitHub release.

When I choose Tools->Check for Updates, I get an error message as below:

image
image657×226 13.1 KB

My account is working because sync between devices works fine.

My version, installed on Win 11:

Version ⁨26.08 (666c2c64)⁩
Python 3.13.13 Qt 6.11.0 Chromium 140

2

I only get “No updates available”. Maybe it is different for me because I use a custom sync server (whyever that would be the case)?

Anki 26.08 (666c2c64) (ao)
Python 3.13.13 Qt 6.11.0 PyQt 6.11.0
Platform: Linux-6.12.74+deb13+1-amd64-x86_64-with-glibc2.41

3

I also get “No updates available” with 26.08 on Mac. I use the default AnkiWeb server for syncing. I upgraded from 26.08beta2 to 26.08 via downloading and installing the .dmg file.

4

Can you reproduce this without add-ons?
The update option just checks for new releases on GitHub - it shouldn’t rely on AnkiWeb or custom servers.

5

Now I also only get “No updates available”.

Weird. I will try a few times in the next days, maybe I will be able to reproduce.

6

I’ve just tried and got this again.
I opened Anki with Shift held down, so no add-ons are loaded.

image
image655×227 12.9 KB

7

I reconfirm that “Check for Updates” still works for me:

  • With Version 26.08, the button correctly told me that there was an update available (and I installed it).
  • With Version 26.08.1, the button correctly told me “No updates available”.

OP: Perhaps there is some other sort of network-related problem that is being (incorrectly?) detected as an authentication issue? I suggest that you try some network-related troubleshooting activity to see if anything might possibly help. (Things like rebooting your computer, rebooting your router, trying a different network connection, disabling VPN, etc.)

8

I was able to reproduce it in 26.05. Looking into it.

9

It turned out to be a GitHub rate limit error:

10

Thank you.

I knew I wasn’t crazy :rofl: