Open aureat opened 2 months ago
Update
The duplicate symbols are coming from @unimodules/react-native-adapter
, depended on by isomorphic-webcrypto
.
Here's the appropriate code from my package-lock.json
:
"node_modules/isomorphic-webcrypto": {
"version": "2.3.8",
"resolved": "https://registry.npmjs.org/isomorphic-webcrypto/-/isomorphic-webcrypto-2.3.8.tgz",
"integrity": "sha512-XddQSI0WYlSCjxtm1AI8kWQOulf7hAN3k3DclF1sxDJZqOe0pcsOt675zvWW91cZH9hYs3nlA3Ev8QK5i80SxQ==",
"optional": true,
"dependencies": {
"@peculiar/webcrypto": "^1.0.22",
"asmcrypto.js": "^0.22.0",
"b64-lite": "^1.3.1",
"b64u-lite": "^1.0.1",
"msrcrypto": "^1.5.6",
"str2buf": "^1.3.0",
"webcrypto-shim": "^0.1.4"
},
"optionalDependencies": {
"@unimodules/core": "*",
"@unimodules/react-native-adapter": "*",
"expo-random": "*",
"react-native-securerandom": "^0.1.1"
}
},
its possible to remove the dependecy of isomorphic-webcrypto in DidCom ? Cause its need to Migrate to Expo-Modules for Expo SDK 43 and newer, and not use unimodules-core but expo-modules instead.
its possible to remove the dependecy of isomorphic-webcrypto in DidCom ? Cause its need to Migrate to Expo-Modules for Expo SDK 43 and newer, and not use unimodules-core but expo-modules instead.
sadly we can't remove isomorphic-webcrypto as we don't have an alternative yet
@vadimchilinciuc @aureat maybe if enough people insist here: https://github.com/paulmillr/noble-ciphers/issues/12 we could get a pure JS implementation. I believe AESKW is the last algorithm for which we don't have multi-platform alternatives and that is a requirement in didcomm
Bug When you run on a physical device with
expo run:ios
, the error saysld: 12 duplicate symbols
.To Reproduce Steps to reproduce the behaviour:
npx expo prebuild --platform ios
npx expo run:ios --device
, run on a physical deviceObserved behaviour All of the build phases go through as below:
Until in the last phase it results in a build error with
ld: 12 duplicate symbols
.Expected behaviour I have tested veramo with another expo-managed react native project, it worked, compiled, and ran perfectly. This error started popping up within the last 48-72 hours.
Details
Versions: Exact versions as the official react native guide and the react native tutorial repository: https://veramo.io/docs/react_native_tutorials/react_native_1_setup_identifiers https://github.com/veramolabs/veramo-react-native-tutorial/blob/main/package.json