microsoft / microsoft/react-native-windows

Playgroud-composition.sln produces a build error

Open
#14,711 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area: Build Infrastructure bug Scenario: Visual Studio Workstream: Developer Experience
Dominant language
C++
Stars
17.3k
Forks
1.2k
Avg merge
1d 13h
Merged PRs (30d)
33

Description

Problem Description

Running playground-composition locally produces the following error, I think it's from Nuget package restore failing in VS but the app will still run fine.

While the app still works, this is confusing to see and should suppress this error or fix!

Image

Steps To Reproduce
  1. Run playground-composition.sln
Expected Results

No response

CLI version

npx @react-native-community/cli -v

Environment
npx @react-native-community/cli info
Community Modules

No response

Target Platform Version

None

Target Device(s)

No response

Visual Studio Version

None

Build Configuration

None

Snack, code example, screenshot, or link to a repository

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by opening and running playground-composition.sln in Visual Studio, then inspect the NuGet restore error shown during the build. Determine whether the restore failure can be fixed or suppressed without affecting the app, and verify that the solution no longer reports the confusing error while still running.

Written by the indexing model from the issue text.

Assessment

Tech stack
react-native
Domain
build-system, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.