Make sure you're using the latest version of TurboActivate (currently 4.0.9.6). If you're still having problem, a way to reproduce the problems is needed in order to give you any sort of useful help.
Hello,
I am having some odd problem. Odd in a sense that the error occurred with one of the clients only. The same application runs without any error on other machines. The error I am getting is, 'The systa process ended before the response could be delivered'
Even weirder is, the lower version of the same application runs without any error on that machine. At my end, I have never touched the core files like systa, TurboActivate.dat and libTurboActivate.dylib ever since it has been used in the application.
I have also checked whether the systa file has write permission as listed here https://wyday.com/limelm/help/using-turboactivate-with-adobe-air/ But this has not helped to solve the issue. Please check screenshot of the terminal of my client at here, https://www.dropbox.com/s/bdjfps80el0iut8/Screenshot%202018-02-02%2016.00.46.png?dl=0 The customer is using Mac 10.7.5.
The error occurs when the application is launched at the beginning. Tried uninstalling and re-installing the application numerous time. What other details do you want ?
Thanks
Make sure you're using the latest version of TurboActivate (currently 4.0.9.6). If you're still having problem, a way to reproduce the problems is needed in order to give you any sort of useful help.
I have downloaded the latest version from this url, https://wyday.com/limelm/help/using-turboactivate-with-adobe-air/ So, I guess I am already using 4.0.9.6 .
I am unable to reproduce the error on my machine. The error is occurring when IsGenuineEx () is fired. What else details do you need ?
A way to reproduce this.
My guess:
Something is "helpfully" killing the process (rogue anti-virus programs, etc.). Tell them to uninstall all garbage 3rd party anti-virus and only use Windows Defender. It's free, it's lightweight, and it doesn't do stupid things.
And one important thing is, if any of these 3rd party pluggins are hampering the application, then how are we able to install and run flawlessly the lower versions ?
I don't understand the question.
The problem: something is killing the systa process. Stop whatever is doing it.
The ability to reproduce the problem will let you provide enough information to us so we can see if it's a bug in our products. But from what you've said so far this looks like a problem on the user's machine.
My point is straight forward, if there are things that are killing Systa, then how the older version of Systa is running fine.
Is your systa file compatible upto any certain version of Mac ?
It's likely a problem on that particular customer's computer. Again, it's a guess. If you could reproduce it we could give you an actual answer and an actual solution.
A way to reproduce the problem they're having. Whatever details you need to get that end-result is what you need.
I've replied multiple times. there's only so many ways I can say it:
1. We can't reproduce this. As far as we know from the information provided this is an end-user mistake. What exactly they're doing is a mystery, but it's not a mystery we're willing to devote resources to. Why? Because not enough information is provided. Which brings me to point 2 (which I've said multiple times already)...
2. Provide a way to reproduce this and we'll be able to provide better feedback.
Hi Wyatt
I have today freshly installed OS X Lion (10.7) on my Mac.
I have opened the most recent version of my software product (v3.6) and it produced the error:'The systa process ended before the response could be delivered'.
I have opened the older version of my software product (v2.1) and it ran without issue.
As I mentioned above, this is a fresh install, there is no other software installed on the machine.
Therefore the way to replicate the error is to run the software on OS X Lion (10.7).
ThanksNick
Are you using the latest systa process?
Are you using the lastest Adobe AIR class files?
Are you using the latest libTurboActivate.dylib?
Correct me if I am wrong,
I have downloaded the latest version from this url, https://wyday.com/limelm/help/using-turboactivate-with-adobe-air/
Therefore, I guess I am using 4.0.9.6 along with latest Systa and libTurboActivate.dylib file.
And, I am using Adobe Air SDK 26.0.0.1
By way to reproduce the problem I mean code. Not pre-compiled binaries. I need a simple code example to reproduce what you're seeing.
Best place to start: our example. Just run it as is. Do you get an error?
If not, that suggest the problem might lie in how you're using the TurboActivate class in Adobe AIR. Adobe AIR has lots of problems (besides the fact that Adobe has all but abandoned it as a language).
Not least of which is that there's no synchronous execution of dlls.
What does this mean? It means you must only execute TurboActivate functions from one thread in your app at a time. The example app shows this. Your app may not being doing that.
Long story short: I need a way to reproduce this with a code example. The smaller the code example the better.
Hello,
Sorry was away for a bit with personal work. We have integrated latest AIRSDK i.e. 28.0 and still got the same error.
To make your life easier, we were able to reproduce the same error with the example code from your website.
So, the error is definitely at your end. Let me know how to email you the code and we hope this would be resolved fast as possible.
Thanks
So the technical description is
' The Systa process ended before the response could be delivered. '
This occurs on OS X Lion (10.7)
To reproduce error, simply run your example code on OS X Lion.
If needed, we can send you a code as well.
Thanks
The latest version of systa only supports macOS 10.8 and newer. This is by design. Why? Because Apple dropped support for 10.7 about 4 years ago (and it has known security vulnerabilities that will continue to go unfixed).
For non-Adobe Air / NodeJS languages you still have the option of using libTurboActivate.dylib built for 10.5 and newer (the libstdc ++ version).
Adobe Air and NodeJS require systa, which in turn requires 10.8 or newer.
Im glad we finally solved this mystery (why we couldnt reproduce it is because we were testing on supported versions of macOS)