Replies: 4 comments
-
|
@iternio/react-native-auto-play 0.1.18 was built with nitrogen and react-native-nitro-modules 0.31.10, maybe that conflicts? |
Beta Was this translation helpful? Give feedback.
-
|
At least for the example app we provide this seems to work fine |
Beta Was this translation helpful? Give feedback.
-
|
@thomas-rx did you have a chance to check this with 0.2? |
Beta Was this translation helpful? Give feedback.
-
|
I'm having the same issue. I think it might be specific to apps with |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone! I’m currently integrating @iternio/react-native-auto-play into my project, but I'm hitting a compilation wall on the iOS side. The error seems to be originating from the C++ bridge generation within Unistyles (Nitro Modules).
When I attempt to build the project after installing the library, the compiler fails with the following error:
It looks like the generated Nitrogen headers for Unistyles are unable to locate the ColorScheme definitions during the C++ bridging phase.
Here are the relevant parts of my package.json:
@iternio/react-native-auto-play: ^0.1.18
react-native-unistyles: ^3.0.22
react-native-nitro-modules: ^0.33.2
Question
Has anyone else encountered this header search path issue when using Unistyles 3 with this library?
It seems like the addition of @iternio/react-native-auto-play might be affecting how the header search paths are resolved for Nitro-generated files, or perhaps there is a version mismatch between the Nitro modules expected by the different packages.
I'd appreciate any insights or suggestions on how to point the compiler to the missing .hpp file!
Beta Was this translation helpful? Give feedback.
All reactions