Crash on reload after calling `new RTCPeerConnection()` on iOS
See original GitHub issueIf I call new RTCPeerConnection()
and then change my code so that a live reload is triggered, the app crashes every time. It’s a nightmare trying to develop this way. Does this happen for everyone?
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
iOS 15 Safari WebRTC Issue | Apple Developer Forums
We're encountering an issue on the iOS 15 Beta when establishing a WebRTC connection through Safari, where we are not receiving the remote...
Read more >RTCPeerConnection.addTrack() causes app to crash when a ...
When we test Unified Plan mode on Android, basic calls work fine. However, when we initiate an audio call on iOS, the app...
Read more >App crash when reload button is pressed - ios - Stack Overflow
Simply pressing alt and drag the button to my ViewController.swift and create the action IBAction. Where should i put this code? Sorry, but...
Read more >RTCPeerConnection.setRemoteDescription() - Web APIs | MDN
The RTCPeerConnection method setRemoteDescription() sets the specified session description as the remote peer's current offer or answer.
Read more >Outputs to collect in the event of crash or unexpected reload
Catalyst 9000 Series Switches. Basic Checks. When did the reload/crash happen? Did the switch recover automatically after the crash?
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Should be fixed by https://github.com/oney/react-native-webrtc/pull/68 and https://github.com/oney/react-native-webrtc/commit/3405429227151e328abd182142667cae1b43d7a1 Available on 0.7.0
Can be reproduced in my device now, I will solve it.