microsoft / microsoft/react-native-windows

WACK failing in CI after bump to VS 17.11.0

Open
#13,578 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Scenario: Visual Studio Workstream: ES Compliance SFI
Dominant language
C++
Stars
17.3k
Forks
1.2k
Avg merge
1d 13h
Merged PRs (30d)
33

Description

Problem Description

In #13455 we bump the minimum required VS version to 17.11.0 but the WACK test for new apps is failing for "Supported APIs".

This doesn't seem to repro locally, the app cert passes that test fine.

Steps To Reproduce

Only repros in CI but this is what we're doing locally:

  1. Create new RNW app with old/uwp-cpp-app template
  2. Run-windows to build once for release
  3. Open in VS, build app store package for sideload and create test cert during flow
  4. Run WACK on the final msixbundle
Expected Results

No response

CLI version

14.0.0-alpha.11

Environment
- 10.0.22621.0
      - 10.0.26100.0
IDEs:
  Android Studio: Not Found
  Visual Studio:
    - 17.11.35208.52 (Visual Studio Enterprise 2022)
Languages:
  Java: Not Found
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli":
    installed: 14.0.0-alpha.11
    wanted: 14.0.0-alpha.11
  react:
    installed: 19.0.0-rc-fb9a90fa48-20240614
    wanted: 19.0.0-rc-fb9a90fa48-20240614
  react-native:
    installed: 0.76.0-nightly-20240701-9f6cb21ed
    wanted: 0.76.0-nightly-20240701-9f6cb21ed
  react-native-windows:
    installed: 0.0.0-canary.855
    wanted: 0.0.0-canary.855
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
Community Modules

No response

Target Platform Version

10.0.22621

Target Device(s)

Desktop

Visual Studio Version

Visual Studio 2022

Build Configuration

Release

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

Example failed App Cert Kit result from CI: result.zip

Example passing App Cert Kit result from local test: result-local.zip

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

Reproduce the listed release packaging and WACK flow for a new RNW app, then compare the CI result.zip with result-local.zip, focusing on the failing “Supported APIs” check. Investigate the CI-only difference after the VS 17.11.0 minimum-version bump; done means the CI App Cert Kit result passes for the generated msixbundle.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, react-native
Domain
ci-cd, operating-systems, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.