Failed to restore the NuGet Packages

[MaxiBoether]

Hi,

I installed react-native-windows according to your guide, but whenever I run the command react-native run-windows it tells me:

Failed to restore the NuGet Packages

Why does that happen? I am running Windows 8.1 and tried non-administrator and administrator permissions.

[rozele]

Can you run:

.\node_modules\react-native-windows\local-cli\runWindows\.nuget\nuget.exe restore .\<yourapp>\ReactNative.sln

From your project root and paste the output. (replace with the folder containing the solution file.

[MaxiBoether]

node_modules\react-native-windows\local-cli\runWindows\.nuget\nuget.exe restore windo
ws\mTable.sln

MSBuild auto-detection: using msbuild version '4.0' from 'C:\Windows\Microsoft.N
ET\Framework\v4.0.30319'.
C:\Program Files (x86)\MSBuild\Microsoft\WindowsXaml\v14.0\Microsoft.Windows.UI
.Xaml.Common.targets(6,18): error MSB4086: Es wurde versucht, einen numerischen
 Vergleich für "$(TargetPlatformMinVersion)" auszuführen, der nicht zu einer Za
hl, sondern zu 10.0.10240.0 ausgewertet wird in der '$(TargetPlatformIdentifier
)' == 'UAP' And '$(TargetPlatformMinVersion)' != '' And '$(TargetPlatformMinVer
sion)' > '10.0.10587.0'-Bedingung. [F:\Eigene Dateien\Eigene Dokumente\Arbeitsp
latz\Programmierung\Apps\mTable\windows\mTable\mTable.csproj]
C:\Program Files (x86)\MSBuild\Microsoft\WindowsXaml\v14.0\Microsoft.Windows.UI
.Xaml.Common.targets(6,18): error MSB4086: Es wurde versucht, einen numerischen
 Vergleich für "$(TargetPlatformMinVersion)" auszuführen, der nicht zu einer Za
hl, sondern zu 10.0.10240.0 ausgewertet wird in der '$(TargetPlatformIdentifier
)' == 'UAP' And '$(TargetPlatformMinVersion)' != '' And '$(TargetPlatformMinVer
sion)' > '10.0.10587.0'-Bedingung. [F:\Eigene Dateien\Eigene Dokumente\Arbeitsp
latz\Programmierung\Apps\mTable\node_modules\react-native-windows\ReactWindows\
ReactNative\ReactNative.csproj]

The German error message (I'm sorry for that, my system lang is German) can be translated to

It was tried to do a numeric comparison for $(TargetPlatformMinVersion) which didn't result in a number, but in 10.0.10240.0 in the '$(TargetPlatformIdentifier
)' == 'UAP' And '$(TargetPlatformMinVersion)' != '' And '$(TargetPlatformMinVer
sion)' > '10.0.10587.0'- condition

[MaxiBoether]

After quick research on the error number, I found this StackExchange Thread: http://stackoverflow.com/questions/38181160/error-running-msbuild

The suggested fix to run
call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat"

Doesn't create an error when running

node_modules\react-native-windows\local-cli\runWindows\.nuget\nuget.exe restore windo
ws\mTable.sln

again! But the react-native run-windows command still produces an error:

F:\Eigene Dateien\Eigene Dokumente\Arbeitsplatz\Programmierung\Apps\mTable>react
-native run-windows
Restoring NuGet packages
MSBuild auto-detection: using msbuild version '14.0' from 'C:\Program Files (x86
)\MSBuild\14.0\bin'.
Restoring packages for F:\Eigene Dateien\Eigene Dokumente\Arbeitsplatz\Programmi
erung\Apps\mTable\node_modules\react-native-windows\ReactWindows\ReactNative\pro
ject.json...
Restoring packages for F:\Eigene Dateien\Eigene Dokumente\Arbeitsplatz\Programmi
erung\Apps\mTable\windows\mTable\project.json...
Committing restore...
Committing restore...
F:\Eigene Dateien\Eigene Dokumente\Arbeitsplatz\Programmierung\Apps\mTable\windo
ws\mTable\mTable.csproj
Restore completed in 1283ms.
F:\Eigene Dateien\Eigene Dokumente\Arbeitsplatz\Programmierung\Apps\mTable\node_
modules\react-native-windows\ReactWindows\ReactNative\ReactNative.csproj
Restore completed in 1283ms.

NuGet Config files used:
    C:\Users\Maximilian\AppData\Roaming\NuGet\NuGet.Config
    C:\ProgramData\nuget\Config\Microsoft.VisualStudio.Offline.config

Feeds used:
    https://api.nuget.org/v3/index.json
    C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\

Building F:/Eigene Dateien/Eigene Dokumente/Arbeitsplatz/Programmierung/Apps/mTa
ble/windows/mTable.sln
FEHLER: Der angegebene Registrierungsschl?ssel bzw. Wert wurde nicht gefunden.
Found MSBuild v14.0 at C:\Program Files (x86)\MSBuild\14.0\bin
Found MSBuild v12.0 at C:\Program Files (x86)\MSBuild\12.0\bin\amd64\
Found MSBuild v4.0 at C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
Building Solution: F:/Eigene Dateien/Eigene Dokumente/Arbeitsplatz/Programmierun
g/Apps/mTable/windows/mTable.sln
Build configuration: Debug
Build platform: x86
Build failed with message Error: Command failed: "C:\Program Files (x86)\MSBuild
\14.0\bin\msbuild.exe" F:/Eigene Dateien/Eigene Dokumente/Arbeitsplatz/Programmi
erung/Apps/mTable/windows/mTable.sln /clp:NoSummary;NoItemAndPropertyList;Verbos
ity=minimal /nologo /p:Configuration=Debug /p:Platform=x86
. Check your build configuration.

My guess is that my path contains whitespaces (my bad) and thus it needs quotations which the script doesn't do.

[MaxiBoether]

#582 (please note that this pulll request doesn't handle the problem of error MSB4086, I don't know what causes this)

[rozele]

@Mayesters What version of Windows 10 SDK do you have installed?

[MaxiBoether]

I tried Build 10586, which Visual Studio 2015 didn't accept, thus installing 14393. Is is possible that Windows 8.1 is not suitable for Windows UWP development?

[rozele]

I haven't tried Windows 8.1, but in theory nothing should be blocking UWP development (it meets the requirements for the Windows 10 SDK). I also haven't upgraded yet to the 14393 SDK. I'm still using 10586.

[matthargett]

is it possible to have different AppVeyor builds with different SDKs installed?

[rozele]

Which SDKs are you referring to? Having a build for each version of the Windows 10 SDK? Or having a build for 7/8/10?

[matthargett]

Having a build for each version of the Windows 10 SDK. It seems like that and slightly older npm installs are the main issues that keep coming up -- despite the updates to the README. Let me know if it's even possible with the AppVeyor config and I can poke around.

[rozele]

This seems like a configuration issue with Visual Studio. Not sure why Visual Studio 2015 would not accept the 10586 build as you stated above. Closing out this issue, please re-open with new details and a stable repro if this is still a problem.