Package is not found in the following primary source

Question

I have a build pipeline set up to create Nuget packages and publish them to a feed in artifacts.

I was able to use the feed successfully.

However when I ran the pipeline again, causing the packages to publish again I am not able to update the consuming project successfully.

Even though I can see the correct new version number in the Package Manager (Visual Studio -> Tools-> Nuget Package Manager -> Manage Nuget Packages for solution)

When I click install I get an error

Package '<mypackagename with version number>' is not found in the following primary source

<correct feed nuget/v3/index.json> Please verify all your online package sources are available (OR) package id, version are specified correctly.

score 203 · Answer 1 · answered Jul 11 '19 at 20:54

203

This is caused by caching. If you don't want to wait like the above answer suggested, just clear Nuget caches by going to Tools -> Options -> Nuget -> General and click on the "Clear All Nuget Cache(s)" button.

answered Jul 11 '19 at 20:54

noriMonsta

2,507
2
11
7

Thanks I will try that next time it bothers me. – Kirsten Jul 11 '19 at 22:14
4

For those who dont want to wait, this is the fix. – Darth Scitus Dec 13 '19 at 05:05
1

Perfect answer. Should be the accepted answer. – stigzler Jun 17 '21 at 15:14
I don't understand why are they even caching because it definitely isn't working since it takes 10-15 seconds anyway for that error to appear – Sasino Jan 06 '23 at 21:35
1

Worked for me. Why is Nuget so full of these idiosyncracies and gotchas? – Steve Smith Apr 03 '23 at 13:28

score 36 · Accepted Answer · answered Feb 17 '19 at 23:35

36

I waited another 5 minutes and the problem went away. Maybe the version shows before the publishing is complete.

answered Feb 17 '19 at 23:35

Kirsten

15,730
41
179
318

5

Just had the same time delay on our private NuGet feed hosted on Azure DevOps. Took 10 minutes for the package to show up. – tomRedox Apr 25 '19 at 16:41
7

INDEED! THIS IS A REALLY OBNOXIOUS THING! The OP states they can see the updated version in their 'Package Manager Console' - but I think they mean the 'Nuget Package Manager' browsing UI. I too can see my updated package listed there but then when I attempt to run the `Install-Package` command it fails. – bkwdesign Jun 03 '19 at 16:09
Thanks, It has been a while since this bothered me, but I think you must be right. I corrected the question. ( What does OP stand for? ) – Kirsten Jun 03 '19 at 21:53
3

I'm afraid that 5 min is very optimistic. I've uploaded the package 8 minutes ago using release pipeline but it is still `invisible` by the VS. The strange thing is that `https://pkgs.dev.azure.com/orgid/_packaging/feedguid/nuget/v3/query2/` show correct version for my package. Do you know how can I adjust the time required to refresh the package ? – oleksa Feb 05 '20 at 16:23
2

@Kirsten: OP stands for Original Poster – jmoreno Dec 02 '22 at 01:34

Waqas Javaid · Answer 3 · 2021-06-17T11:22:30.220

8

After 4 hours struggle I found solution here https://www.grapecity.com/componentone/docs/uwp/online-getting-started/config-nugetpackage.html

Tools > Options > NuGet Package Manager > Package Sources. > Click add button and add following one by one...

nuget.org https://www.nuget.org/api/v2/

GrapeCity http://nuget.grapecity.com/nuget

edited Jun 17 '21 at 11:22

answered Jun 17 '21 at 11:15

Waqas Javaid

155
1
10

1

Nuget online repo link was missing. Thank you! – SiL3NC3 Mar 04 '22 at 22:00

score 6 · Answer 4 · answered Sep 02 '19 at 08:49

6

You have to check your package source I think the default is

Microsoft Visual Studio Offline Packages

So, you can change that to "All".

answered Sep 02 '19 at 08:49

1392023093user

1,047
4
21
37

score 1 · Answer 5 · answered Oct 02 '20 at 13:44

1

In my case I did not include the url from nuget.org in the Package Source. Therefore add the url from nuget.org in "Tools-> Options-> NuGet Package Manager-> Package Sources" and the whole thing started to work. for more details can visit this blog

answered Oct 02 '20 at 13:44

AgungCode.Com

677
6
9

score 0 · Answer 6 · answered Jul 21 '20 at 19:10

0

In my case there was a private network folderbased nuget repository listed in my sources. And at the moment it was not available. I unchecked it in "Tools->Options->NuGet Package Manager->Package Sources" and the whole thing started to work

answered Jul 21 '20 at 19:10

user3088037

83
6

score -2 · Answer 7 · answered Aug 14 '21 at 18:40

-2

Restarting Visual Studio 2019 Community fixed the issue for me.

answered Aug 14 '21 at 18:40

RMuesi

2,852
1
24
27

Package is not found in the following primary source

7 Answers7

Linked