Skip to content

Conversation

cipolleschi
Copy link
Contributor

@cipolleschi cipolleschi commented Aug 27, 2025

Summary:

To be able to handle cocoapods USE_FRAMEWORKS with both dynamic/static linkage and precompiled we needed a common way to resolve this.

The issue was that when using precompiled and USE_FRAMEWORKS our precompiled framework caused the resulting Pods project to only include header files - hence there where no need to change the header_mappings_dir which a lot of the podspecs did.

When using precompiled and building with frameworks (USE_FRAMEWORKS) we need to explicitly add the correct path to ReactCodegen when calling create_header_search_path_for_frameworks to ensure libraries can access their codegen files.

  • Added method that handles this in a generic way
  • Replaced logic for resolving header mappings and module name using the new method resolve_use_frameworks in all podspecs.
  • Add an explicit check to make sure we add the correct path when using frameworks and the pod is ReactCodegen.
  • Added includes in the NativeCXXModuleExample.cpp file to test this.

Changelog:

[IOS] [FIXED] - Fixed using USE_FRAMEWORKS (static/dynamic) with precompiled binaries

Test Plan:

Build RN-Tester with USE_FRAMEWORKS static and dynamic

Tests ran:

✅ Build with source and no USE_FRAMEWORKS
✅ Build with source and USE_FRAMEWORKS = static
🔴 Build with source and USE_FRAMEWORKS = dynamic

Undefined symbols for architecture arm64:
"facebook::react::oscompat::getCurrentProcessId()", referenced from:
facebook::react::jsinspector_modern::HostTargetTraceRecording::start() in HostTargetTraceRecording.o
ld: symbol(s) not found for architecture arm64
clang++: error: linker command failed with exit code 1 (use -v to see invocation)

This fails on main as well.

FIXED when adding dep on React-oscompat when USE_FRAMEWORKS=dynamic:

✅ Build with source and USE_FRAMEWORKS = dynamic

✅ Build with precompiled and no USE_FRAMEWORKS
✅ Build with precompiled and USE_FRAMEWORKS = static
✅ Build with precompiled and USE_FRAMEWORKS = dynamic

chrfalch and others added 6 commits August 27, 2025 09:10
To be able to handle cocoapods USE_FRAMEWORKS with both dynamic/static linkage and precompiled we needed a common way to resolve this.

The issue was that when using precompiled and USE_FRAMEWORKS our precompiled framework caused the resulting Pods project to only include header files - hence there where no need to change the header_mappings_dir which a lot of the podspecs did.

A method was added that handles this in a common way.
Replaced logic for resolving header mappings and module name using the new method `resolve_use_frameworks` in all podspecs.

Also added `React-oscompat` dependency on `React-jsiinspector_modern` which failed when linkage was "dynamic".
When using precompiled and building with frameworks (USE_FRAMEWORKS) we need to explicitly add the correct path to ReactCodegen when calling `create_header_search_path_for_frameworks` to ensure libraries can access their codegen files.

This commit adds an explicit check to make sure we add the correct path when using frameworks and the pod is ReactCodegen.

Added includes in the NativeCXXModuleExample.cpp file to test this.
Co-authored-by: Riccardo Cipolleschi <cipolleschi@meta.com>
After a github `suggestion` we had a superfluous `end`. Sorry for that.
@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Aug 27, 2025
@cipolleschi cipolleschi changed the base branch from main to 0.81-stable August 27, 2025 08:17
@cipolleschi cipolleschi marked this pull request as ready for review August 27, 2025 08:18
@motiz88 motiz88 merged commit 6526a98 into 0.81-stable Aug 27, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. p: Facebook Partner: Facebook Partner Pick Request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants