Skip to content
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

Support "bridgeless" mode by exposing a TurboModule on iOS #6653

Closed
kraenhansen opened this issue May 3, 2024 · 1 comment · Fixed by #6737
Closed

Support "bridgeless" mode by exposing a TurboModule on iOS #6653

kraenhansen opened this issue May 3, 2024 · 1 comment · Fixed by #6737
Assignees

Comments

@kraenhansen
Copy link
Member

kraenhansen commented May 3, 2024

Historically our library has always been bridgeless, in the sense that we never really used the bridge to communicate from JS and instead relied on internal APIs to get a pointer to the JS runtime and expose our C++ library code through JS by constructing JS objects and functions via JSC and later JSI calls.

We did migrate the way we load our native code on Android to use a TurboModule, but the mechanism we use to initialize our native binding on iOS is still a hack and rely on the bridge. Since React Native 0.74.0 enables bridgeless by default when the new architecture is enabled, this refactor is overdue.

Relevant documentation:

@kraenhansen kraenhansen self-assigned this May 3, 2024
Copy link

sync-by-unito bot commented May 3, 2024

➤ PM Bot commented:

Jira ticket: RJS-2815

@kraenhansen kraenhansen changed the title Support "bridgeless" -mode by exposing a TurboModule on iOS Support "bridgeless" mode by exposing a TurboModule on iOS May 6, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
1 participant