With upcoming iOS versions the swizzling of NSCFMutableArray's and NSCFMutableDictionary's addObject: fails, as the class clusters now also have __NSCFMutable* classes which will not respond to the swizzeled selectors as they were not added.
I only looked into the crashes for 5mins or so there might be more/other causes for it.
Add the method to the other classes could fix that.
In general we could (should?) look into a way to not swizzle the whole programs behaviour with added nils to arrays and only do so in a nu context?
Any ideas/pointers @timburks ?
With upcoming iOS versions the swizzling of NSCFMutableArray's and NSCFMutableDictionary's
addObject:fails, as the class clusters now also have__NSCFMutable*classes which will not respond to the swizzeled selectors as they were not added.I only looked into the crashes for 5mins or so there might be more/other causes for it.
Add the method to the other classes could fix that.
In general we could (should?) look into a way to not swizzle the whole programs behaviour with added nils to arrays and only do so in a nu context?
Any ideas/pointers @timburks ?