-
Notifications
You must be signed in to change notification settings - Fork 25.1k
[Bridge & Packager] Module resolution issues after 0.7.0-rc.2 upgrade. #1808
Copy link
Copy link
Closed
Labels
Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.
Description
I wanted to test 0.7.0-rc.2, so I made the update and tried running my application. Now, everytime I stop the packager, and it restarts, I get this error:
2015-06-30 11:10:55.714 [error][tid:main][RCTModuleData.m:119] SMXTabBarManager is returning nil for it's methodQueue, which is not permitted. You must either return a pre-initialized queue, or @synthesize the methodQueue to let the bridge create a queue for you.
(I am not sure that is related to the module resolution, so, I can move that to its own issue if needed)
However, that "goes away" after a second, and it replaced by module resolution errors. I am using a few 3rd-party modules, which worked fine in 0.6.0. However, now I am getting Unable to resolve module errors. This even happens when trying to require react-timer-mixin.
Furthermore, when it actually can find and import the module, that module's code then can't resolve core RN modules. Example:
Unable to resolve module NativeModules from [project_path]/node_modules/react-native-keyboardevents/KeyboardEvents.ios.js
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.