SIGABRT in TMReachabilityCallback
Sega-Zero opened this issue · 1 comments
Sega-Zero commented
Using Reachability via Cocoapods in swift project. Sometimes catching a crash like this:
Cannot reproduce this crash, but I catch it on device only.
Could it happen because I call stopNotifier in instance owner deinit?
Probably, the object has been already deallocated, but a block in reachabilitySerialQueue
is still executed. Wouldn't it be better to pass self in context.info
using __bridge_retained
so no garbage will pass in the callback?
chrisballinger commented
We are also seeing this crash. Changing to __bridge_retained
and __bridge_transfer
introduced even more crashes.