Closed kristfal closed 1 year ago
Hey! 👋
The issue doesn't seem to contain a minimal reproduction.
Could you provide a snippet of code, a snack or a link to a GitHub repository that reproduces the problem?
Hey! 👋
It looks like you've omitted a few important sections from the issue template.
Please complete Snack or minimal code example section.
It looks like proguard configuration issue. Could you try to mark as required these classes in your proguard config?
Same issue here:
java.lang.NoSuchMethodError: no non-static method "Ljava/lang/Class;.getUpTime()Ljava/lang/String;"
at com.swmansion.reanimated.NativeProxy$EventHandler.receiveEvent(NativeProxy.java)
at com.swmansion.reanimated.NativeProxy$EventHandler.receiveEvent(NativeProxy.java:55)
at com.swmansion.rnscreens.events.ScreenDismissedEvent.dispatch(ScreenDismissedEvent.kt:17)
at com.swmansion.reanimated.NodesManager.handleEvent(NodesManager.java:485)
at com.swmansion.reanimated.NodesManager.onEventDispatch(NodesManager.java:462)
at com.facebook.react.uimanager.events.EventDispatcher.dispatchEvent(EventDispatcher.java:114)
at com.swmansion.rnscreens.ScreenFragment.onDestroy(ScreenFragment.kt:260)
at androidx.fragment.app.Fragment.performDestroy(Fragment.java:2927)
at androidx.fragment.app.FragmentStateManager.destroy(FragmentStateManager.java:492)
at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1296)
at androidx.fragment.app.FragmentManager.endAnimatingAwayFragments(FragmentManager.java:2251)
at androidx.fragment.app.FragmentManager.saveAllState(FragmentManager.java:2380)
at androidx.fragment.app.FragmentController.saveAllState(FragmentController.java:152)
at androidx.fragment.app.FragmentActivity.onSaveInstanceState(FragmentActivity.java:512)
at androidx.appcompat.app.AppCompatActivity.onSaveInstanceState(AppCompatActivity.java:533)
at android.app.Activity.performSaveInstanceState(Activity.java:2242)
at android.app.Instrumentation.callActivityOnSaveInstanceState(Instrumentation.java:1514)
at android.app.ActivityThread.callActivityOnSaveInstanceState(ActivityThread.java:6353)
at android.app.ActivityThread.callActivityOnStop(ActivityThread.java:5712)
at android.app.ActivityThread.performStopActivityInner(ActivityThread.java:5642)
at android.app.ActivityThread.handleStopActivity(ActivityThread.java:5743)
at android.app.servertransaction.StopActivityItem.execute(StopActivityItem.java:43)
at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:45)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2434)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8633)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:567)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)
In our case enableProguardInReleaseBuilds is false.
"react-native-reanimated": "^2.2.4",
"react-native": "0.63.4",
@piaskowyk we don't run Progard either, so this has us puzzled. Any suggestion for how to dig deeper?
@kristfal Last month we renamed one of our internal methods from getUpTime
to getUptime
(see here). The error comes from C++ part of Reanimated trying to invoke getUptime
method via JNI which does not exist now. It seems like there was some mismatch between C++ precompiled sources (distributed as shared library libreanimated.so
within .aar
) and Java sources.
Hi @tomekzaw , is there any possible fix for this in future?
Same issue here. proguard not enabled, using react-native-reanimated 2.6.0.
Any update on this one.? Still facing this issue.
Also facing this using react-native-reanimated 2.2.3, any updates would be greatly appreciated
+1 same issue
Facing the same
ReactNative: 0.68.2
react-native-reanimated: 2.8.0
+1 same issue
"react-native": "0.64.3"
"react-native-reanimated": "2.3.3"
Hey, do you use Expo managed workflow? If yes, then the JS version of Reanimated (in node_modules
) must match the version from SDK.
I don't use Expo managed workflow, I use react-native directly. And I haven't been able to reproduce this issue myself, just found the crash log in the prod environment
Any update on this one? Still facing this issue.
Hey! 👋
The issue doesn't seem to contain a minimal reproduction.
Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem?
Description
Seeing the following crash in production:
Expected behavior
No crash
Actual behavior & steps to reproduce
Unknown – crash from production log. Full stack trace:
Snack or minimal code example
Package versions
Affected platforms