-
Notifications
You must be signed in to change notification settings - Fork 923
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
Message Sent to Deallocated Object #96
Comments
Hmm, interesting. What's the full stack trace at the time of the crash? |
The |
at the time of the crash, this method - (UIView*)TPKeyboardAvoiding_findFirstResponderBeneathView:(UIView*)view {
// Search recursively for first responder
for ( UIView *childView in view.subviews ) {
if ( [childView respondsToSelector:@selector(isFirstResponder)] && [childView isFirstResponder] ) return childView;
UIView *result = [self TPKeyboardAvoiding_findFirstResponderBeneathView:childView];
if ( result ) return result;
}
return nil;
} has the following properties: |
also, just tested on iOS6.1 to compare and it does not occur. only seems to be on iOS7. i deleted a previous comment to keep clarity here and try and make all of this a little more concise. I've narrowed down the scenario to be: |
I implemented next method in my category on TPAvoidingKeyboardScrollView:
It works for me. |
So, I have TPKeyboardAvoidingScrollviews in a couple nibs. I don't really reference them in the code so they usually don't have an
IBOutlet
at all.I'm experiencing an issue where I'm getting the dreaded
Message Sent to Deallocated Object
crash. I can reliably reproduce this by going through my applciation to a certain point, hitting a button that triggers apopToRootViewControllerAnimated:NO
. I can then go to a certain screen and reliably crash the application.The crash occurs in
UIScrollView+TPKeyboadAvoidingAdditions.h
here:Heres some retain counts and the line it's dying on, spit out by the profiler:
whatcha think? this issue is triggered by me calling
becomeFirstResponder
on a textview inviewDidAppear
. It works fine unless I go through the application a little first. I dont understand where the hook is that could cause this... is there some way the lilbrary could be holding on to a reference to one of my VC's? Could it be related to the notifications that get observed for & posted?thanks for the great library!
The text was updated successfully, but these errors were encountered: