-
Notifications
You must be signed in to change notification settings - Fork 195
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
[iOS] Library project generated for Turbo Module fails to build with React Native 0.77.0 #755
Comments
Might be related to #754 — exploring my project I see that Codegen generates some |
Same issue,
EDIT: I now found this: https://github.com/reactwg/react-native-new-architecture/blob/main/docs/codegen.md#including-generated-code-into-libraries so I'm no longer sure :) |
I just created a new library and also faced duplicated symbols. I guess there is something about the template that breaks. That being said I also faced an issue with included codegen code in the distribution facebook/react-native-website#4460 This was also discussed internally in the react-native maintainer discord and indeed the documentation is not clear. Codegen code can break between versions, so builder-bob should not turn on this IMO. In any case, if you guys have a workaround to get builder-bob working with the C++ template again let me know. Maybe it's just a case of downgrading to 0.76.6. |
@ospfranco It seems that |
Description
Linker reports duplicated symbols, in my current understanding they happen because of a name clash between the code generated by
codegen
for the library, and some similar code generated bycodegen
for the app itself (the screenshot is from a library I maintain, after resetting its scaffolding with the latestcreate-react-native-library
version, and [email protected]; but I got the same problem with just new project created bycreate-react-native-library
, with no subsequent changes):Packages
Selected options
N/A
Link to repro
https://github.com/birdofpreyru/react-native-fs/tree/dev-v2.31
Environment
N/A
The text was updated successfully, but these errors were encountered: