I'm a bit rusty on this but this came up in 2011 and the solution was to reinstall the OS -> https://discussions.apple.com/thread/3067155?answerId=15233086022#15233086022
No, this is a developer error on your part. You must call the completion handler, passing it a value before the function returns. Please provide a copy of you're calling the handler.
Try the test functions from this snippet and see if the outcome is the same:
https://android.googlesource.com/platform/external/libusb/+/HEAD/examples/xusb.c
https://cpp.hotexamples.com/examples/-/-/libusb_control_transfer/cpp-libusb_control_transfer-function-examples.html
https://github.com/Codingboy/ucuni/blob/master/src/example.c
Regardless of the application being developed by whom, knowing what applications or services are running outside your sandbox is a privacy overreach. Stick to jailbreak detection and debugger attachment checks to terminate your application accordingly.
I'm a bit rusty on this but this came up in 2011 and the solution was to reinstall the OS -> https://discussions.apple.com/thread/3067155?answerId=15233086022#15233086022
No, this is a developer error on your part. You must call the completion handler, passing it a value before the function returns. Please provide a copy of you're calling the handler.
Try the test functions from this snippet and see if the outcome is the same:
https://android.googlesource.com/platform/external/libusb/+/HEAD/examples/xusb.c
https://cpp.hotexamples.com/examples/-/-/libusb_control_transfer/cpp-libusb_control_transfer-function-examples.html
https://github.com/Codingboy/ucuni/blob/master/src/example.c
Regardless of the application being developed by whom, knowing what applications or services are running outside your sandbox is a privacy overreach. Stick to jailbreak detection and debugger attachment checks to terminate your application accordingly.