send failure Beta 4.8.3 Mojave only

[hodger]

Still poking around the beta.  The "send" and "reply" mechanisms seem to work fine pre-Mojave.  With Mojave things silently fail.  No errors, just not working.  

greg

[hodger]

Time for some additional detail.  
This is really two issues.  #1, Send/Reply local CPU; #2, Send/Reply to another LAN CPU.
#1 seems less problematic so I'll document issue 1 later.
Here are more specifics for issue 2.

There are two receivers at this IP,  klok is sc473-based, and klok3 is sc483-based.  
The receiving CPU is running Tiger.

Sending script...
send "fubar" to program "eppc://172.20.1.149/klok"
put the result into cd field 1


Receiving script...
on fubar
reply (the ticks)
end fubar

I used the "send" project using multiple operating systems, as well as using both 473 and 483.

Tiger client  --  All 4 send options work as expected, including keychain authentication.
Lion client  --  All 4 send options work but keychain recall does not work across multiple receivers.
Mountain Lion client  --  473 send (x2) results in "could not send session request"
Mountain Lion client  --  483 send (x2) results in error-600
ElCapitain  --  same as Mountain Lion.
Sierra, HighSiera and Mojave  --  same as Mountain Lion.

I skipped over some OS versions as it seems the significant lapse came with Mountain Lion and has not recovered since.

Hope this helps
Greg

[hodger]

For issue #1, without IP addresses etc, the details are more simple.

Sending  script
send "fubar" to program "C11.acgi" without reply

put the result into cd field 1

Receiving script

on fubar
put "We have some fubar here" into cd field 1
end fubar

Sending from both v4.73 and v4.83, Receiving with both v4.73 and v4.83.

Tested Tiger, ElCapitain, Sierra, High Sierra and Mojave.  Only Mojave has issues.

On Mojave, sending 4.73 to 4.73 works, and all the other three possibilities that involve 4.83 fail silently.

Hope this helps,
Greg

[hodger]

...and on a more positive note, "answer program" no longer seems to have all the issues from 4.7.3, which is EXCELLENT!.

Checked on Tiger, ElCap, Sierra, HighSierra, and Mojo.  This was an unexpected surprise after all the issues prior.

[Collection PhotoGraphex]

Hello Greg, 

I may affirm that with the latest SuperCard 4.83d3 Test Universal Builds, AppleEvents a functioning normally. 

I may do further tests, but as for this moment and for severals years, I do use AppleEvents extensively locally, oven an Ethernet network and over the Internet in this form:

request ScriptAE from program ServerAE 

Sorry for this short answer, I may provide further details if necessary. 

I also use SuperCard with MacOS Tiger, but in this case, it could not communicate AppleEvents with a higher MacOS systems. 

HTH

André

[Uli Kusterer]

On 12. Oct 2024, at 10:19, hodger <mkt...@track25.studio> wrote:
> Still poking around the beta. The "send" and "reply" mechanisms seem to work fine pre-Mojave. With Mojave things silently fail. No errors, just not working.
>
> greg

Just out of curiosity, are you using Apple Events to talk to some other apps on other machines (and if I may ask, what apps?), or are you mainly communicating between two SuperCard projects on different computers?

Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de

[hodger]

Just out of curiosity, are you using Apple Events to talk to some other apps on other machines (and if I may ask, what apps?), or are you mainly communicating between two SuperCard projects on different computers?

Cheers,
-- Uli Kusterer 

Hi Uli,

I use commands to talk between various SC Standalones on separate CPUs and VMs on local networks.  I've not spent any time with AE's to/from SuperCard itself or any other apps.  The only exception is receiving events from AAEB (aaeb.net) which does not have any of these reported issues.

My testing was primarily to help stress test the current beta.  Since some of this functionality began to break years ago I only choose versions and OS's that do work, and always check new SC versions in hope of some improvements.  Around a decade ago, I recall someone (probably Mark) pointing out that some of the issues can be worked around by using AppleScript, but haven't used any of those tricks in quite a while.

Greg 

[Uli Kusterer]

On 13. Jan 2025, at 02:39, hodger <mkt...@track25.studio> wrote:
> I use commands to talk between various SC Standalones on separate CPUs and VMs on local networks. I've not spent any time with AE's to/from SuperCard itself or any other apps. The only exception is receiving events from AAEB (aaeb.net) which does not have any of these reported issues.

I see AAEB has not been updated since 2010. Do you know if there's a more modern equivalent? Apple have added newer inter-process communication mechanisms. So just wondering if there's something that wouldn't need Apple Events. Probably not, but since you're doing this, just thought you maybe came across something.

> My testing was primarily to help stress test the current beta. Since some of this functionality began to break years ago I only choose versions and OS's that do work, and always check new SC versions in hope of some improvements. Around a decade ago, I recall someone (probably Mark) pointing out that some of the issues can be worked around by using AppleScript, but haven't used any of those tricks in quite a while.

Cool, thanks for the clues. I'm just thinking in my head what a path going forward would be.