-
-
Notifications
You must be signed in to change notification settings - Fork 596
ReactNative - EventEmitter bug #1412
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
Comments
Thanks for opening this issue!
|
Please note that I have tried everything in all the related and/or duplicated issues. |
@davimacedo should this issue stay in this repo or be moved to the react repo? |
This issue belongs to this repo. @camdagr8 are you using cli or expo? |
React-Native 0.70.0 Simplified and rewrote the EventEmitter. Can you try updating? |
For those still having errors with this and landing here (probs because they still on an older version of Parse, like myself)
|
So if this issue has been solved, can we close it? And why is #1999 pointing to this issue if it's solved? |
You can close it. I didn’t realized this was solved until just know. Any import issues involving live query is most likely event emitter related. |
Closing, see explanation above. So #1999 is actually a new feature that doesn't have an issue yet, right? |
New Issue Checklist
Issue Description
Unable to use Parse in React Native
0.65.1
Steps to reproduce
import Parse from 'parse/react-native';
Actual Outcome
Error:
Environment
0.65.1
Client
3.3.0
The text was updated successfully, but these errors were encountered: