-
Notifications
You must be signed in to change notification settings - Fork 259
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
Line in swizzledDealloc triggers exception breakpoints #11
Comments
Check this question (Ignore certain exceptions when using Xcode's All Exceptions breakpoint) from StackOverflow. |
Why would you even swizzle dealloc? It's not because of ARC, is it? You're still encouraged to use dealloc even with ARC, you just don't call Edit: Oh god, please ignore this... it's late here, we're in a category. xD Sorry! :D |
😄 |
How about this approach? #12 |
You can add a dummy view as a subview to the UITextView, and do your remove observer when the dummy view receives See line 196 in SVPullToRefresh.m |
I make a pull request try to not swizzle dealloc. |
And lucky, it also help to solve #12 , because the addObserver and removeObserver is in the same life cycle. |
The exception breakpoint is triggered on the line in the try block, and while it does not crash the app it makes using the app in the debugger a pain because it interferes with my ability to identify other exceptions and test my app.
Is there a way to fix this? or even just special case the exception breakpoint behavior?
It is especially frustrating because it hits that breakpoint for each of the observing keys which typically are the following:
The text was updated successfully, but these errors were encountered: