-
Notifications
You must be signed in to change notification settings - Fork 56
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
Update react-native-webrtc
#70
Comments
thanks for the heads up |
I'm about to publish a release with the updated react-native-webrtc, but I am seeing this error in my local build: 2024-03-12 19:38:34,445 ERROR: Unused scanignore path: app/mobile/node_modules/react-native-webrtc The build succeeds without that line, but I don't understand why that line is no longer needed. Should I submit a PR to remove that scanignore? |
Do that, will look at the CI output then. |
Should I remove the scanignore on the last built version in the yml ...or publish a new release, allow the build to fail, and do the PR on that failed version yml? |
Don't edit an already built version. Open a MR with a new build block, or if on autoupdate and if updated, with a one-line fix. |
I opened a MR with a new build block. I apologize if I missed something obvious. Thank you for your help. |
@licaon-kter is there any concern with me adding http support:
Several people have requested that I support IP based addressing for communication over their LAN. The above line would need to be added to the AndroidManifest.xml |
It's not, but it's discouraged... :( |
Sounds good. I will leave it off and inform the users that it's not supported. |
I mean, self-signed does not work? That's half way there, not cleartext but no need for CAs and etc. |
I think that might work, but I don't imagine it's easy to load the self-signed cert into the phone OS to establish trust with that server. |
......to fix CVE-2023-5217: Heap buffer overflow in vp8 encoding in libvpx
Wait on upstream: react-native-webrtc/react-native-webrtc#1480
The text was updated successfully, but these errors were encountered: