Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I was wondering if anyone knew how iSimulate automatically registers/hooks itself into a debugged iDevice application? It’s as simple as including the static library (and a couple of frameworks) and it just works. There are no methods or functions to call. How is this possible?
Short answer: using categories in Objective-C, you can extend or augment any class in the system, including core classes and NSObject itself. (Similar to “monkey patching” in Ruby for example.)
The actual communication is most likely a broadcast, sending packages that don’t expect to get an answer back. When you start your app, it just starts intercepting these packages. So it’s the simulator app that hooks into the iSimulate stream, rather than iSimulate somehow “reaching into” your app.
Have a look at the open source accelerometer simulator project. You could easily extend it to broadcast touches too, and basically duplicate what iSimulate does. And you learn about the nifty side of Objective-C.