-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hermes AndroidUnicodeUtils ClassNotFoundException #25679
Comments
Thanks for submitting your issue. Can you take another look at your description and make sure the issue template has been filled in its entirety? 👉 Click here if you want to take another look at the Bug Report issue template. |
can you please post a repro? |
I have enableProguardInReleaseBuilds enabled. So adding a line to my proguard-rules.pro config did the trick for me.
From what I found out this is caused by some code in the "share" module. I am using https://github.com/react-native-community/react-native-share/ but it seams to happen with the react native build in one as well. Would be helpful if this proguard rule could be added somewhere. Where is the place this should go hermes/rn/react-native-share? |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
Using 0.60.3 with Hermes enabled crashes with the following exception:
terminating with uncaught exception of type facebook::jni::JniException: java.lang.ClassNotFoundException: Didn't find class "com.facebook.hermes.unicode.AndroidUnicodeUtils"
This only happens in release builds on real devices.
The text was updated successfully, but these errors were encountered: