I am writing a program that I hope to get into the App Store. During testing,
all went well - no errors, no crashes, nothing to be concerned about. Having
Archived it, and exported a Developer ID-signed Application (for further
testing), I find myself facing a rather annoying problem. My program still
works correctly (no crashes or problems of that nature), but the console is
showing the following error on a regular basis:
25/04/2013 13:02:06.100 sandboxd[701]: ([458]) DeviceInfo(458) deny hid-control
How can I track down what is causing this 'deny hid-control' error? The full
report leaves me none the wiser:
DeviceInfo(458) deny hid-control
Process: DeviceInfo [458]
Path: /Applications/DeviceInfo.app/Contents/MacOS/DeviceInfo
Load Address: 0x100000000
Identifier: com.paxsoftware.DeviceInfo
Version: 1 (1.0)
Code Type: x86_64 (Native)
Parent Process: launchd [178]
Date/Time: 2013-04-25 13:02:06.093 +0100
OS Version: Mac OS X 10.8.3 (12D78)
Report Version: 8
Thread 0:
0 libsystem_kernel.dylib 0x00007fff98e9e686 mach_msg_trap + 10
1 CoreGraphics 0x00007fff954ed259 _CGSPostEventRecord
+ 201
2 CoreGraphics 0x00007fff956b1494
encode_event_record_for_posting + 42
3 CoreGraphics 0x00007fff9530d645 CGSEncodeEventRecord
+ 117
4 CoreGraphics 0x00007fff956b1458 CGSPostEventRecord +
657
5 Ink 0x00007fff96373f01 -[InkClientSideEvent
repostCGEventToCGConnection:markAsReposted:] + 155
6 Ink 0x00007fff96364dc7 -[InkContext
dispatchQueuedEvent:withDisposition:andRepostType:isFinalDispatch:] + 472
7 Ink 0x00007fff96364ad0 -[InkContext
metaDispatch:triggerEventDisposition:] + 560
8 Ink 0x00007fff963645eb -[InkContext
inspectEvent:] + 929
9 Ink 0x00007fff96363145
_InkInspectCarbonEvent + 202
10 HIToolbox 0x00007fff96d0431e InkPreflight + 413
11 HIToolbox 0x00007fff96cfbc8c
AcquireEventFromQueue + 270
12 HIToolbox 0x00007fff96cf1c77
ReceiveNextEventCommon + 393
13 HIToolbox 0x00007fff96cf1ae3
BlockUntilNextEventMatchingListInMode + 62
14 AppKit 0x00007fff8da9e563 _DPSNextEvent + 685
15 AppKit 0x00007fff8da9de22 -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
16 AppKit 0x00007fff8da951d3 -[NSApplication run]
+ 517
17 AppKit 0x00007fff8da39c06 NSApplicationMain +
869
18 DeviceInfo 0x0000000100001db4 start + 52
Thread 1:
0 libsystem_kernel.dylib 0x00007fff98ea0d16 kevent + 10
1 libdispatch.dylib 0x00007fff9730e9ee _dispatch_mgr_thread
+ 54
Thread 2:
0 libsystem_kernel.dylib 0x00007fff98e9e686 mach_msg_trap + 10
1 CoreFoundation 0x00007fff91697233
__CFRunLoopServiceMachPort + 195
2 CoreFoundation 0x00007fff9169c916 __CFRunLoopRun + 1078
3 CoreFoundation 0x00007fff9169c0e2 CFRunLoopRunSpecific
+ 290
4 CoreFoundation 0x00007fff916aadd1 CFRunLoopRun + 97
5 Foundation 0x00007fff8fc4ccd2 __NSThread__main__ +
1345
6 libsystem_c.dylib 0x00007fff8d24c7a2 _pthread_start + 327
7 libsystem_c.dylib 0x00007fff8d2391e1 thread_start + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff98ea06d6 __workq_kernreturn +
10
1 libsystem_c.dylib 0x00007fff8d24ed13 _pthread_wqthread +
412
2 libsystem_c.dylib 0x00007fff8d2391d1 start_wqthread + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff98ea06d6 __workq_kernreturn +
10
1 libsystem_c.dylib 0x00007fff8d24ed13 _pthread_wqthread +
412
2 libsystem_c.dylib 0x00007fff8d2391d1 start_wqthread + 13
Binary Images:
0x100000000 - 0x10000cff7 com.paxsoftware.DeviceInfo (1.0 - 1)
<543C3BAA-C385-3E8F-8F7B-6D9AA0B421D0>
/Applications/DeviceInfo.app/Contents/MacOS/DeviceInfo
0x7fff8d238000 - 0x7fff8d304ff7 libsystem_c.dylib (825.26)
<4C9EB006-FE1F-3F8F-8074-DFD94CF2CE7B> /usr/lib/system/libsystem_c.dylib
0x7fff8d949000 - 0x7fff8e576ff7 com.apple.AppKit (6.8 - 1187.37)
<FAEA8B77-210F-3C0F-B9CF-85A7595CCA26>
/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff8fbb7000 - 0x7fff8ff14ff7 com.apple.Foundation (6.8 - 945.16)
<89BD68FD-72C8-35C1-94C6-3A07F097C50D>
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff91667000 - 0x7fff91851ff7 com.apple.CoreFoundation (6.8 -
744.18) <A60C3C9B-3764-3291-844C-C487ACF77C2C>
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff951bc000 - 0x7fff95b4c6ff com.apple.CoreGraphics (1.600.0)
<4953961C-96DC-39D7-ADF5-B767F2A7E4E1>
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
0x7fff9635f000 - 0x7fff963fdff7 com.apple.ink.framework (10.8.2 - 150)
<84B9825C-3822-375F-BE58-A753444FBDE2>
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x7fff96c92000 - 0x7fff96fc2fff com.apple.HIToolbox (2.0)
<656D08C2-9068-3532-ABDD-32EC5057CCB2>
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x7fff9730a000 - 0x7fff9731fff7 libdispatch.dylib (228.23)
<D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
0x7fff98e8e000 - 0x7fff98ea9ff7 libsystem_kernel.dylib (2050.22.13)
<5A961E2A-CFB8-362B-BC43-122704AEB047> /usr/lib/system/libsystem_kernel.dylib
My software gets notifications of which USB devices are connected by the method
described here (thanks Apple!), and this method appears to work still - albeit
that error messages are raised. Any suggestions for how to fix this would be
gratefully received. In fact, is this still the approved method for getting
USB notifications in sandboxed apps?
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
