Is static linking required? (Expo) #219
-
The docs now mention that you need to enable static linking for iOS. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hey, yes - static linking is required. The example app is outdated, I need to update it to a newer one. In 0.5.0 (https://github.com/okwasniewski/react-native-bottom-tabs/releases/tag/v0.5.0) I've introduced another native dependency to handle SVG support. This dependency doesn't define modules (and all of the cocoapods quirks that go with it) require us to enable static linking. There is a workaround you can do if you really don't want to enable static linking: https://github.com/okwasniewski/cocoapods-swift-modular-headers You can create a simple Expo config plugin to inject this plugin into your Podfile and this will solve the issue with modular headers. Expo does this in their autolinking but only for Expo Modules. |
Beta Was this translation helpful? Give feedback.
Hey, yes - static linking is required.
The example app is outdated, I need to update it to a newer one. In 0.5.0 (https://github.com/okwasniewski/react-native-bottom-tabs/releases/tag/v0.5.0) I've introduced another native dependency to handle SVG support. This dependency doesn't define modules (and all of the cocoapods quirks that go with it) require us to enable static linking.
There is a workaround you can do if you really don't want to enable static linking: https://github.com/okwasniewski/cocoapods-swift-modular-headers
You can create a simple Expo config plugin to inject this plugin into your Podfile and this will solve the issue with modular headers. Expo does this in their autolin…