Issue installing on MacOS Sequoia 15.2

Anki Help
1

Checking for updates…

Unable to check for Anki versions. Please check your internet connection.

Error: Failed to run (2): /Applications/Anki.app/Contents/MacOS/uv run --no-project --no-config --managed-python --with pip-system-certs,requests[socks] --python 3.13.5 /Applications/Anki.app/Contents/Resources/versions.py: warning: Failed to patch the install name of the dynamic library for /Users/liamleslie-greene/.local/share/uv/python/cpython-3.13.5-macos-aarch64-none/bin/python3.13. This may cause issues when building Python native extensions.

error: Querying Python at `/Users/liamleslie-greene/.local/share/uv/python/cpython-3.13.5-macos-aarch64-none/bin/python3.13` failed with exit status signal: 9 (SIGKILL)

Press enter to close…

2

Please look at the previous topics about the “Failed to patch the install name of the dynamic library” error message and see if any of the suggestions in those topics might help.

(The search brings up issues with Conda/Anaconda/python architecture mismatches. Also, if you previously migrated the contents of an old Intel-based Mac onto a new Apple silicon Mac, that might explain the architecture mismatch.)

1 Like
3

Already checked these threads, no solution found. Anaconda is not installed, and it is a fresh install of Anki from the website.

4
  • The threads suggested a number of possible fixes and workarounds. Which specific ones did you try?
  • What model of Mac are you using? Is it Intel or Apple Silicon?
  • When you got this computer, did you migrate the contents from your old computer?
  • Have you ever used pip or homebrew to install things on your system?
  • Have you ever previously installed python on your system?
5

Apple Silicon, M4

Yes, migrated from my old system, and I have used pip and homebrew. Python has been previously installed.

6

(I’m hoping that other people will chime in with advice, because I’m not an expert in fixing these sorts of issues.)

For now, in Terminal could you please try running which install_name_tool and then file <fully qualified path of install_name_tool>?

% which install_name_tool
/usr/bin/install_name_tool

% file /usr/bin/install_name_tool
/usr/bin/install_name_tool: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64e:Mach-O 64-bit executable arm64e]
/usr/bin/install_name_tool (for architecture x86_64):	Mach-O 64-bit executable x86_64
/usr/bin/install_name_tool (for architecture arm64e):	Mach-O 64-bit executable arm64e

One possiblity is that an Intel-only version of install_name_tool might be installed and being run on your system. The above commands look for the specific copy of install_name_tool that gets used and then checks to see what architecture it is for. (From the above output on my system, I am running /usr/bin/install_name_tool, and it is a universal binary that runs on both Intel and Apple Silicon systems.)