Exception during update from v10.4 to v10.5 #10773

10 Answer(s)

• 

  0

  AI-Bot created 2 months ago

  Support Team ABP Agent

  • This is almost always caused by your NuGet sources (or packageSourceMapping) not allowing ABP Studio/CLI to see the correct LeptonX packages, so during the upgrade it ends up trying to resolve an old LeptonX installer version (5.1.1) from whatever feeds it can see, then fails with “package not found”.

  • Fix it by making sure your machine can restore Commercial LeptonX packages from the correct feed(s), then re-run the update:

  1) Verify/enable the correct NuGet sources

  Run:

  dotnet nuget list source
  

  Ensure:

  • nuget.org is enabled (public packages)
  • ABP Commercial NuGet feed is enabled and reachable (the one you normally use for Volo.* commercial packages)

  If you’re in a corporate environment, also check your user/global NuGet.Config for:

  • a broken/unreachable internal feed (can break resolution)
  • packageSourceMapping that does not map Volo.* / Volo.Abp.* to the ABP commercial feed

  (We’ve seen cases where removing a company feed from NuGet.Config fixed similar “can’t install/update ABP tool/package” issues.)

  2) Clear caches and retry

  dotnet nuget locals all --clear
  abp clean
  abp update
  

  3) If you need to upgrade immediately, pin versions explicitly

  Instead of relying on “latest” detection, run:

  abp update -v 10.5.0
  

  (If your solution uses LeptonX, also pin the LeptonX line version that matches your target ABP version, so Studio/CLI doesn’t try to resolve an unexpected older LeptonX installer.)

  4) Sanity check: confirm NuGet can actually see the package/version

  Try resolving the exact package from your configured sources:

  dotnet add <any .csproj> package Volo.Abp.LeptonXTheme.Installer --version 5.1.1
  

  • If this fails, it confirms it’s 100% a NuGet source/config visibility problem on the machine (not the ABP update logic).

  ---

  Links (verified):

  • https://abp.io/docs/latest/CLI#update
  • https://abp.io/docs/latest/studio/installation#upgrading
  • https://abp.io/docs/10.5/release-info/migration-guides/abp-10-5

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  rshapiro created 2 months ago

  I've tried several of the suggestions with no luck. More and more I'm thinking that the fact that I'm stuck on v5.1.1 of LeptonX is the issue because it's pretty old. Not sure how I get it to update

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 2 months ago

  Support Team Fullstack Developer

  Hi,

  The failure comes from a stale module import version in your solution, not from the LeptonX packages themselves.

  abp update runs in two steps: first it updates the package versions in your .csproj files (this part succeeds), then it runs a follow-up step that reads the imports section of your root .abpmdl file and, for each import, downloads that exact recorded version's .Installer package to re-sync the versions. Your .abpmdl still records Volo.Abp.LeptonXTheme at 5.1.1 (that's the LeptonX version from the ABP 10.1 era) and it was never bumped as you moved up to 10.4. So the update reaches back for Volo.Abp.LeptonXTheme.Installer 5.1.1, that request fails in your environment, and the whole update aborts. That's why you see it pulling such an old version.

  Two things to fix it:

  1. Make sure you're logged in so Studio can reach the commercial feed:

  abp login <your-username>
  

  2. Open the .abpmdl file at your solution root (<YourApp>.abpmdl), find the LeptonX import and bump its version to the one now referenced in your .csproj files after the update (for ABP 10.5 that's 5.5.0):

  "imports": {
    "Volo.Abp.LeptonXTheme": {
      "version": "5.1.1",   // change to 5.5.0
      ...
    }
  }
  

  Save and run the update again. The re-sync step will then fetch the current installer and complete.

  We'll also make this step more resilient in a next release so a stale import version can't break the whole update.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 2 months ago

  Support Team Fullstack Developer

  Hi,

  Your current question credits have been refunded.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  rshapiro created 2 months ago

  Thanks that worked now. One thing I noticed though is that the update changed all the versions for every package in the abpmdl and abpsln to unknown. Now if I try to run the update again it throws an exception indicating that package was not found

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 2 months ago

  Support Team Fullstack Developer

  Hi,

  First, to get you unblocked: restore the .abpmdl and .abpsln files from source control (their state before the update). Your packages were already upgraded to 10.5, so you keep the upgrade — only these two metadata files need fixing. After restoring, make sure there's no Unknown left in them and that the Volo.Abp.LeptonXTheme import is 5.5.0 (not the old 5.1.1).

  For the cause: abp update writes Unknown like this when the package versions aren't set directly on each PackageReference but resolved centrally. Could you confirm how your versions are managed — do you use a Directory.Packages.props (Central Package Management), and are the versions there set through an MSBuild $(...) property? If you can share your Directory.Packages.props and one .csproj, I can confirm it matches what we've reproduced.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  rshapiro created 2 months ago

  Hi,

  Yes, the packages are centrally managed. I did this based on your suggestion, after the 10.4 update, to resolve the issues of the vulnerabilites being reported by Scriban and AutoMapper. I've shared the files you requested below.

  Directory.Packages.props Whitecap.COE.HttpApi.Host.csproj

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 2 months ago

  Support Team Fullstack Developer

  Hi,

  Thanks for the files — your version setup is fine. Your Directory.Packages.props already has all the ABP packages at 10.5.0 (LeptonX at 5.5.0), so your solution is on 10.5; nothing is wrong with the actual package versions.

  So the only thing left to fix is the Unknown values that ended up in the .abpmdl and .abpsln. The cleanest way is to restore both files from source control (their state before the update). If you'd rather edit them by hand, replace every Unknown with the matching version from your Directory.Packages.props — that's 10.5.0 for the ABP packages and 5.5.0 for LeptonX. Make sure you fix both files, including the AbpFramework / AbpCommercial / AbpStudio / LeptonX entries in the .abpsln, since those feed later Studio operations.

  You don't need to re-run the update for this — your packages are already on 10.5. Please avoid running abp update again on this version, as the same follow-up step can write Unknown a second time. We're fixing that step so it can never write an unresolved version into the .abpmdl/.abpsln, and it'll be in the next release.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  rshapiro created 2 months ago

  Thanks for the help. Had already fixed things manually before my last response. Was just letting you know there is that issue.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 2 months ago

  Support Team Fullstack Developer

  Hi,

  Glad it's sorted, and thanks for flagging it. We've fixed the update so it won't write those Unknown versions again — it'll be in the next release.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel