-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot build on 0.69.21 with C# library #11345
Comments
Title of your issue says C++ library, but the implementation of that module looks like it's C#. Typo? This failure looks to be in the codegen. There was a change in 0.71 that updates the dotNet version that could affect this. Is upgrading an option? Also 0.69.6 is a bit behind. 0.69.21 is the latest (https://github.com/microsoft/react-native-windows/releases). Anyway, not confident this has been patched. But it'll help in investigation if we're dealing with latest. There has been motion in this area.
How is it being built in CI? |
@chrisglein Apologies, it is indeed a C# module. I've updated the title. I tried 0.69.21 with no luck unfortunately.
Not in the short term unfortunately. Might look into it as a last resort but it would affect our release schedule.
Here is the build command I'm using:
|
Just to clarify: This builds fine for you locally but it's only in CI that it fails? Or is it failing to build in both? |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. |
Problem Description
I'm trying to get an older library (react-native-file-viewer) to run in my project.
I made a fork to update dependencies and minimal build which you can find here.
I was running into UAP version errors until I implemented this workaround of setting an
AssetTargetFallback
property:I'm now getting the following error when attempting a build on CI:
I can't find any reference to this error outside of dotnet forums and I'm struggling to apply their use cases to mine.
I thought it could be due to the long paths, but this should be allowed:
Steps To Reproduce
Expected Results
No response
CLI version
npx react-native --version
Environment
Target Platform Version
None
Target Device(s)
No response
Visual Studio Version
Visual Studio 2019
Build Configuration
None
Snack, code example, screenshot, or link to a repository
No response
The text was updated successfully, but these errors were encountered: