0x104f2f700 -[REAAnimationsManager clearSharedTransitionConfigForTag:] Thread 1: EXC_BAD_ACCESS (code=1, address=0x10) #5947
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? |
ggnsingh
changed the title
|
i am also getting same , as soon as user logs into the application app crashes ... same happens if i run from xcode or install it via testflight... i can not provide access to code since its private project, and obviously its impossible to create reproducible snack, due to complexity of the project.. .. i used to use 3.6.x version of reanimated, upgraded to latest 3.9 today but still getting same error. here is the stack : |
|
more investigative info I have is that, screen that seens to be crashing is using following animation code : but this code is very old and we have not touched it for a loooong time. |
This comment was marked as spam.
This comment was marked as spam.
|
downgrading to 2.17 solved the poblem for me. |
|
Having the same problem Reanimated version React Native version Platforms |
|
Same error here... crashes when navigating to other screens. I am not using this library, but its a dependency of react-native-reanimated-carousel, which I am also only using in one component deep down... 
tmp fix => downgrading to ~3.8.1 |
Downgrade didn’t work for me, the app is still crashing while navigating. |
Can confirm downgrading from 3.9.0 => ~3.8.1 worked. |
@KazakovVS try to remove and add node_modules folder and run |
|
same problem !!! "react-native": "^0.74.0", so for ios and for android but this is not a solution can someone provide a better solution for this problem please |
|
Also happens for 3.10.0 |
|
doesn't ^3.8.1 also include 3.10.0? |
|
I am also getting this hard crashing issue and agree with the others that this issue started happening with I have a feeling this issue could possibly be related to: #5274 (as that was added in ...and that didn't seem to help matters. Still crashing on certain forward/back navigations (happens 100% of the time when clicking back button in nav header early after app launches). This is a pretty serious issue! It's worse when you consider that apps that use Hoping the maintainers recognize this issue and work on a fix ASAP 🤞 . In the meantime, I have downgraded to diff --git a/node_modules/react-native-reanimated/apple/sensor/ReanimatedSensor.m b/node_modules/react-native-reanimated/apple/sensor/ReanimatedSensor.m
index 863c788..656a27a 100644
--- a/node_modules/react-native-reanimated/apple/sensor/ReanimatedSensor.m
+++ b/node_modules/react-native-reanimated/apple/sensor/ReanimatedSensor.m
@@ -48,7 +48,7 @@ - (bool)initializeGyroscope
[_motionManager
startGyroUpdatesToQueue:[NSOperationQueue mainQueue]
withHandler:^(CMGyroData *sensorData, NSError *error) {
- double currentTime = [[NSProcessInfo processInfo] systemUptime];
+ double currentTime = CACurrentMediaTime() * 1000;
if (currentTime - self->_lastTimestamp < self->_interval) {
return;
}
@@ -69,7 +69,7 @@ - (bool)initializeAccelerometer
[_motionManager startAccelerometerUpdates];
[_motionManager startAccelerometerUpdatesToQueue:[NSOperationQueue mainQueue]
withHandler:^(CMAccelerometerData *sensorData, NSError *error) {
- double currentTime = [[NSProcessInfo processInfo] systemUptime];
+ double currentTime = CACurrentMediaTime() * 1000;
if (currentTime - self->_lastTimestamp < self->_interval) {
return;
}
@@ -96,7 +96,7 @@ - (bool)initializeGravity
[_motionManager
startDeviceMotionUpdatesToQueue:[NSOperationQueue mainQueue]
withHandler:^(CMDeviceMotion *sensorData, NSError *error) {
- double currentTime = [[NSProcessInfo processInfo] systemUptime];
+ double currentTime = CACurrentMediaTime() * 1000;
if (currentTime - self->_lastTimestamp < self->_interval) {
return;
}
@@ -121,7 +121,7 @@ - (bool)initializeMagnetometer
[_motionManager
startMagnetometerUpdatesToQueue:[NSOperationQueue mainQueue]
withHandler:^(CMMagnetometerData *sensorData, NSError *error) {
- double currentTime = [[NSProcessInfo processInfo] systemUptime];
+ double currentTime = CACurrentMediaTime() * 1000;
if (currentTime - self->_lastTimestamp < self->_interval) {
return;
}
@@ -157,7 +157,7 @@ - (bool)initializeOrientation
[_motionManager startDeviceMotionUpdatesUsingReferenceFrame:(1 << _referenceFrame)
toQueue:[NSOperationQueue mainQueue]
withHandler:^(CMDeviceMotion *sensorData, NSError *error) {
- double currentTime = [[NSProcessInfo processInfo] systemUptime];
+ double currentTime = CACurrentMediaTime() * 1000;
if (currentTime - self->_lastTimestamp < self->_interval) {
return;
}
|
|
@dan-trewin easy boi, this is open source software so instead of ranting open a PR and try to fix the issue. |
|
I also have the same issue. I'm not using expo, but I tried the suggestion of importing reanimated into index.js; this still didn't fix the problem. |
i dont think he is ranting.. and as opposed to you, who acts like a cyber-judge he at least spent time on research and posted his findings here, and further more, your statment that its opensource means nothing... when library claims |
any update on this ? also tried "3.10.0" and it is crash on ios
|
|
React native 0.74.1 solved this problem for me. |
|
I was able to reproduce this issue on 81c4130. RecordingScreen.Recording.2024-05-05.at.14.28.27.movSteps to reproduce
Example/App.tsximport {NavigationContainer} from '@react-navigation/native';
import {createNativeStackNavigator} from '@react-navigation/native-stack';
import {createBottomTabNavigator} from '@react-navigation/bottom-tabs';
import React from 'react';
const Stack = createNativeStackNavigator();
const Tab = createBottomTabNavigator();
function Feed() {
return null;
}
function Messages() {
return null;
}
function Profile() {
return null;
}
function Settings() {
return null;
}
function Home() {
return (
<Tab.Navigator>
<Tab.Screen name="Feed" component={Feed} />
<Tab.Screen name="Messages" component={Messages} />
</Tab.Navigator>
);
}
export default function App() {
return (
<NavigationContainer>
<Stack.Navigator>
<Stack.Screen
name="Home"
component={Home}
options={{headerShown: false}}
/>
<Stack.Screen name="Profile" component={Profile} />
<Stack.Screen name="Settings" component={Settings} />
</Stack.Navigator>
</NavigationContainer>
);
}
|
|
Bumped Example app to |
|
Workaround: import something from import Animated from 'react-native-reanimated';
console.log(Animated); // make sure to use the imported thing, otherwise the import will be optimized away |
|
PR with a temporary fix: |
@levancho you definitely need to redefine the term open source in your head, specially the last paragraph of the MIT license. |
…TransitionConfigForTag:]` (#5975) ## Summary Fixes #5947. Fixes #5968. When `react-native-reanimated` is installed but not used directly, switching between bottom tabs from `@react-navigation/bottom-tabs` will result in a `EXC_BAD_ACCESS` crash on iOS. This PR adds missing mock for `_clearSharedTransitionConfigForTag` as suggested by @bartlomiejbloniarz. ## Test plan Try repro from #5947 (comment)
Description
Working propery with version 3.8.1
Steps to reproduce
Running a react native app with library version 3.9.0 crashes the app on ios with this logs.
Snack or a link to a repository
none
Reanimated version
3.9.0
React Native version
0.72.5
Platforms
iOS
JavaScript runtime
None
Workflow
None
Architecture
None
Build type
None
Device
None
Device model
Iphone 15 pro
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: