ezranbayantemur / react-native-rtmp-publisher

📹 Live stream RTMP Publisher for React Native
MIT License
102 stars 16 forks source link

Crash on switching off the internet #9

Closed rranjan14 closed 1 year ago

rranjan14 commented 1 year ago

Describe the bug As soon as the internet connection is closed, handleOnConnectionFailed handler is called and the app crashes.

To Reproduce Steps to reproduce the behavior:

  1. Create a View with
  2. Start streaming.
  3. Switch off the internet.
  4. Application crashes as soon as the handleOnConnectionFailed callback is received

Expected behavior Streaming should stop but the application should not crash.

Smartphone (please complete the following information):

Stacktrace: Link to stacktrace

ezranbayantemur commented 1 year ago

Hello, @rranjan14 I tried to reproduce that issue but my app didn't crashed. I updated android package to 2.2.2 by 0.4.6 version.

Can you try it again?

rranjan14 commented 1 year ago

I did try. Same result again. I get Error send packet, Broken pipe message in the onConnectionFailed handler, and then it crashes.

ezranbayantemur commented 1 year ago

I've tried to reproduce your issue but it looks like its not crashing. Maybe it's about your device. I think looking at logcat outputs will help

https://user-images.githubusercontent.com/42299721/211173192-1ba65ad0-6ca1-449e-bebb-95a95ec8b508.mov

rranjan14 commented 1 year ago

I'll verify once again and attach the log file if i encounter the same issue.

rranjan14 commented 1 year ago

https://user-images.githubusercontent.com/47914095/211361641-52f9bd6d-1c65-42bf-8d1f-1834ef138d08.mp4

Not sure of the behaviour on emulator, but on real device, it still is crashing. I also got the message Connection Failed: Error send packet, Broken pipe from the onConnectionFailed handler. I'll try and attach the log file. Do you want logs specific to the app or complete session log?

ezranbayantemur commented 1 year ago

Yes, can you give me the Logcat output of the crash timestamps?

ezranbayantemur commented 1 year ago

@rranjan14 I'm closing this issue as resolved. You can open it again if it happens again.