RN Android crash, probably zmq issue #2346
Comments
|
I would like just add some more info. There is |
|
I am running into the same issue and getting the same error from Android Studio. I'm currently using |
|
The issue was introduced with 0.62.0. It works with 0.61.5. |
|
According to logs, it seems like the problem happens at this line https://github.com/hyperledger/indy-sdk/blob/master/libindy/src/services/pool/networker.rs#L334. Also worth mentioning that it works on iOS (tested with RN |
|
Thanks, @jakubkoci for the report and investigation. You are correct that In React Native 0.62.0 have been changed one of system libraries libfb.so -> libfbjni.so: facebook/react-native@9ad5e72 |
|
I'm curious if there is any update on this? 👀 |
|
@TimoGlastra Sorry, we don't have any fix yet. We are tackling another issue internally. But this issue is definitely a priority for us. We are hoping to get started on this issue very soon. Sorry for not providing exact time. We also have few of our apps written in react-native. So, this issue is one of the priority for us as well. We will update here once we start working on this issue. |
|
Are there any updates regarding this issue? |
|
@mikaeljan we have a client implementation that is using RN 0.63.3 currently--although we need to do some additional investigating as to the exact details that has enabled this capability (as we were not the developers that achieved this). This hopefully/likely is something that we can further dig into shortly. |
|
Have an update here on this--after some digging from @TheTreek and I, we identified that running Android with Hermes enables successful opening of the pool (at least we've tested for React Native v0.63.3 and v0.64.1). Interestingly it also works when running in debug mode (using Chrome's engine), which leads me to believe that Hermes is either doing a compile step or causing a side affect of sorts (although I'm not sure as of what). This does make me a little concerned for longer-term resolution, however it will at least if nothing else get us able to use v0.64.1 of React Native. Another option is utilizing Indy-VDR as a proxy server for ledger operations. I was considering using it as an on-device replacement to switch to for ledger operations, which does help reduce our dependency on Indy SDK, but as far as I know Indy VDR is also unfortunately utilizing ZMQ--which doesn't end up solving this problem. |
|
Thanks for this @JamesKEbert and @TheTreek! I can confirm this works in RN 0.64.0. Really great work, and thanks for looking into this! :) |
|
I ran into this issue again in our app. It crashed whenever you opened a pool. After a lot of adding and removing stuff I came to the conclusion that is was because we had updated flipper from 0.75.1 to 0.98.0 in Maybe I can save some of you some headaches with this # Version of flipper SDK to use with React Native
-FLIPPER_VERSION=0.75.1
+FLIPPER_VERSION=0.98.0 // don't do this |
|
Yeah, I had found issues in regards to Flipper--in fact this issue was completely solved in an unrelated ZMQ RN project via removal of Flipper: rgb-archive/react_native_demo#1 (comment) |
|
I have new findings. Unfortunately, it won't solve anything, but I just want to add it here for information: App with React Native android:extractNativeLibs="true"You can find more info about the flag at https://developer.android.com/studio/releases/gradle-plugin#extractNativeLibs. The trick is that this flag was in previous version of Android Gradle plugin set to |
|
Is there any update on this ? |
|
@erenakyildiz-code see this comment: #2346 (comment) It works if you enable hermes on Android. It's not a fix per se, but we've all switched to using Hermes |
|
I see, i will post a pr to rn-indy-sdk library to change the example demo project. Thanks for the response. |
|
rn-indy-sdk has been deprecated in favour of https://github.com/hyperledger/indy-sdk-react-native, but a PR to that repo would be much appreciated! |
WadeBarnes
added
the
wont-address-project-depreciated
Hello,
we are having issues with indy-sdk on React native, Android - issue does not depend on the device.
This is our deps setup for example project:
RN wrapper uses these methods:
And this dependency for indy:
implementation 'org.hyperledger:indy:1.15.0'We also opened an issue for RN at: react-native-community/upgrade-support#114
Issue is not reproducible on 0.61.x RN version. Below you can find our logs. It seems to us it might be connected to zmq somehow. We are thinking about making our custom build of indy-sdk with a different version of zmq which might somehow help us however it would be better to fix this issue in official repo, not just in a forked one.
The text was updated successfully, but these errors were encountered: