Windows Build Failed for Android #32957
Labels
CLI
Versioned Expo CLI -- `npx expo start`
invalid issue: react-native-core
Issues related to react-native-core don't belong in this repository
Comments
Vijayabaskar56
added
CLI
|
I had the same error today and solved it |
brentvatne
added
the
invalid issue: react-native-core
|
Hi there! It looks like your issue concerns code in react-native core, rather than Expo tools. We recommend posting this issue directly to the react-native repository. |
|
thank you @FouadMagdy01! folks should refer to your pr if they come across this issue. facebook/react-native#47641 |
|
thank you @FouadMagdy01 , Will look into your solution |
facebook-github-bot
pushed a commit
to facebook/react-native
that referenced
this issue
Nov 18, 2024
Summary: This pull request addresses a CMake configuration issue where an invalid escape character in file paths caused the build process to fail. Specifically, it resolves the issue in the React Native CMake configuration file where the path separator was incorrectly handled, leading to an error in the build system. the issue is in [This Issue](expo/expo#32955) and [This](expo/expo#32957) ## Changelog: <!-- Help reviewers and the release process by writing your own changelog entry. Pick one each for the category and type tags: [ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message For more details, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [INTERNAL] [FIXED] - Corrected invalid escape character in CMake path handling Pull Request resolved: #47641 Test Plan: To test the changes, I performed the following steps: 1. Cloned the repository and checked out the `fix-cmake-invalid-escape-character` branch. 2. Ran the CMake build on a Windows environment where the issue was previously occurring. 3. Verified that the build process completed successfully without the "invalid character escape" error. 4. Ensured that the path handling now works correctly in CMake on Windows platforms. Reviewed By: rshest Differential Revision: D66073896 Pulled By: cipolleschi fbshipit-source-id: bd2a71bb00ce5c5509ed403842c995c32f58f91d
|
@FouadMagdy01 youre a living legend man |
blakef
pushed a commit
to facebook/react-native
that referenced
this issue
Nov 21, 2024
Summary: This pull request addresses a CMake configuration issue where an invalid escape character in file paths caused the build process to fail. Specifically, it resolves the issue in the React Native CMake configuration file where the path separator was incorrectly handled, leading to an error in the build system. the issue is in [This Issue](expo/expo#32955) and [This](expo/expo#32957) ## Changelog: <!-- Help reviewers and the release process by writing your own changelog entry. Pick one each for the category and type tags: [ANDROID|GENERAL|IOS|INTERNAL] [BREAKING|ADDED|CHANGED|DEPRECATED|REMOVED|FIXED|SECURITY] - Message For more details, see: https://reactnative.dev/contributing/changelogs-in-pull-requests --> [INTERNAL] [FIXED] - Corrected invalid escape character in CMake path handling Pull Request resolved: #47641 Test Plan: To test the changes, I performed the following steps: 1. Cloned the repository and checked out the `fix-cmake-invalid-escape-character` branch. 2. Ran the CMake build on a Windows environment where the issue was previously occurring. 3. Verified that the build process completed successfully without the "invalid character escape" error. 4. Ensured that the path handling now works correctly in CMake on Windows platforms. Reviewed By: rshest Differential Revision: D66073896 Pulled By: cipolleschi fbshipit-source-id: bd2a71bb00ce5c5509ed403842c995c32f58f91d
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Build Task is Failing Due to Path difference like "" for this Character , sepculating due to difference in the Path Variation on the Windows
FAILURE: Build failed with an exception.
What platform(s) does this occur on?
Android
SDK Version
52
Environment
Minimal reproducible example
Here is the Minial Reproduction of the Bug Cointaing Repo
https://github.com/Vijayabaskar56/expo-windows-build-failed.git
Just a Bare new expo application , Failed during Development Build ,
Here is the Full Detailed Log , With
The text was updated successfully, but these errors were encountered: