microsoft / microsoft/react-native-windows
React Native windows Release build stuck after "Done copying assets"
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Problem Description
React Native windows Release build stuck at "Done copying assets"
When a new React Native Windows project is created and the release build is run, it gets stuck at "Done copying assets" and does not proceed further.
This only happens on the first release build. Subsequent release builds work fine.
This is creating a problem for CI/CD pipelines where release build is stuck as it is the first build every time a new build is triggered.
When running locally, when the build gets stuck at Done copying assets, terminating the build (Ctrl+C) and running the release build again works fine.
Here are my full build logs:
build.log
Steps To Reproduce
- npx --yes @react-native-community/cli@next init myapp --version "latest"
- cd myapp
- yarn add react-native-windows@latest
- npx react-native init-windows --overwrite --logging --template cpp-app
- npx react-native run-windows --arch x64 --release --logging
Build hangs when running the above steps:
Expected Results
The app builds successfully the first time.
CLI version
14.0.0
Environment
System:
OS: Windows 10 10.0.20348
CPU: (8) x64 Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz
Memory: 11.18 GB / 16.00 GB
Binaries:
Node:
version: 19.9.0
path: C:\Program Files\nodejs\node.EXE
Yarn:
version: 3.6.4
path: C:\Program Files\nodejs\yarn.CMD
npm:
version: 9.6.3
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
Versions:
- 10.0.10240.0
- 10.0.17763.0
- 10.0.19041.0
- 10.0.22000.0
- 10.0.22621.0
IDEs:
Android Studio: Not Found
Visual Studio:
- 17.11.35219.272 (Visual Studio Professional 2022)
- 15.9.34407.156 (Visual Studio Professional 2017)
Languages:
Java: Not Found
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.3.1
wanted: 18.3.1
react-native:
installed: 0.75.2
wanted: 0.75.2
react-native-windows:
installed: 0.75.0
wanted: latest
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Community Modules
{
"name": "myapp",
"version": "0.0.1",
"private": true,
"scripts": {
"android": "react-native run-android",
"ios": "react-native run-ios",
"lint": "eslint .",
"start": "react-native start",
"test": "jest",
"windows": "react-native run-windows",
"test:windows": "jest --config jest.config.windows.js"
},
"dependencies": {
"react": "18.3.1",
"react-native": "0.75.2",
"react-native-windows": "latest"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"@babel/preset-env": "^7.20.0",
"@babel/runtime": "^7.20.0",
"@react-native/babel-preset": "0.75.2",
"@react-native/eslint-config": "0.75.2",
"@react-native/metro-config": "0.75.2",
"@react-native/typescript-config": "0.75.2",
"@rnx-kit/jest-preset": "^0.1.17",
"@types/react": "^18.2.6",
"@types/react-test-renderer": "^18.0.0",
"babel-jest": "^29.6.3",
"eslint": "^8.19.0",
"jest": "^29.6.3",
"prettier": "2.8.8",
"react-test-renderer": "18.3.1",
"typescript": "5.0.4"
},
"engines": {
"node": ">=18"
},
"packageManager": "yarn@3.6.4"
}
Target Platform Version
10.0.22321
Target Device(s)
Desktop
Visual Studio Version
Visual Studio 2022
Build Configuration
Release
Snack, code example, screenshot, or link to a repository
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce with the listed init-windows and npx react-native run-windows --arch x64 --release --logging commands, then compare the first-build output with the attached build.log. Start at the build path around the "Done copying assets" entry and determine why the first Release build stops there. Done means a newly created project completes its first Release build without requiring a second run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- build-system, ci-cd, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100