RemoveEventListener error in react-native-navigation@4

[gkasireddy202]

Current behavior

I have used react-navigation: 4.4.4 in my project for the last 5 years. We maintained the navigation structure in 4.4.4 because of more screens. I upgraded my project to 0.73.2 and got this error. Click on tab screen and go back to previous screen getting this error. _reactNative.Linking.removeEventListener is not a function (it is undefined)

Expected behavior

I expect this error will be resolved. Screen A.js

import React, { Component } from 'react'; import { View, Button, StyleSheet } from 'react-native';

class ScreenA extends Component { constructor(props) { super(props);

}

// Method to handle button press handlePress = () => { // Your logic here this.props.navigation.navigate("ScreenB"); };

render() { return (

);

} }

const styles = StyleSheet.create({ container: { flex: 1, justifyContent: 'center', alignItems: 'center', }, });

export default ScreenA;

ScreenB.js

import React,{Component} from "react"; import {View} from 'react-native'; class ScreenB extends Component{

render() { return(<View style={{flex:1,backgroundColor:'white'}}>) } } export default ScreenB;

Reproduction

N/A

Platform

• [ ] Android
• [X] iOS
• [ ] Web
• [ ] Windows
• [ ] MacOS

Packages

• [ ] @react-navigation/bottom-tabs
• [ ] @react-navigation/drawer
• [ ] @react-navigation/material-top-tabs
• [ ] @react-navigation/stack
• [ ] @react-navigation/native-stack
• [ ] react-native-tab-view

Environment

"react-navigation": "^4.4.4", "react-navigation-drawer": "^2.7.2", "react-navigation-stack": "^2.10.4", "react-navigation-tabs": "^2.11.2",

https://github.com/react-navigation/react-navigation/assets/90603484/b56d95d7-910a-4676-9f54-0fe338ac8a4b

[github-actions[bot]]

Hey @gkasireddy202! Thanks for opening the issue. It seems that the issue doesn't contain a link to a repro.

The best way to get attention to your issue is to provide an easy way for a developer to reproduce the issue.

You can provide a repro using any of the following:

• Expo Snack
• TypeScript Playground

• GitHub repo under your username

  A snack link is preferred since it's the easiest way to both create and share a repro. If it's not possible to create a repro using a snack, link to a GitHub repo under your username is a good alternative. Don't link to a branch or specific file etc. as it won't be detected.

  Try to keep the repro as small as possible by narrowing down the minimal amount of code needed to reproduce the issue. Don't link to your entire project or a project containing code unrelated to the issue. See "How to create a Minimal, Reproducible Example" for more information.

  You can edit your original issue to include a link to the repro, or leave it as a comment. The issue will be closed automatically after a while if you don't provide a repro.

[github-actions[bot]]

Couldn't find version numbers for the following packages in the issue:

• @react-navigation/native

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

[gkasireddy202]

"react-navigation": "^4.4.4".I added a sample code for this error. Getting the error in the react-native-navigation package when I go back from the tab screen. this error occurred in my production environment. We have used this navigation for the last 5 years. We have integrated the navigation structure in v4 for more than 25 screens. Please look at this issue.

[satya164]

React Navigation 4 is no longer supported. Please update to the latest stable version. You've had 4 years to upgrade.

[github-actions[bot]]

Hey! This issue is closed and isn't watched by the core team. You are welcome to discuss the issue with others in this thread, but if you think this issue is still valid and needs to be tracked, please open a new issue with a repro.

[gkasireddy202]

how to open issue with a repo?

[gkasireddy202]

React Navigation 4 is no longer supported. Please update to the latest stable version. You've had 4 years to upgrade.

Can you please help to fix this issue? We are upgrading my project to 0.73.2 for the iOS Privacy manifest policy. We have many screens having react-native-navigation@4 navigation structure in my project. Now it is difficult to upgrade.

[gkasireddy202]

@satya164 - Please any update on this?