failed to select a version for `arrayref`

[NotKimAtALL]

build Rust app, run cargo check will get the following errors:

cargo add pdf-inspector
    Updating git repository `https://github.com/firecrawl/pdf-inspector`
      Adding pdf-inspector (git) to dependencies
             Features as of v1.15.0:
             - model-cache
             - model-download
             - ocr
             - ocr-oar
             - pyo3
             - python
             - render-pdfium
             - vision
    Updating crates.io index
    Updating git repository `https://github.com/firecrawl/pdf-inspector`
error: failed to select a version for `arrayref`.                                                                                                           
    ... required by package `tiny-skia v0.11.0`
    ... which satisfies dependency `tiny-skia = "^0.11"` of package `sctk-adwaita v0.7.0`
    ... which satisfies dependency `sctk-adwaita = "^0.7.0"` of package `winit v0.29.4`
    ... which satisfies dependency `winit = "^0.29.4"` of package `eframe v0.28.0`
    ... which satisfies dependency `eframe = "^0.28"` of package `pdf_purifier v0.1.0 (C:\Users\nkaa\rs_p1)`
versions that meet the requirements `^0.3.6` are: 0.3.10

all possible versions conflict with previously selected packages

[mathurshubham]

I dug into this and pdf-inspector isn't actually involved in the arrayref conflict — it doesn't depend on arrayref (or on winit/sctk-adwaita/tiny-skia) under any feature or platform. The only thing that pulls arrayref in your project is your own eframe 0.28 chain: eframe → winit → sctk-adwaita → tiny-skia → arrayref.

What actually happened: your existing Cargo.lock had arrayref/tiny-skia 0.11.0 pinned to versions that were later yanked — that's why cargo reports only 0.3.10 as available for ^0.3.6. Running cargo add pdf-inspector triggered an index refresh and re-resolve, and cargo couldn't reconcile the stale pins with the rest of your frozen eframe subtree — hence the "all possible versions conflict with previously selected packages" failure. Adding pdf-inspector just happened to be the action that forced the re-resolution.

Fix on your side, no pdf-inspector change needed:

• cargo update -p arrayref (or cargo update -p tiny-skia) to move off the yanked pin, or
• delete Cargo.lock and re-run cargo check, then cargo add pdf-inspector.

On a clean resolve this combination works fine — I reproduced eframe = "0.28" + pdf-inspector (default and full feature sets) and it locks cleanly to arrayref 0.3.9 / tiny-skia 0.11.4. This one can likely be closed as not a pdf-inspector bug, but happy to help if the cargo update doesn't clear it.

[NotKimAtALL]

Thanks for the detailed investigation and explanation. The issue has been resolved, and I can confirm that pinning arrayref to 0.3.9 works as expected.

Really appreciate your help in tracking down the root cause and clarifying that this wasn't a pdf-inspector issue.