BAD EX when you leave a view and return to it and open keyboard about skinputclass HOT 4 OPEN

@doctordbx @SunilSpaceo i'm using this lib in production, any ideas on a fix?

from skinputclass.

@doctordbx @SunilSpaceo I think the KVOBlock library you are using has an update for this Tricertops/Block-KVO@f4e5450 I'm gonna try this myself and see if it fixes my crashes

from skinputclass.

@hamin Let me know how you get on please.

from skinputclass.

@doctordbx @SunilSpaceo so I figured it out. It was an issue with that KVOBlock library. I was able to reproduce this bug very consistently:

• Have Two fields, one UITextField and one SKDigitField
• Tap on SKDigitField first
• Dismiss your view controller
• Launch transition to same view controller again
• Tap on SKDigitField or the other UITextField
• You get a BAD EX crash

Using the Zombies template in Xcode Instruments I noticed that there was a Zombie (object wasn't dealloced and was being sent a message).

The culprit is actually iMartinKiss's KVOBlock library.

From what I can tell SKInput is only using that library for one method, the removeAllObservations method.

This is actually not necessary and I don't quite see the point of using that lib for this class especially since there is no direct KVO manipulation going on. SKInput is subscribing to events via NSNotificationCenter.

My solution:

• Comment out all occurences of removeAllObservations ( I found two [doneButton removeAllObservations] )
• Add a dealloc method to properly remove observations

-(void)dealloc{
    [[NSNotificationCenter defaultCenter] removeObserver:self];
}

Essentially I think you can remove KVOBlock library completely from SKInput since you're not really using any block handlers for direct KVO handling at all @SunilSpaceo

This solved my crashes :)

from skinputclass.