John MacMullin wrote:
> Anyone have an idea of what is causing this message in the log file?
>
> AppleEvents: Send port for process has no send right, port=(
port:37207/0x9157 rcv:1,send:0,d:0 limit:5)
(findOrCreate()/AEMachUtils.cp #526)
Nope, although you're obviously not the only one. Given what an
ill-documented pig the Apple event stack is (and this error is way down
where it bridges to Mach messages, where even more dragons lie
<https://developer.apple.com/library/mac/documentation/Darwin/Conceptual/KernelProgramming/Mach/Mach.html>),
you might want to go straight for a TSI
<https://developer.apple.com/support/technical/> and see if that does
any good. No guarantees - I think there's very few folk at Apple these
days who give a crap about this stuff, and even fewer who know what
they're doing - but if they do give a useful response it will save no
end of time and frustration.
> I am using scripting bridge for several Apple program interfaces.
Essential troubleshooting steps for any Apple event-based IPC problem:
1. If your apps are sandboxed, disable it and see if that makes any
difference.
2. If you're using Scripting Bridge or JavaScript for Automation,
rewrite the relevant code in AppleScript, which is the de facto
standard, and try that:
* If it works in AppleScript then the problem is that SB/JXA are crappy
broken junk which don't speak Apple events correctly/competently, in
which case stick to using AppleScript. (It may be a rotten language, but
it's the only _supported_ option that does Apple event IPC right.) FWIW,
the AppleScript-ObjC bridge takes most (though not all) of the pain out
of bridging between the two: Shane Stanley's the go-to guy for ASOC
questions, and there's a brief how-to here:
<http://appscript.sourceforge.net/asoc.html>.
* If it doesn't work in AppleScript, then the problem is down in the OS,
at which point all you can do is dig the web to see if anyone else has
gotten a solution, or put in a TSI and hope it won't just be a waste of
a perfectly good ticket.
3. If you've got some cases that are working and some that aren't, you
could try running with `AEDebug` options enabled
<https://developer.apple.com/legacy/library/documentation/AppleScript/Conceptual/AppleEvents/AppleEvents.pdf
> and see if you can spot discrepancies in the logged messages that
might give clues. At the least, it'll give you more data to include in
your ticket in case they can't replicate it themselves.
HTH
has
_______________________________________________
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
