You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are aware of some issues that are preventing pure C++ Modules to work well on Android, when developed locally in the app.
23
+
Pure C++ modules consumed as external libraries works well on Android.
24
+
25
+
These issues started from version 0.76.2 and are still persisting in version 0.76.5.
26
+
27
+
We found the root cause for the issue (see [#48298](https://github.com/facebook/react-native/issues/48298) and [#48340](https://github.com/facebook/react-native/pull/48340)), and we are aiming to fix in 0.76.6.
28
+
:::
29
+
21
30
## 1. Create the JS specs
22
31
23
32
Pure C++ Turbo Native Modules are Turbo Native Modules. They need a specification file (also called spec file) so that Codegen can create the scaffolding code for us. The specification file is also what we use to access the Turbo Native Module in JS.
We are aware of some issues that are preventing pure C++ Modules to work well on Android, when developed locally in the app.
23
+
Pure C++ modules consumed as external libraries works well on Android.
24
+
25
+
These issues started from version 0.76.2 and are still persisting in version 0.76.5.
26
+
27
+
We found the root cause for the issue (see [#48298](https://github.com/facebook/react-native/issues/48298) and [#48340](https://github.com/facebook/react-native/pull/48340)), and we are aiming to fix in 0.76.6.
28
+
:::
29
+
21
30
## 1. Create the JS specs
22
31
23
32
Pure C++ Turbo Native Modules are Turbo Native Modules. They needs a specification file (also called spec file) so that Codegen can create the scaffolding code for us. The specification file is also what we use to access the Turbo Native Module in JS.
0 commit comments