Riccardo Cipolleschi

yeah, i remember. But we had to revert those changes because they were failing on other test cases, now I don't remember the specifics, unfortunately, as some weeks has passed....

I think there are different problems: - The problem highlighted by @evelant is due to pnpm and the relative patch that are specified in the podspecs, which stops working correctly...

For webview, there is already a PR pending with the fixes: https://github.com/react-native-webview/react-native-webview/pull/3231/files

I created the PR for Lottie as well: https://github.com/lottie-react-native/lottie-react-native/pull/1139

Monorepo setup are not officially supported, unfortunately. We haven't figured out a proper way to handle them. In monorepo setup the problems are likely to be the various relative path...

You should not use `cocoapods lib create` to create a library for react-native. Cocoapods is the tool we use but the base use case is to create a lib for...

The problem is that `use_frameworks` changes how the files are arranged in the disk after pod install run. Frameworks must follow a very specific structure: ``` FrameworkName '-> Headers '->...

@Slapbox symlink is stable for Metro, but not for the whole framework. My colleague that worked on simlinks for metro is now tackling monorepo scenarios, so, hopeful, we are going...

Hi @hamidhadi, thanks for the report. I'll look into it. What is the pod that is getting multiple HEADER_SEARCH_PATHS? The [link you added](https://github.com/facebook/react-native/blob/4ccd6e124278abf3c63765195715ee3ae39a769e/packages/react-native/scripts/cocoapods/codegen_utils.rb#L105) refers to a function called `get_react_codegen_spec` that...

PSA: I'll be on PTO from tomorrow until the 12th of December.