v3.4.1 crash _clearAnimationConfigForTag #4836
Comments
github-actions
bot
added
Platform: iOS
|
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? |
|
I also installed |
|
i same issue on IOS, work fine on android! |
|
I same issue on IOS, work fine on android! |
|
Same issue. For me, it's reproducing only with Chrome Debugger turned on. |
|
Hi, if so many people have this issue maybe someone can throw in a repro? 😅 |
|
had to downgrade to |
|
is there any update on this issue? I'm getting the same crashes. these are my versions |
|
I'm still getting the same crash after downgrading to version 3.3.0. Any updates or help would be appreciated! |
|
Please post a repro so we can investigate this issue 🙏 |
|
clash after call |
|
yep, mine is the same as @kunger97 , but I've downgraded to 3.3.0 and it's working now |
|
@tjzel I am encountering a consistent crash whenever I use the "Debug with Chrome" feature and navigate to another screen. This happens on a newly initialized project, and the error is reproducible. Here are the step-by-step details of how to reproduce the issue: Steps to reproduce:
Every single time I navigate back, the app crashes without fail, and it also crashes the moment I disable the "Debug with Chrome" feature. This is a major issue for us because our team heavily relies on the React Native Debugger and we literally can't use it at the moment for the newly created project. Could you please look into it? Thanks. Here is my dependencies list:
import React from 'react';
import { Button, SafeAreaView, Text } from 'react-native';
import { NavigationContainer } from '@react-navigation/native';
import {
createNativeStackNavigator,
NativeStackScreenProps,
} from '@react-navigation/native-stack';
const Home = ({ navigation: { navigate } }: NativeStackScreenProps<any>) => {
return (
<SafeAreaView>
<Text>Main screen</Text>
<Button title="Go to details" onPress={() => navigate('Details')} />
</SafeAreaView>
);
};
const Details = ({ navigation: { goBack } }: NativeStackScreenProps<any>) => {
return (
<SafeAreaView>
<Text>Main screen</Text>
<Button title="Go back" onPress={goBack} />
</SafeAreaView>
);
};
const NativeStack = createNativeStackNavigator();
const App = () => {
return (
<NavigationContainer>
<NativeStack.Navigator>
<NativeStack.Screen name={'Home'} component={Home} />
<NativeStack.Screen name={'Details'} component={Details} />
</NativeStack.Navigator>
</NavigationContainer>
);
};
export default App; |
|
@david-tabaka-guesty thank you for providing the reproduction! 🙏 I have an idea how to solve this issue. I will post a PR soon. |
|
I have this problem too, it's been bothering me for a day "react-native-reanimated": "^3.4.1", |
|
If you need a temporary workaround you can put |
Your method works, thanks |
import type {WithSpringConfig, WithTimingConfig} from 'react-native-reanimated'; When this is introduced on the screen, the editor will prompt as follows, whether it can be solved together, thank you Module ""react-native-reanimated"" has no exported member "WithSpringConfig". Are you trying to use "import WithSpringConfig from "react-native-reanimated"" instead? |
|
@caixingyue This is a known issue that with release of |
|
Hi @tjzel when is the next relese for the version 3.4.2? |
|
Is there any update on this error ... i m facing this issue while navigating from one screen to another from Drawer. 
|
Temporary solution, add import 'react-native-reanimated' to index.js or App.ts |
Another temporary solution I found (but I don't think it's better then the one @caixingyue suggested) is to just disable the chrome deubugging for now. |
|
This issue is under investigation. @sebasgarcia29 I can't guarantee that it will be released in |
|
import 'react-native-reanimated' |
I spent hours trying different fixes. This is the way... |
…4878) ## Summary This PR adds default instances for uninitialized blocks in AnimationManager on iOS. It helps avoid null exceptions in two cases: - When reloading during Layout Animations and Shared Transitions. - When someone has installed Reanimated but doesn't import anything from it. In this situation, these blocks will not be set, but due to swizzling in Screens, there is a possibility of calling some of these blocks. Fixes #4836 Fixes: <img width="500" alt="Screenshot 2023-06-26 at 21 26 52" src="https://github.com/software-mansion/react-native-reanimated/assets/36106620/5bc60a08-da8b-4b14-8762-bbd1ab9a45ec"> ## Test plan 1. Run Example -> open [LA] Entering and Exiting with Layout -> click toggle -> press R in console 2. Run example from #4836 (comment)
Way to go! |
|
:*( this error cost me sleepless nights!, the irony is that it only appeared on production build/real device. Same error in 3.4.2 |
|
This fix hasn't released yet. It will be available in 3.5.0 |
|
add in babel.config.json https://docs.swmansion.com/react-native-reanimated/docs/fundamentals/installation/#babel-plugin This works for me |
|
For some reason, |
|
You can use current nightly version that has it fixed, |
|
This is an issue in latest react native reanimated , putting |
|
@tjzel thanks a lot, |
|
I was able to reproduce the issue still on version importing but since the post has been declared closed I'm assuming the fix is going to be released soon. |
|
This worked. |
|
Fix will come in Reanimated 3.5 (software-mansion/react-native-reanimated#4836)
…imated 3.4. Fix will come in Reanimated 3.5 (software-mansion/react-native-reanimated#4836)
…imated 3.4. Fix will come in Reanimated 3.5 (software-mansion/react-native-reanimated#4836)
Amazing work around |
|
When you do Xcode Crash Report below. Crash trigger only. Thread 3 Crashed:: Dispatch queue: com.facebook.react.ExceptionsManagerQueue Below are the dependencies. "@react-native-community/slider": "^4.4.2", |
|
any update on this ?? still getting the issue on |
|
@piaskowyk have you found a solution for this issue? If you could share the solution or the PR, we could apply a patch until it's officially released |
|
Today we released version that contains the fix, you should update your Reanimated to 3.5.0 |
|
I had the same error in Reanimated version 3.8.1. I tried several Reanimated versions and imported Reanimated into my App.tsx file, but nothing worked in my instance. After many tries, I decided to import Animated from'react-native-reanimated' and apply it to any view of my landing page, which worked! You can use it on any view on your screen. Example usage: Import Animated from'react-native-reanimated' <Animated.View style={[{ marginHorizontal: 16, }]}> |
and others
Description
I checked viewtag = nil but still run into this block:
Steps to reproduce
Snack or a link to a repository
https://snack.expo.dev
Reanimated version
3.4.1
React Native version
0.72.3
Platforms
iOS
JavaScript runtime
Hermes
Workflow
React Native (without Expo)
Architecture
Paper (Old Architecture)
Build type
Debug mode
Device
Real device
Device model
Ipad gen7
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: