-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
RCTVideo re-registered direct event topReadyForDisplay as a bubbling event. #1618
Comments
Same problem here :/ |
Do you have a list of RN libraries installed? |
The error is dismissable, right? |
@CHaNGeTe The error is dismissable, yes. We are using expo on this project, and one of my team members indicated that expo's video functionality seems to be causing the conflict here. |
update on this! I was able to completely remove "EXAV" (which is expo-av in node_modules which is a piece of Expo) and removing that fixed the error. Basically, react-native-video is declaring a type of listener that is named the same as a listener that expo-av declares (this is my understanding of the issue at least). So that's why removing expo-av fixes the problem. Now, I haven't figured out how to exclude expo-av from being included when you're using expo (I think the solution is unimodules somehow but it's still getting pulled in) so when you "clean" the project (delete node modules, reinstall, update pods, etc) the problem comes back, and you would have to manually remove all the references to EXAV again. If anybody has insight on the above ^ problem that would be super helpful. |
@annie-elequin just curios, and I can not test it right now. |
Thanks @CHaNGeTe. Let's test this branch out @annie-elequin |
Nice find @CHaNGeTe. Didn't know DirectEventBlock was an option. |
Yeah that looks promising! I tried it out, by adding this as the entry in package.json: However, when I do that it's not getting all of the file from the branch (notably, |
Probably I branched from the wrong side, let me update the branch with only changes from master and let you know |
try this one, notice the |
it worked! Thanks so much @CHaNGeTe |
Please @annie-elequin, can you test the updated branch? (I pushed some more changes) |
Fixed on 4.4.2 |
This is still an issue. |
Where did you aded exactly? |
Bug
Environment info
React native info output:
Also, this is running in the context of Expokit SDK 33.
Library version: 4.4.1
Steps To Reproduce
No idea what is causing this.
Describe what you expected to happen:
Reproducible sample code
The text was updated successfully, but these errors were encountered: