microsoft / microsoft/react-native-windows

Integration tests broken with 'double-conversion/double-conversion.h'

Open
#11,644 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Integration Follow-up Workstream: Test Coverage
Dominant language
C++
Stars
17.3k
Forks
1.2k
Avg merge
1d 13h
Merged PRs (30d)
33

Description

Problem Description

Recent integration pulls in Add JSI<->C++ bridging conversion for folly::dynamic which breaks our Microsoft.ReactNative.IntegrationTests with the error Error C1083: Cannot open include file: 'double-conversion/double-conversion.h': No such file or directory even when specifying the include file. File is currently overwritten, but we should find the reason and fix it upstream.

Steps To Reproduce
  1. Remove override
  2. Try to build integration tests
Expected Results

tests should build fine

CLI version

npx react-native -v

Environment
npx react-native info
Target Platform Version

10.0.19041

Target Device(s)

Desktop

Visual Studio Version

Visual Studio 2022

Build Configuration

Debug

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 removing the current override and rebuilding Microsoft.ReactNative.IntegrationTests to reproduce the missing double-conversion/double-conversion.h include. Trace the recent JSI-to-C++ bridging conversion integration and determine why the header is unavailable even when its include path is specified. Done means the integration tests build successfully without the override and the underlying fix is addressed upstream.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, react-native
Domain
build-system, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.