Closed pronevich closed 1 year ago
The issue is invalid!
The same
also seeing this crash for react-native version 0.66.0
try doing changes as per link https://docs.swmansion.com/react-native-reanimated/docs/fundamentals/installation/#android enablehermes editing Mainapplication.java
changes from the docs are applied. It doesn't seem to always crash. I can reliably reproduce this on our CI but not on local devices so far, I'll keep investigating @amitkumar3968
good to know, its working on local device. for CI, please update if you fixed it.
changes from the docs are applied. It doesn't seem to always crash. I can reliably reproduce this on our CI but not on local devices so far, I'll keep investigating @amitkumar3968
Yeah, no issue was in dev, only after the release build. I can confirm that crashes happening sometimes.
@amitkumar3968 Hermes enabled and here is my MainApplication:
@Override
protected JSIModulePackage getJSIModulePackage() {
return new JSIModulePackage() {
@Override
public List<JSIModuleSpec> getJSIModules(
final ReactApplicationContext reactApplicationContext,
final JavaScriptContextHolder jsContext
) {
List<JSIModuleSpec> modules = Arrays.asList();
modules.addAll(new WatermelonDBJSIPackage().getJSIModules(reactApplicationContext, jsContext));
modules.addAll(new ReanimatedJSIModulePackage().getJSIModules(reactApplicationContext, jsContext));
// ⬅️ add more JSI packages here by conventions above
return modules;
}
};
}
};
1.please check your release crashlytics logs.
I'm also having this issue in v2.3.0-beta.2, also seems to be happening at random
@amitkumar3968 looks like issue exists also in other projects without several jsi modules. Later I will try to return only reanimated module as per docs for the test.
i am also facing issues with this version, not crash. Seems like we have to switch to latest version or move to another library. WIP
Hey @pronevich! Can you (or anyone) confirm this crash occurs on latest release version & reanimated is installed properly?
@kkafar I will update the project and look at the result, then give you feedback
@kkafar I don't see this crash in Crashlytics, but after update to the stable version has risen this issue:
Fatal Exception: com.facebook.react.uimanager.IllegalViewOperationException: Trying to resolve view with tag 913 which doesn't exist
at com.facebook.react.uimanager.NativeViewHierarchyManager.resolveView(NativeViewHierarchyManager.java:102)
at com.facebook.react.uimanager.UIManagerModule.resolveView(UIManagerModule.java:964)
at com.swmansion.reanimated.layoutReanimation.AnimationsManager.removeLeftovers(AnimationsManager.java:236)
at com.swmansion.reanimated.layoutReanimation.AnimationsManager.lambda$scheduleCleaning$0$AnimationsManager(AnimationsManager.java:286)
at com.swmansion.reanimated.layoutReanimation.-$$Lambda$AnimationsManager$wJRqdL09xrx99sALjL4PPWgrOyU.run(:4)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
at android.os.Looper.loop(Looper.java:236)
at android.app.ActivityThread.main(ActivityThread.java:7861)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:600)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:967)
@kkafar are there any plans to release a version with the merged fix soon? It's causing quite a few crashes in my app and I'd prefer to pull in an explicitly released version.
Is there a reason a patch with this change hasn't been released yet @kkafar? It's been almost three weeks since a fix was merged and we are definitely seeing crashes in our app related to this and we can't get a build working with a git sha.
@kinigitbyday and @elGatoMantocko you can always build with the latest from master by doing the following: https://docs.swmansion.com/react-native-reanimated/docs/2.2.0/installation/#using-main-branch-builds
You can then get a build working based on the sha that you want 👍
I won't give you specifics, but release is coming within days.
However as was mentioned above you can build reanimated from source, which is extremely easy right now.
@kkafar Just to share some insights regarding this crash:
At Mixcloud we've recently introduced reanimated 2, and we made use of the latest SHA in master
We have followed/confirmed the steps regarding the installation and they are correct.
We still see the crashes as you can see in this screen-capture from firebase:
I'd like to kindly ask if you could reopen this issue as it seems that it persists despite https://github.com/software-mansion/react-native-reanimated/pull/2982
And if there's anything we can do to help, please let us know
Edit: @piaskowyk Just tagging you as well so you know about it. Thanks again
We are also seeing this issue in our crashlytics:
RN: 0.67.3 reanimated: 2.4.1 react-navigation: 6.1.1
We need to look at this again
@alexfoxy are you still seeing that error? Maybe 2.8.0
fixed it for you? It includes this fix:
https://github.com/software-mansion/react-native-reanimated/pull/3162
Which seems to be the NPE you're seeing
Im still seeing this error, but some times.
RN: 0.66.3 reanimated: ^2.9.1
@nickcruz Yes it seems fixed for us at least 🙏
Description
Stack trace from Crashlytics, Android 11, Redmi Note 9 Pro:
Package versions
Affected platforms