Anki 25.07/08 Beta 1-2

Not sure if anyone have reported this already. The “your parameters are already optimal” pop-up doesn’t show up when you’re doing the health-check.

And it should. Both messages should show up.

1 Like


Perhaps we should reconsider the design of the “FSRS Simulator”? Having a window nested within another window creates unnecessary confusion.

2 Likes

I can’t seem to reproduce this with beta 1 and the latest launcher. Is anyone else still seeing it?

I agree
@A_Blokee I think the simulator should be a separate window, like the Edit window

2 Likes

image
Another inexplicable bug. This one occurred after editing an IO card


Going back to the deck menu didn’t fix it. Restarting Anki did help

1 Like

I also noticed the same issue. After recompiling from source it seemed to be fixed.

That is unfeasible. The simulator is heavily related to presets.

A post was split to a new topic: Hover over images

I’m not sure if this was a thing before

I have selected a deck, and I see the cog icon. If I hover the mouse over the place where the cog icon of another deck should be, it’s invisible, but clickable


On the image you can see that I clicked the invisible cog icon of a deck that isn’t currently selected. If I remember correctly, previously the cog icon was visible even if the deck wasn’t selected

1 Like

I set a python virtual environment in my ~/.zshrc file and this appears to keep the Anki Launcher from determining the current version. When the Anki Launcher comes up I get a warning that Anki could not determine the current version:

Anki Launcher

Warning: Could not determine current Anki version

  1. Latest Anki (just press enter)
  2. Choose a version
  3. Revert to previous version (25.08b1)

If I install from scratch without sourcing my venv in ~/.zshrc then the Anki Launcher shows the current version. Once I restore the line to source my venv to my .zshrc file, though, the launcher stops showing the version, whether I source my venv or not.

For a bit more background, if I hit Enter to get the latest Anki, I get this message at the top. I suspect, though, that the Launcher does not ignore my virtual environment everywhere.

warning:VIRTUAL_ENV=/Users/myname/venv_313 does not match the project environment path .venv and will be ignored; use --active to target the active environment instead**

In spite of this, Anki runs fine, I just see the problems in the launcher.

Using the latest installer, when trying to downgrade from 25.08b1 to 25.07.2, I often get this failure:

error: failed to remove file 
C:\Users\Username\AppData\Local\AnkiProgramFiles\.venv\Lib\site-packages\PyQt6/Qt6/resources/icudtl.dat: 
The file cannot be accessed. The file is being used by another process.. (os error 32)
Install failed: Failed with code Some(2): C:\Users\Username\AppData\Local\Programs\Anki\uv.exe sync --upgrade --managed-python --no-config --python 3.13.5

The issue with AnkiConnect is because it cannot parse beta versions properly. See the comments https://ankiweb.net/shared/info/2055492159.

The error message is:

When loading AnkiConnect:
Traceback (most recent call last):
  File "C:\Users\me\AppData\Local\AnkiProgramFiles\.venv\Lib\site-packages\aqt\addons.py", line 250, in loadAddons
    __import__(addon.dir_name)
    ~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "C:\Users\me\AppData\Roaming\Anki2\addons21\2055492159\__init__.py", line 19, in <module>
    anki_version = tuple(int(segment) for segment in aqt.appVersion.split("."))
  File "C:\Users\me\AppData\Roaming\Anki2\addons21\2055492159\__init__.py", line 19, in <genexpr>
    anki_version = tuple(int(segment) for segment in aqt.appVersion.split("."))
                         ~~~^^^^^^^^^
ValueError: invalid literal for int() with base 10: '08b1'

This is not the most elegant solution, but you can temporarily fix it by going to the path e.g. (C:\Users\your-username\AppData\Roaming\Anki2\addons21\2055492159\__init__.py) and replacing line 19:

anki_version = tuple(int(segment) for segment in aqt.appVersion.split("."))

with

import re
anki_version = tuple(
    int(segment) for segment in re.split(r"[a-zA-Z]", aqt.appVersion)[0].split(".")
)
1 Like

Question on Python interpreter version:
Does downloading from https://github.com/ankitects/anki/releases/download/25.02.7/anki-25.02.7-windows-qt6.exe not result in getting a version of Anki which uses Python 3.13 ?
I was very surprised to see that’s not the case:


I looked for settings in preferences to see whether there’s a dropdown somewhere, but apparently not so I must have missed something, I thought 25.02.7 would switch everyone to Python 3.13.

1 Like

You’re confusing 25.02.7 with 25.07.2

2 Likes

I just downloaded and installed the latest bundle (sha256:ec657fac9e45ef249432732cb55ff2a2944b8d8d4a7069cfbdd9a3275a1ea257) for the Mac. If I pick “2) Choose a version” from the Upgrade/Downgrade window from Anki I get the following error:

Please wait…
Error: Failed with code Some(1): /Applications/Anki.app/Contents/MacOS/uv run --no-project /Applications/Anki.app/Contents/Resources/versions.py
Press enter to close…

If I start the launcher from the command line and get the upgrade/download menu then this works fine:

Please wait…
Latest releases: 25.08b1, 25.07.2, 25.06b7, 25.02.7, 25.05b2
Enter the version you want to install:

If I run the versions.py from the error on the command line I get this:

