App Crashes with unrecognized selector about touchvisualizer

[zarghol]

have the same problem in iOS 10 when I try to perform a segue (custom transition).
I fixed it but since I wait for merge the pull request for iOS 10, I can't send it unitary.
here it is : zarghol@dbaafdf

[morizotter]

Thanks for your backlogs!

[krunalsheth]

can you please explain why is swizzledDescription there in first place? what purpose does it serve?

[morizotter]

When application becomes active, UIWindow's swizzle() method would be called. At that time, TouchVisualizer switches sendEvent with the custom sendEvent. But if this swizzle() method were called multiple times, it would switch methods again. To prevent this behavior, I created swizzlingMessage and changed description.

When swizzle() are called, checks if description contains this message first. And do nothing if description contains this swizzlingMessage . This is a hack. But there have to be a better way...

@krunalsheth

[krunalsheth]

okay i see that in code now. I am new to "method swizzling" . so this may be a naive question. can you please explain why the "swizzle" needs to happen only when application becomes active? can't you do the same when Visualizer.start is called? with the current implementation, TouchVisualizer doesn't work if someone calls Visualizer.start long after application is started (imagine you have a "presentation mode" switch in the app and you want to show TouchVisualizer only when someone turns the switch) @morizotter

[morizotter]

can you please explain why the "swizzle" needs to happen only when application becomes active?

I think it is because when user write Visualizer.start() in application: didFinishLaunchingWithOptions: it was too late because UIWindow maybe create after Visuzlizer.star(). At first stage of this library, Visualizer.start() is supposed to write in application:didFinish....

[krunalsheth]

@morizotter are you saying Visualizer.start() need to be called only during application:didFinish? if so, i think documentation needs to be updated.

my original question was, can the code to swizzle be called inside Visualizer.start ? would that not work?

[lm2343635]

I have same problem in my app.