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
I've been trying to get started with a fresh project and I've hit multiple stumbling blocks. My fresh project is a fork of the recommended react native typescript template.
Had to tweak some other packages to be compatible with use_frameworks!. In my case I had to enable $RNFirebaseAsStaticFramework = true for firebase.
When using [email protected], I had to do a force install because the packages because virgil packages don not declare themselves as compatible with react@17 npm i @virgilsecurity/e3kit-native @virgilsecurity/key-storage-rn react-native-keychain react-native-virgil-crypto --force. Also had to install npm i @react-native-async-storage/async-storage instead of the recommended @react-native-community/async-storage
After all this it "works" provided debugging is not enabled. If I enable remote debugging I get the following error when using virgil APIs
Invariant Violation: Calling synchronous methods on native modules is not supported in Chrome.
mfbx9da4
changed the title
React-native 0.66 not supported - Invariant Violation: Calling synchronous methods on native modules is not supported in Chrome.
Invariant Violation: Calling synchronous methods on native modules is not supported in Chrome.
Oct 13, 2021
looking through the source the issue is that the library always exports with RCT_EXPORT_BLOCKING_SYNCHRONOUS_METHOD. So this error is guaranteed to happen... Do I have to fork the library and re-export everything with RCT_EXPORT_METHOD?
I've been trying to get started with a fresh project and I've hit multiple stumbling blocks. My fresh project is a fork of the recommended react native typescript template.
use_frameworks!
.use_frameworks
being disabled.use_frameworks!
. In my case I had to enable$RNFirebaseAsStaticFramework = true
for firebase.npm i @virgilsecurity/e3kit-native @virgilsecurity/key-storage-rn react-native-keychain react-native-virgil-crypto --force
. Also had to installnpm i @react-native-async-storage/async-storage
instead of the recommended@react-native-community/async-storage
After all this it "works" provided debugging is not enabled. If I enable remote debugging I get the following error when using virgil APIs
This error is present with [email protected] and [email protected] configurations.
The text was updated successfully, but these errors were encountered: