-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to resolve module @react-native-community/push-notification-ios
from ~/Code/React/MYS_Copy/node_modules/react-native-push-notification/component/index.ios.js
#1176
Comments
@react-native-community/push-notification-ios
from /Users/tholhubner/Code/React/MYS_Copy/node_modules/react-native-push-notification/component/index.ios.js
@react-native-community/push-notification-ios
from ~/Code/React/MYS_Copy/node_modules/react-native-push-notification/component/index.ios.js
Have you solved this issue? I am now running into this issue too. |
I found the solution, you can try to delete
in metro.config.js |
@nhiicts I removed that whole "resolver" section but it didn't help. |
Any update on this issue? |
in my case, when I deleted the "resolver" section my app still refused to load.... but it was because I needed some of the blacklist entries for proper bundling. this is what i ended up with that allowed the react-native-community/push-notification-ios package to be resolved by metro: // https://github.com/janeasystems/nodejs-mobile-react-native/tree/ed727edea17e8a9e1a85cef3413becc83b8a0328#duplicate-module-name
// https://github.com/facebook/metro/issues/265#issuecomment-424334996
const blacklist = require('metro-config/src/defaults/blacklist');
module.exports = {
resolver:{
blacklistRE: blacklist([
// /node_modules\/.*\/node_modules\/react-native\/.*/,
/nodejs-assets\/.*/,
/CodePush\/.*/,
/android\/.*/,
// /ios\/.*/
])
},
}; |
@tholhubner i was running into the same issue, but this lib uses the @react-native-community/push-notification-ios (as stated in installation instructions). I think this issue can be closed. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions. |
I am in the middle of upgrading our project to 0.60.5 and I am now running into this issue:
I have the dependency installed and I am completely up to date on this package as well, but I still seem to be getting this error. I have done all the typical steps, clearing watchman, removing node_modules, clearing npm caches, but nothing seems to solve this issue.
If anyone has any suggestions, please send them my way.
The text was updated successfully, but these errors were encountered: