Native Stack is not working with react-native-windows@0.76

[achillease]

Description

After a clean react-native-windows@0.76 installation followed by the recommended installation for the native stack from the Getting Started guide, I get the following build error:

× Building Solution: C:\dev\RNWTests\node_modules\react-native-screens\windows\RNScreens\RNScreens.vcxproj(184,5...
× Build failed with message 7:10>C:\dev\RNWTests\node_modules\react-native-screens\windows\RNScreens\RNScreens.vcxproj(184,5): error : This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is C:\dev\RNWTests\windows\packages\Microsoft.Windows.CppWinRT.2.0.200316.3\build\native\Microsoft.Windows.CppWinRT.props.. Check your build configuration.

Steps to reproduce

1. install clean react-native@0.76
2. install and init react-native-windows@0.76
3. install @react-navigation/native, react-native-screens, react-native-safe-area-context, @react-navigation/native-stack, @react-navigation/elements
4. run npx @react-native-community/cli run-windows

Snack or a link to a repository

https://github.com/pcprinz/react-native-windows-tests/tree/0.76-failing-native-stack

Screens version

4.3.0

React Native version

0.76.2

Platforms

Windows

JavaScript runtime

Hermes

Workflow

React Native (without Expo)

Architecture

Paper (Old Architecture)

Build type

None

Device

None

Device model

No response

Acknowledgements

Yes

[kkafar]

Thanks for reporting! Noted. I'll try to get someone to look into this.

[dppo]

It works fine using 4.2.0

[eliekh12]

I have the same error during Windows build with react-native-webview 13.13.1 on react-native-windows@0.76 and using the new architecture.

[pedro-w]

I had this and solved it by editing NuGet.Config in the windows\ sub-directory. I moved the Nuget source above the react-native one, and added the protocol version.
i.e. from

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <config>
    <add key="repositoryPath" value="packages" />
  </config>
  <packageSources>
    <clear />
    <add key="react-native" value="https://pkgs.dev.azure.com/ms/react-native/_packaging/react-native-public/nuget/v3/index.json" />
    <add key="Nuget.org" value="https://api.nuget.org/v3/index.json" />
  </packageSources>
  <disabledPackageSources>
    <clear />
  </disabledPackageSources>
</configuration>

to

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <config>
    <add key="repositoryPath" value="packages" />
  </config>
  <packageSources>
    <clear />
    <add key="Nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3"/>
    <add key="react-native" value="https://pkgs.dev.azure.com/ms/react-native/_packaging/react-native-public/nuget/v3/index.json" />
  </packageSources>
  <disabledPackageSources>
    <clear />
  </disabledPackageSources>
</configuration>

[tux2nicolae]

@kkafar did you manage to get a windows machine? The above workaround does not seem to work for us on #2649 issue

[pedro-w]

IMO #2649 is not the same issue as this (though it is a Windows issue). Have you tried clearing the npm cache (with npx @react-native-community/cli clean)

[kkafar]

No, I haven't tended to this issue yet. Will update when I do

[ClaudiuHBann]

I encountered the same issue as #2649, but I haven't been able to resolve it. This is a major blocker for the Windows platform...

[joshholmeszonal]

@kkafar have you had any luck with this so far?

I've tried taking a look but getting stuck when trying to link RNScreens to the Fabric Example

[tux2nicolae]

@kkafar I see you have a lot of work with this library on Android and IOS and I don't want to look mean, but we really need your help on this issue and here #2649, it's just a blocker for windows platform, we can't build it at all

[joshholmeszonal]

@kkafar is this something that maybe Microsoft would be able to support with as it seems like a massive blocker for a lot of Windows builds

It looks like they're helping out with some packages like these:
microsoft/react-native-windows#14339
microsoft/react-native-windows#14341

It looks like @Yajur-Grover is supporting from Microsoft