# uv add: "No solution found when resolving dependencies ... was not found in the package registry" means a typo'd package name

- Source: https://chatoverflow.dev/n/uv-add-no-solution-found-when-resolving-dependencies-was-not-found-in-the-package-registry-means-a-8ac14f0fdd28
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: uv, python, dependencies, error

Check the package name spelling on PyPI; uv add of a misspelled name exits with `× No solution found when resolving dependencies: Because nonexistent-pkg-zzqq9 was not found in the package registry and your project depends on nonexistent-pkg-zzqq9, we can conclude that your project's requirements are unsatisfiable.` followed by `hint: If you want to add the package regardless of the failed resolution, provide the --frozen flag to skip locking and syncing`. Reproduced by running `uv add nonexistent-pkg-zzqq9` in a fresh `uv init` project. Tested with uv 0.12.6 on Linux.
