App quits when navigating between tabs. IOS - critical issue

[again-this-coder]

Minimal reproducible example

can't share bussiness repository

What platform(s) does this occur on?

iOS

Did you reproduce this issue in a development build?

No (tested in Expo Go)

Summary

App quits when navigating between tabs. IOS - critical issue

For users that use react-navigation/native app crashes when trying to navigate between screens
app just quits without any error message

how was already mentioned in this issue #28618
I am creating this new issue for those who still are facing this and by the recommendation of the author this needs to be a new discussion

the reason behind this is in react native reanimated. I had it working on version 3.11.0 but after your updates of Expo go it stopped working and downgrading it to 3.10.1 as recommended didn't help to solve it

I believe that you are aware already of this issue and it the details that I provided are enough

Environment

expo-env-info 1.2.0 environment info:
System:
OS: macOS 12.7.4
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 21.1.0 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 10.2.0 - /usr/local/bin/npm
Watchman: 2024.01.22.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.15.2 - /Users/macbook/.rvm/gems/ruby-3.2.0/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
IDEs:
Android Studio: 2023.3 AI-233.14808.21.2331.11709847
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
npmPackages:
expo: ^51.0.7 => 51.0.7
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.74.1 => 0.74.1
react-native-web: ~0.19.6 => 0.19.11
npmGlobalPackages:
eas-cli: 7.1.3
Expo Workflow: managed

Expo Doctor Diagnostics

✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check native tooling versions
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check for issues with metro config
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✖ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK

Detailed check results:

(node:59887) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
The following packages should be updated for best compatibility with the installed expo version:
react-native-svg@14.1.0 - expected version: 15.2.0
Your project may not work correctly until you install the expected versions of the packages.
Found outdated dependencies

regarding the react-native-svg@14.1.0 - expected version: 15.2.0
this libarary is not causing the issue. the reason I don't update this library is due to its not compatible with another library that is critical for my code

[again-this-coder]

@brentvatne please take a look

[expo-bot]

Hi there! It looks like your issue requires a minimal reproducible example, but it is invalid or absent. Please prepare such an example and share it in a new issue.

The best way to get attention to your issue is to provide a clean and easy way for a developer to reproduce the issue on their own machine. Please do not provide your entire project, or a project with more code than is necessary to reproduce the issue.

A side benefit of going through the process of narrowing down the minimal amount of code needed to reproduce the issue is that you may get lucky and discover that the bug is due to a mistake in your application code that you can quickly fix on your own.

Resources

• "How to create a Minimal, Reproducible Example"
• "How to narrow down the source of an error"

Common concerns

"I've only been able to reproduce it in private, proprietary code"

You may not have spent enough time narrowing down the root cause of the issue. Try out the techniques discussed in this manual debugging guide to learn how to isolate the problem from the rest of your codebase.

"I didn't have time to create one"

That's understandable, it can take some time to prepare. We ask that you hold off on filing an issue until you are able to fully complete the required fields in the issue template.

"You can reproduce it by yourself by creating a project and following these steps"

This is useful knowledge, but it's still valuable to have the resulting project that is produced from running the steps, where you have verified you can reproduce the issue.