IOS Shouldapplyexclusivetouch, * *-[xxxx respondstoselector:]: Message sent to Deallloc instance

This problem typically occurs when zombie objects are called and crashes when the Zombie object method is invoked.

For the Zombie object mode how to set up, own Baidu, here only analyze three possible reasons:

1.block deferred execution, causing block code blocks to invoke object methods after the object may disappear

2. If the zombie mode + global breakpoint is set, still crashes in the main function, it is likely that the xib line, such as Xib button Point method in the code has been deleted, but the Xib connection has not been removed, causing bad lines, may cause a crash

3.UIview animation + Strong reference ring: For example: A controller set B control for the strong properties, b control Click a page add a B control to view, and do animation and enter the C page, C page return directly call a controller's destruction method. This creates a reference loop: B-a,a cannot be released (because B is the strong attribute, and b clicks on it and is addsubview by A's view), and the B control persists. If you're on a page and you click on one of the other pages and crash into the main function, that's probably why.

Here I met the reason three, the solution is that when the B control is clicked, the B control is removefromsuperview and the B control property is set to weak.

More questions, please Gathen discussion: 565191947