-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Invariant Violation: new NativeEventEmitter()
requires a non-null argument
#294
Comments
Yes I did, I deintegrated pods, reinstalled them, even deleted all derived data because, why not and I am always running the app with |
@riamon-v I highly doubt it could be because of the expo. I mean - a lot of people were using this library with expo and didn't complain that this package had some kind of conflicts 🤷♂️ Would it be possible for you to use binary search (keep I think it would be the only one way to check where is the conflict. If you figure out where is the conflict and can provide a minimal reproduction example, then for sure I will try to figure out what is going wrong and how to fix it 👀 What do you think about it? |
@riamon-v by the way - does it happen only on iOS? Is |
Haven't tested on Android yet, and yes my Podile.lock changes when reinstalling. I will try to find out if there is any package that can interfere as suggested |
@riamon-v have you found any solution by chance? |
## 📜 Description Avoid deep worletization of `react-native` package. ## 💡 Motivation and Context It looks like in specific project setup babel plugin may try to serialize entire `react-native` package (see #393 for more context). To avoid that in this PR I'm extracting `Platform.OS` into separate `OS` variable, so that babel plugin will capture only value of `OS` (and not entire `Platform` object). Closes #393 and #294 ## 📢 Changelog ### JS - extract `Platform.OS` into separate `OS` variable ## 🤔 How Has This Been Tested? Tested in the project where this error occurs. ## 📝 Checklist - [x] CI successfully passed - [x] I added new mocks and corresponding unit-tests if library API was changed
Describe the bug
I just installed the package in my React Native project and wrapped my whole app into the
KeyboardProvider
provided.The app can't seem to run afterwards.
The app is a bare React Native workflow implementing
expo-modules-core
Here is a snippet of my package.json, maybe there is a conflict ?
My
App.tsx
, is just a simple component with the wrapper inside, nothing fancyHere is the error:
The text was updated successfully, but these errors were encountered: