-
Notifications
You must be signed in to change notification settings - Fork 42
Migrate to Expo-Modules for Expo SDK 43 and newer #65
Comments
+1 |
+1 |
1 similar comment
+1 |
I found a temporary workaround, which is to use Expo's classic build service, instead of their newer EAS build service. Unfortunately, the classic build service is deprecated and goes offline in about 160 days. So I'm reaching out to them and see if they can get EAS build to work like classic in this regard, or hold off on deprecating classic. |
Update: The EAS guys gave a kind of "not my problem" response. |
For yarn I found the following {
// ... other package.json options ...
"resolutions": {
"@unimodules/react-native-adapter": "./node_modules/expo"
}
} |
I think this should be fixable by removing the dependency on the unimodules and instead updating to the expo modules. Not sure why it is needed to depend on the unimodules in the first place, couldn't we directly depend on expo-random? @kevlened would you accept a PR for this change? |
@TimoGlastra |
Using React : 17.0.2
react-native: 0.67.0
Expo SDK: 44 (Bare)
We are using this library due to the webcrypto polyfill.
This library is using expo unimodules, which causes a duplicate symbol issue on iOS, UMReactNativeAdapter belongs to expo unimodules. Could we get a version in which we don't depend on unimodules please? I would contribute but I currently have no idea how you have it set up for react-native support. No issues on Android
The text was updated successfully, but these errors were encountered: