When running the project we get the error:
› Linking injiexpo2 » injiexpo2
❌ duplicate symbol '_secureKeyStoreError' in
┌─ libreact-native-mmkv-storage.a(SecureStorage.o)
└─ libreact-native-secure-key-store.a(RNSecureKeyStore.o)
❌ ld: 1 duplicate symbol for architecture x86_64
❌ clang: error: linker command failed with exit code 1 (use -v to see invocation)
Additional context
The error is due to the conflicting method name secureKeyStoreError in both the libraries. The same method is present in SecureStorage.m file in mmkv-storage library and in RNSecureKeyStore.m file in secure-key-store library. We have tried to understand the usage of this method in the mmkv-storage code and couldn't find any usages/references for the same.
In order to resolve the issue, we tried removing the method and also tried renaming it, both seems to work.
Can you confirm if this is an unused method, if so, do you have plans to remove it in the upcoming releases.
If this is a method used somewhere which we couldn't figure out as of now. We would like understand about it and a way to resolve this conflict.
Describe the bug Add react-native-secure-key-store and react-native-mmkv-storage to a project and compile it for iOS.
When running the project we get the error: › Linking injiexpo2 » injiexpo2
❌ duplicate symbol '_secureKeyStoreError' in ┌─ libreact-native-mmkv-storage.a(SecureStorage.o) └─ libreact-native-secure-key-store.a(RNSecureKeyStore.o)
❌ ld: 1 duplicate symbol for architecture x86_64
❌ clang: error: linker command failed with exit code 1 (use -v to see invocation)
To Reproduce Steps to reproduce the behavior:
npm run
Platform Information:
Additional context The error is due to the conflicting method name
secureKeyStoreError
in both the libraries. The same method is present in SecureStorage.m file in mmkv-storage library and in RNSecureKeyStore.m file in secure-key-store library. We have tried to understand the usage of this method in the mmkv-storage code and couldn't find any usages/references for the same.In order to resolve the issue, we tried removing the method and also tried renaming it, both seems to work.