Nuget restore v1.0.5 failing

Nuget restore v1.0.5 failing

Description of the issue

Nuget restore step failing for access to path denied. See log message below.


Where did the issue happen?

Visual Studio Mac Stable Stack

Which build Step causes the issue and which version of the step?



  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : YES
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? : Every time
  • Does upgrading the build Step to the latest version help? : NO (on latest version of the step)
  • When did the issue start? : 7 April 2018

Build log

Please copy paste the build’s URL here (or if the issue happens somewhere else then the full logs), or if you can’t share the url / log here then send the url or full log through a private channel (e.g. email - ), with a link to the related Discuss issue.

Enabled bitrise support for

Unable to find version '1.0.0' of package 'Screenmedia.Plugin.Alert'.
  /Users/vagrant/.nuget/packages/: Package 'Screenmedia.Plugin.Alert.1.0.0' is not found on source '/Users/vagrant/.nuget/packages/'. Package 'Screenmedia.Plugin.Alert.1.0.0' is not found on source ''. Failed to fetch results from V2 feed at ''Screenmedia.Plugin.Alert',Version='1.0.0')' with following message : Access to the path "/Users/vagrant/.local/share/NuGet/v3-cache" is denied.
  Access to the path "/Users/vagrant/.local/share/NuGet/v3-cache" is denied.
1 Like

Hi @tomcurran,

Thanks for reporting the issue, we’re working on a step update to fix this!

In the meantime the workaround is to specify the nuget version in the step instead of setting it to “latest”.

We’ll let you know as soon as the fix is released, if you’d have any questions just let us know! :slight_smile:

1 Like


We have just released a new version of NuGet restore step (1.0.6) which contains a fix for this problem.
It should resolve this issue.


Looks like the update has fixed our issue. Thanks!!

1 Like

Awesome to hear, thanks for reporting @tomcurran! :slight_smile: :tada:

This topic was automatically closed after 13 days. New replies are no longer allowed.