Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Attempted to remove more RCTLinkingManager listeners than added

See original GitHub issue

New Version

0.66.4

Old Version

0.66.1

Build Target(s)

ios simulator

Output of `react-native info`

System: OS: macOS 12.0.1 CPU: (8) arm64 Apple M1 Memory: 803.86 MB / 16.00 GB Shell: 3.3.1 - /opt/homebrew/bin/fish Binaries: Node: 17.0.1 - /opt/homebrew/bin/node Yarn: 1.22.17 - /opt/homebrew/bin/yarn npm: 8.1.0 - /opt/homebrew/bin/npm Watchman: 2021.10.18.00 - /opt/homebrew/bin/watchman Managers: CocoaPods: 1.11.2 - /opt/homebrew/bin/pod SDKs: iOS SDK: Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3 Android SDK: API Levels: 26, 28, 29, 30, 31 Build Tools: 29.0.2, 30.0.2, 31.0.0 System Images: android-31 | Google Play ARM 64 v8a Android NDK: Not Found IDEs: Android Studio: 2020.3 AI-203.7717.56.2031.7784292 Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild Languages: Java: 11.0.10 - /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/javac npmPackages: @react-native-community/cli: Not Found react: 17.0.2 => 17.0.2 react-native: 0.66.1 => 0.66.1 react-native-macos: Not Found npmGlobalPackages: react-native: Not Found

Issue and Reproduction Steps

When I upgrade from react native version 0.66.1 to 0.66.4 I get the error “Attempted to remove more RCTLinkingManager listeners than added”. This error causes the application to crash. I downgrade the application, the problem is solved.

Issue Analytics

State:
Created 2 years ago
Reactions:6
Comments:11

Top GitHub Comments

2reactions

beisert1commented, Mar 2, 2022

For anyone struggling with this issue please check react-navigation, we are on an old fork of v2 react-navigation and I was able to apply something similar to this solution that resolved this error: https://github.com/react-navigation/react-navigation/issues/9894

1reaction

nica0012commented, Jul 21, 2022

For anyone struggling with this issue please check react-navigation, we are on an old fork of v2 react-navigation and I was able to apply something similar to this solution that resolved this error: https://github.com/react-navigation/react-navigation/issues/9894

Can you please share how you went about solving this?

Do you need to apply those edits every time you run yarn / npm install?

Top Results From Across the Web

How to fix "Attempted to remove more RCTLinkingManager ...

It says that "Attempted to remove more RCTLinkingManager listeners than added". But I don't know how to fix this.

Attempted to remove more RCTLinkingManager listeners than ...

Coding example for the question "Attempted to remove more RCTLinkingManager listeners than added" error in react-native-React Native.

Attempted to remove more RCTLinkingManager listeners than ...

is appearing after each restart of the app, but everything is working fine after dismissing it. It's only showing on iOS, on android...

Linking - React Native

For instructions on how to add support for deep linking on Android, ... return [RCTLinkingManager application:application openURL:url options:options];

Deep Linking in React Native with Universal Links and URL ...

This event listener can then handle that event accordingly, ... configuration is no more complex than URL Schemes, with the only additional ......