search

iolate / SimulateTouch

Simulate touch library for iOS
MIT License
512 stars 158 forks source link

deny mach-lookup kr.iolate.simulatetouch #2

Closed schappthority closed 10 years ago

schappthority commented 10 years ago

Hi, I've successfully got the SimulateTouch working on ios7. I'm testing a few apps by sending click events to controllers that I have enumerated.

However, on this specific TestApp, I get two errors from within the library and then a complaint from sandboxd.

Any idea what could be causing this? I'm not quite sure why some apps would work and others would fail, I've been trying to diagnose this all day.

Thanks for your help.

Jan 27 16:27:44 TestApp[627] : Sending click event to: (469.000000,42.500000)! Jan 27 16:27:44 TestApp[627] : ST Error: simulateTouch:atPoint:withType: index:0 type:1 pathIndex:0 Jan 27 16:27:44 TestApp[627] : ST Error: simulateTouch:atPoint:withType: index:0 type:2 pathIndex:0 Jan 27 16:27:44 sandboxd[83] : TestApp(627) deny mach-lookup kr.iolate.simulatetouch

eswick commented 10 years ago

I may be wrong, but I think this is what RocketBootstrap is supposed to solve. https://github.com/rpetrich/RocketBootstrap

schappthority commented 10 years ago

Forgive me, but I don't see how these are correlated. Is it perhaps that ios7 applications have more strict sandbox settings than preios7 apps, and this side steps them? I don't have a lot of background in this specific area, so any insight you can provide would be amazing.

iolate commented 10 years ago

Did you use lastest commit? rocketbootstrap_cfmessageportcreateremote instead of CFMessagePortCreateRemote solved this problem.

schappthority commented 10 years ago

I got rocketbootstrap linked against the project and then compiled into my project via simulate touch.

The random sandbox errors have disappeared, however, the library is still returning errors. Any idea why?

: ST Error: simulateTouch:atPoint:withType: index:0 type:1 pathIndex:0 : ST Error: simulateTouch:atPoint:withType: index:0 type:2 pathIndex:0
schappthority commented 10 years ago

This also occurs now in programs that allowed such events without the librocketboost (ex: Reminders)

schappthority commented 10 years ago

I stand corrected, the device needed to be rebooted. This fixed the issue. Many thanks!