/Applications/Anki.app/Contents/MacOS/uv run --no-project /Applications/Anki.app/Contents/Resources/versions.py
[“2.1.24”, “2.1.25”, “2.1.26”, “2.1.28”, “2.1.29”, “2.1.30”, “2.1.31”, “2.1.32”, “2.1.33”, “2.1.34”, “2.1.35”, “2.1.36”, “2.1.37rc1”, “2.1.37”, “2.1.38b1”, “2.1.38b2”, “2.1.38b3”, “2.1.38b4”, “2.1.38”, “2.1.39b1”, “2.1.39b2”, “2.1.39”, “2.1.40”, “2.1.41b1”, “2.1.41b2”, “2.1.41b3”, “2.1.41b4”, “2.1.41b5”, “2.1.41b6”, “2.1.41b7”, “2.1.41”, “2.1.42”, “2.1.43b1”, “2.1.43”, “2.1.44b1”, “2.1.44”, “2.1.45a1”, “2.1.45a2”, “2.1.45a3”, “2.1.45a4”, “2.1.45b1”, “2.1.45b2”, “2.1.45b3”, “2.1.45b4”, “2.1.45b5”, “2.1.45b6”, “2.1.45rc1”, “2.1.45rc2”, “2.1.45”, “2.1.46rc1”, “2.1.46”, “2.1.47rc1”, “2.1.47rc2”, “2.1.47”, “2.1.48rc1”, “2.1.48rc2”, “2.1.48”, “2.1.49”, “2.1.50b1”, “2.1.50b2”, “2.1.50b3”, “2.1.50b4”, “2.1.50b5”, “2.1.50b6”, “2.1.50b7”, “2.1.50b8”, “2.1.50b9”, “2.1.50rc1”, “2.1.50rc2”, “2.1.50rc3”, “2.1.50rc4”, “2.1.50”, “2.1.51rc1”, “2.1.51rc2”, “2.1.51”, “2.1.52rc1”, “2.1.52rc2”, “2.1.52rc3”, “2.1.52”, “2.1.53rc1”, “2.1.53rc2”, “2.1.53”, “2.1.54rc1”, “2.1.54rc2”, “2.1.54rc3”, “2.1.54”, “2.1.55b1”, “2.1.55b2”, “2.1.55b3”, “2.1.55b4”, “2.1.55b6”, “2.1.55b7”, “2.1.55rc1”, “2.1.55rc2”, “2.1.55”, “2.1.56rc1”, “2.1.56”, “2.1.57b1”, “2.1.57rc1”, “2.1.57”, “2.1.58”, “2.1.59”, “2.1.60”, “2.1.61b1”, “2.1.61b2”, “2.1.61”, “2.1.62b1”, “2.1.62rc1”, “2.1.62”, “2.1.63”, “2.1.64”, “2.1.65”, “2.1.66b1”, “2.1.66rc1”, “2.1.66”, “23.10b1”, “23.10b2”, “23.10b3”, “23.10b4”, “23.10b5”, “23.10b6”, “23.10rc1”, “23.10rc2”, “23.10rc3”, “23.10”, “23.10.1rc1”, “23.10.1rc2”, “23.10.1”, “23.12b1”, “23.12b2”, “23.12b3”, “23.12rc1”, “23.12”, “23.12.1”, “24.4rc1”, “24.4rc2”, “24.4”, “24.4.1”, “24.6”, “24.6.1”, “24.6.2”, “24.6.3”, “24.10b1”, “24.10b2”, “24.10b3”, “24.10b4”, “24.10rc1”, “24.10rc2”, “24.11rc1”, “24.11rc2”, “24.11”, “25.1b1”, “25.1rc1”, “25.2rc1”, “25.2”, “25.2.1”, “25.2.2”, “25.2.3”, “25.2.4”, “25.5b1”, “25.5b2”, “25.2.5”, “25.2.6”, “25.2.7”, “25.6b1”, “25.6b2”, “25.6b3”, “25.6b4”, “25.6b5”, “25.6b6”, “25.6b7”, “25.7”, “25.7.1”, “25.7.2”, “25.8b1”]

1 Like

Well, here’s another UI bug
image

I gotta start counting

  1. Whatever this is (not easily reproducible, I’ve only seen it once)

  2. Black bar (not easily reproducible, I’ve seen it twice)

  3. Invisible but clickable cog icons (should be easily reproducible)

Btw, I reverted to 25.07.1 (a83a6b59)⁩ and cog icons are visible. So the invisible cog problem is indeed new in 25.08. Changing video drivers doesn’t fix it.

  1. This (not easily reproducible, I’ve only seen it once)
    image
1 Like

Hi all,

Beta 2 and a new launcher is now available. Updating the launcher prior to upgrading is recommend.

Thanks, the next launcher should fix this, and presumably your issue with choosing a version.

Probably related to the unclosed anki.exe processes you were seeing, which I wasn’t able to reproduce. Does it happen without add-ons enabled?

This is likely Qt/WebEngine issues. I’ll tweak the webengine version in the next beta - please let me know how it goes compared to b1.

4 Likes

Speaking of which, is this intended?
image
I assume no

The inivisible cogs are visible again :+1:

2 Likes

It displays as bold on Windows 11. I’m guessing you’re on Windows 10?