Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'RNCClipboard' could not be found.

[suhmah]

Environment

Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'RNCClipboard' could not be found. Verify that a module by this name is registered in the native binary.Bridgeless mode: false. TurboModule interop: false. Modules loaded: {"NativeModules":["PlatformConstants","LogBox","Timing","AppState","SourceCode","BlobModule","WebSocketModule","SettingsManager","DevSettings","RedBox","Networking","Appearance","DevLoadingView","UIManager","DeviceInfo","ImageLoader","LinkingManager"],"TurboModules":[],"NotFound":["NativePerformanceCxx","NativePerformanceObserverCxx","BugReporting","HeadlessJsTaskSupport","SoundManager","IntentAndroid","RNCClipboard"]}, js engine: hermes

Platforms

iOS only

Versions

• iOS: 17.2
• react-native: "0.74.1"
• react: "18.2.0"
  "@react-native-clipboard/clipboard": "^1.14.1",

Description

I have the following error
Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'RNCClipboard' could not be found. Verify that a module by this name is registered in the native binary.Bridgeless mode: false. TurboModule interop: false. Modules loaded: {"NativeModules":["PlatformConstants","LogBox","Timing","AppState","SourceCode","BlobModule","WebSocketModule","SettingsManager","DevSettings","RedBox","Networking","Appearance","DevLoadingView","UIManager","DeviceInfo","ImageLoader","LinkingManager"],"TurboModules":[],"NotFound":["NativePerformanceCxx","NativePerformanceObserverCxx","BugReporting","HeadlessJsTaskSupport","SoundManager","IntentAndroid","RNCClipboard"]}, js engine: hermes

Reproducible Demo

the error happens when running yarn ios and the application is installed. before even starting the metro bundle it gives an error

[nvacheishvili]

Having the same issue

[BrianIto]

Same here. Did the pod install in the ios directory. Still getting the issue.

[poojagirne]

Same issue in andriod also while testing in real device.

[BrianIto]

@suhmah I really don't get why this is happening, but using expo modules with expo dev client and expo-clipboard package solved the whole problem to me.

I want to just add the the newer version of Expo requires minimum development target to be 13.4 on iOS environments.

[poojagirne]

@suhmah I really don't get why this is happening, but using expo modules with expo dev client and expo-clipboard package solved the whole problem to me.

I want to just add the the newer version of Expo requires minimum development target to be 13.4 on iOS environments.

Even after using Expo, I am still getting the same error while testing on an actual device, not in the simulator.

[Nelie-Taylor]

I got same issue.

[ijs1103]

Both Android emulators and devices have the same problem.

[truezombie]

I have the same error.

[BrianIto]

I got the error again, and then migrated to expo-clipboard. Sorry, folks, that's not much help but it is what worked for me. :(

[UgurGumushan]

I experienced it on mocha tests after version upgrade and I mocked the module. Does it affect production code?

[williamAstudillo]

Rebuilding the app fixed it for me

[MarcosCunhaDev]

So, I had the same problem recently while running my tests after upgrading RN to version 0.74.2. After some research, I found a recommendation for how to mock @react-native-clipboard/clipboard. Here’s what I did:

• I imported mockClipboard at the top of the setupJest file:
  import mockClipboard from '@react-native-clipboard/clipboard/jest/clipboard-mock.js';
• I Added the following block of code between my mocks:
  jest.mock('@react-native-clipboard/clipboard', () => mockClipboard);

After this, the issue was resolved.

[nishith003]

In my case, I encountered the same issue and was able to resolve it with the following steps:

I changed the import from:

import Clipboard from '@react-native-clipboard/clipboard';

to:

import * as Clipboard from '@react-native-clipboard/clipboard';

For copying a string to the clipboard:

Clipboard.default.setString(address);

It worked for me on Android devices. I hope this helps anyone facing the same issue!

[JohnSmall]

@nishith003 I tried your fix, but it didn't work for me.

[dibasdauliya]

same issue