BlackMouse
BlackMouse

Reputation: 4572

React-native, "Native module cannot be null"

I just upgrade React-native from 0.28 to 0.30, and get this error:

"Native module cannot be null".

The problem seem to be with the line/package:

var PushNotification = require('react-native-push-notification');

Screenshot

Upvotes: 54

Views: 80728

Answers (11)

Akhzar Nazir
Akhzar Nazir

Reputation: 830

1- In iOS message is 'Native module cannot be null'

2- In Android message is 'null is not an object evaluating RNFSManager etc'

Meaning is the same and solutions are different, for both cases you need to link native library manually.

Solution for iOS is run pod install in iOS Directory, then react-native run-ios to re-run the app.

Solution for android is react-native link react-native-fs then react-native run-android to re-run the app.

Note: In android better is to open project in android studio again to avoid any inconvenience.

Upvotes: 1

Tebogo Mahlalela
Tebogo Mahlalela

Reputation: 265

  1. npm i @react-native-community/push-notification-ios
  2. cd ios && pod install
  3. react-native unlink @react-native-community/push-notification-ios

That's how I solved it after struggling for hours.

Upvotes: 3

Chirayu Asati
Chirayu Asati

Reputation: 39

Try command

$pod install 

in YourProject/ios. It worked for me.

Hope it helps?

Upvotes: 0

PaulMest
PaulMest

Reputation: 14985

My issue had the same symptoms but a much different root cause. I had two React Native projects open in two different instances of Xcode. My Metro bundler was still running from Project A and causing problems running Project B in the simulator.

The fix: close the old terminal window spawned by Xcode that had the Metro Bundler running and re-run the project.

Upvotes: 3

simaAttar
simaAttar

Reputation: 507

In my case, running a $ pod install inside /ios directory did the trick!

Upvotes: 11

bear1030
bear1030

Reputation: 49

Please use react native community's ios push notification package instead of native's one.

https://github.com/react-native-community/react-native-push-notification-ios

Remove RCTPushNotification project from your libraries and try to use react-native-community's ios push notification. You need to follow the guide. (There are some differences in xcode and linking.)

Upvotes: 1

Ahmet
Ahmet

Reputation: 61

remove react-native-push-notification in node_modules

run npm install [email protected]

Upvotes: 4

Jitendrasinh Zala
Jitendrasinh Zala

Reputation: 171

if it helps someone. Manual link the library in node_modules/react-native/libraries/PushNotificationIOS/RCTPushNotification.xcodeproj for ios https://facebook.github.io/react-native/docs/linking-libraries-ios#manual-linking

that's where the manual linking refers to. not react-native-push-notification

Upvotes: 0

Seraj Ahmad
Seraj Ahmad

Reputation: 415

Sometime, if you had another react-native packager already running for a different app. You may see this problem.

Especially if the react-native versions are same and the previously started app requires a native module which is not available in the current app.

In these cases, you can kill the react packager terminal and restart it and problem should go away.

Also if it is the same app and you just upgraded. Make sure that it is linked properly. If not call react-native link again.

Upvotes: 14

夜一林风
夜一林风

Reputation: 1327

The red-box complaints react-native cannot find some symbol <unkown> in PushNotificationIOS.js line 18.

This usually happens when you fail to link the third lib to your target causing NativeModules find nothing at attempt.

To solve this, your Project Navigator -> Target -> General -> Linked Frameworks and Libraries, make sure somelib.a is there.

enter image description here

In your case, please follow the ios install guides and react-native doc

Upvotes: 31

Shivam Sinha
Shivam Sinha

Reputation: 5150

I think this has to do with how to export and import your modules. Make sure each corresponding

If you export your module like this module.exports = moduleName; You should import using var moduleName = require('moduleName');

If export your module using export default moduleName;. You should import using import ModuleName from './ModuleName;

Review all your exports and imports.

Upvotes: 3

Related Questions