Anki 2.1.66 Beta

3 posts were split to a new topic: Menu pops up on wrong display

website homepage still shows Anki 2.1.65

1 Like

This new version of Anki is trying to install on my username and not on program files. It has been changed?


This changed in 2.1.64: Changes in 2.1.60 to 69 - Changes


I am checking 2.1.66 Beta with Mac M1 Qt6 version.
When I selece multiple card on browser with shift+click or cmd+click, the window suddenly shut down. I tried several times and got same results.
Below is an excerpt of error report.

Translated Report (Full Report Below)

Process: anki [27376]
Path: /Applications/
Identifier: net.ankiweb.dtop
Version: 2.1.66 (???)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2023-08-28 16:54:16.6935 +0900
OS Version: macOS 13.4.1 (22F770820d)
Report Version: 12
Anonymous UUID: E250B4C0-6C11-3574-0DD7-C0C8B27C1F2B

Sleep/Wake UUID: CB41C42C-A4CD-4BBE-8072-F57B57D41D67

Time Awake Since Boot: 260000 seconds
Time Since Wake: 488 seconds

System Integrity Protection: enabled

Crashed Thread: 0 CrBrowserMain Dispatch queue:

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008
Exception Codes: 0x0000000000000001, 0x0000000000000008

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [27376]

VM Region Info: 0x8 is not in any region. Bytes before following region: 105553518919672
MALLOC_NANO (reserved) 600018000000-600020000000 [128.0M] rw-/rwx SM=NUL …(unallocated)

Thread 0 Crashed:: CrBrowserMain Dispatch queue:
0 QtWidgets 0x10d9820a0 QWidget::raise() + 52
1 QtWidgets 0x10da73344 0x10d92c000 + 1340228
2 QtWidgets 0x10daa9080 0x10d92c000 + 1560704
3 QtWidgets 0x10daa8998 0x10d92c000 + 1558936
4 QtWidgets 0x10d9664a8 QLayoutPrivate::doResize() + 224
5 QtWidgets 0x10d966af0 QLayout::activate() + 1224

Does the “reset window sizes” option in the preferences help?

On 2.1.66, the toolbar for both HyperTTS and Language Tools addons stopped working with the following output in the console:

JS warning /_anki/js/editor.js:437 No version information available for component [tex]/noerrors
JS warning /_anki/js/editor.js:437 No version information available for component [tex]/mathtools
JS warning /_anki/js/editor.js:437 No version information available for component [tex]/mhchem
JS error /_anki/js/editor.js:530 Uncaught Error: Cannot require "svelte/internal" at runtime.
JS error /_anki/js/editor.js:530 Uncaught Error: Cannot require "svelte/internal" at runtime.
configureEditorHyperTTS(["New Preset"], 'New Preset', false)
JS error /_anki/legacyPageData?id=140607728117648:1 Uncaught ReferenceError: configureEditorHyperTTS is not defined
JS error /_anki/legacyPageData?id=140607728117648:1 Uncaught ReferenceError: setLanguageToolsEditorSettings is not defined

Here is the code used to build editor components for HyperTTS:

I looked at the changelog but couldn’t find which change exactly might have caused this, also I see that this repository is unchanged: GitHub - hgiesel/anki_new_format_pack, if there was a change in the Svelte API, I would have expected “anki_new_format_pack” to reflect this.

Anyone else with svelte editor extensions experienced the issue ? Is it possible I need to upgrade the svelte version to get things running again on HyperTTS ?

I’m guessing this was caused by the upgrade to Svelte 4. I’ve logged the issue on Something (probably Svelte 4 upgrade) has broken exported components · Issue #2629 · ankitects/anki · GitHub. hgiesel has moved on, so we unfortunately can’t defer to him on this.

I kind of share the sentiment, I’m much more comfortable with the Python API that Anki has maintained over the years. I love the idea of being able to interact with the editor, but i’ll probably look for a more robust approach.

Just curious what were the main motivations for moving most of the editor to Svelte/Typescript, is it because displaying HTML content (which the editor will of course contain) is smoother that way ?

Thanks for your reply. After doing the “Reset window size”, the simptom disappeared.

We need web APIs for WYSIWYG editing, and it’s simpler if the entire page is in one language instead of having two different languages sending messages and state back and forth. When I said our current approach is fragile, I wasn’t talking about Svelte itself, but about the hacky way we tried to expose Anki’s components to add-ons dynamically. Python+Qt is easier for add-ons to use and extend, and we haven’t figured out the add-on story in HTML properly yet. But with the desire to share code between the platforms and all the never-ending Qt bugs, aside from the unsolved add-on story, it is an attractive proposition.

@dae , I know you’ve been very busy (I’ve been following the progress on Burn, impressive), but could you share a roadmap for the next few years of Anki in terms of technology?

Ex: Anki 3.0, back-end, front-end, etc…

I’ve been studying Rust, but I would like to know the direction Anki is heading or the vision you have.
A brainstorm that can be publicly disclosed, of course


I don’t do long-term forecasts, but it’s likely the future holds more Rust & JS code, and more of the interface shared between the different Anki clients.

There will be no 3.0, as the version numbering system is likely to change soon.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.