Skip to content

SIGABRT in TMReachabilityCallback #167

@Sega-Zero

Description

@Sega-Zero

Using Reachability via Cocoapods in swift project. Sometimes catching a crash like this:
reachability m 2018-03-26 20-18-11

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions