[iOS] Receiving message "Codegen didn't run for XXX", but it did + string prop is always "" #265
Unanswered
CptFabulouso
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For the following I will stick to naming convention:
Lib - the library itself
Project - the expo project using the Lib
I've created a lib (can't link, it's private repo) and when I use this lib in expo project I keep getting warning message in console "Codegen didn't run for XXX", while it seems everything is generated. During development of the lib (using bob-builder) I don't receive such messages. Files are generated in the expo project (prebuild opened in xCode).
And I don't know if it's related (but I am not able to spot any other issue) but in one of the js specs I have a string value as a component prop, but in the expo project, whatever I set the value to be, ios native code always receives empty string (
""
) value. It's not a problem during the Lib development. the spec file:The lib's package.json contains:
This means the codegen should run on the project, because I do not have the
includesGeneratedCode
field, right?If I take some example component in the Lib with lines:
then when in the expo project under "Development Pods" I open the reference to
ComponentProps
I get to.../ios/build/generated/ios/react/renderer/components/RNMapsSpec
with all the generated values - that's the codegen generated stuff, right?If I make change in the node_modules by adding some value into the js spec file and run
pod install
, this file is correctly updated. So why do I keep getting the message? I also see this line during the pod install:Running on
I made sure the Lib's example project uses same version. I've also added an expo example project into the lib. All is fine in the lib example projects.
Beta Was this translation helpful? Give feedback.
All reactions