Authentication Error Due to VMAnswered

Can you clarify, if getting this error, should I be still using TA or TF?

APP is using TA currently.   But I read in post later stating should never use TF for virtual machine. https://wyday.com/forum/t/32296/allow-virtual-machines-on-license-with-turbofloat-server-key-by-default/

And yet link suggest it's perfect for it. https://wyday.com/limelm/help/faq/#in-vm

Please advise?  Want to make sure when we recompile with new sdk 5.0.2 with keeping TA in place, that we're addressing issue correctly.

Thank you in advance for your guidance. 

Can you clarify, if getting this error, should I be still using TA or TF?

TurboFloat.

APP is using TA currently.   But I read in post later stating should never use TF for virtual machine. https://wyday.com/forum/t/32296/allow-virtual-machines-on-license-with-turbofloat-server-key-by-default/

No, that says you shouldn't use the TurboFloat Server in a VM, you should use the TurboFloat library in your app in a VM. The TurboFloat Server should run on a real machine.

And yet link suggest it's perfect for it. https://wyday.com/limelm/help/faq/#in-vm

Correct.

Is there any actionscript for turbo float?  

Program is Adobe air.

Unfortunately Adobe has let their AIR product whither and die on the vine. However, you can use Javascript with Adobe AIR (in addition to / or in stead of) Actionscript.

And we have full support for TurboFloat in Javascript.

Thank you Wyatt for your response for Javascript support instead of actionscript. 

Fyi: Know you probably know this, Harman, a subsidiary of Samsung, took over support and future development of Adobe Air.  

https://airsdk.harman.com/

Right now we are using Turbo Activate with the latest version of Adobe Air. Everything works perfectly fine when testing in IntelliJ (0 errors when compiling and debugging). But if I install the application on Mac or Windows my Turbo Activate page never shows up. 

The code for Turbo Activate was never changed for a few years and it worked before. 

Do you think this is some kind of security issue or what exactly should I look for? 

You'd have to add logging to your app to see exactly what is failing. Don't swallow errors. Instead show them or log them.

Make sure you update the integration code and the systa / systf executable files. They’re all required to be updated when updating TurboActivate / TurboFloat.

When debugging with the latest version of TurboActive I got this message:

"libTurboActivate.dylib"
Not Opened

Apple could not verify "libTurboActivate.dylib" is free of malware that may harm your Mac or compromise your privacy.

With two buttons: “Done” and “Move to Bin”

A whole lot more information is needed. Your our pre-built example, make sure you follow the example article.

Thanks! 
From the link you sent: "Inside the folder you copied is a "systa" (or "systa.exe") file and a text file."

Downloading the latest zip archive, I find the TurboActivate.dll file and a TurboActivate.exe file. Should I delete the old “systa.exe” from my project and replace it with this new exe?

Yes.

Ok, I renamed TurboActive.exe to systa.exe since your ActionScript code is looking for the old filename (TurboActivate.as line 85)

But when trying to debug the app on Windows 11 using IntelliJ I get this a popup with this message:

TurboActive

Activation Error

The language file failed to load. Either the file doesn't exist or it's corrupt.

File: 7

If I click “Finish”, the popup closes and my app seems to be working properly. 

The popup also appears if I create and installer and then install the application on my computer and run it. 

Ok, I renamed TurboActive.exe to systa.exe since your ActionScript code is looking for the old filename (TurboActivate.as line 85)

That's wrong. Use the systa.exe file. See the Using TurboActivate with Adobe AIR article.

Ok, I found systa.exe inside the nodejs folder. Is that the one I should include?

TurboActivate.exe needs to also be included in the Windows folder for my Adobe Air project? That exe is something new and I don't really know what to do with it.

TurboActivate.exe is just the TurboActivate Wizard: a completely optional UI that you can include in your app if you want.

Wyatt, I have been working with associate director of Support for Harman, Who directs support for Harman Air & SDK development.   I don't know if you don't have the direct line hook up to him but I can assure you my level of support was fast, responsive, even down to getting code added to next SDK.  I'm going to assume that you would have the same level of support, if not greater.   Harman didn't buy it to phase it out, bought it to continue to develop AIR SDK.   So the eco system is still being developed, supported and engaged in new development.   Would you like for me to send you information for this support side or have you concluded AIR is done and so are you in supporting it?    We have multiple high functioning apps in this eco system and need a security apparatus to integrate seamlessly, like prior Adobe Air SDK versions.   You've been that solution thus far, Please Advise.

As long as AIR exists, and we have customers using it (you're not the only one) we will support it. We're not dropping support until it's officially dead *and* customers have phased away from it.

Notice we still technically support VB6 (a very dead language that Microsoft will not touch no matter how much money you throw at them).

Here's  the response from the associate director of support for Harman air and former developer of Adobe Air.  24 years with org, so I'm passing this on to you as a professional curtesy.

"No, I suspect this is someone looking at Adobe's information (where annoyingly they had called it "end of life" when they handed over to us, but we don't consider this to be EOL). We have the same thing for the Flash Player where security audits flag up the Flash Player as being unsupported (whereas it's only unsupported if it's version 32 or earlier, i.e. from Adobe...). If you can try to point them to our website and encourage them to check with us, it may help, but I don't hold out much hope of getting them to change.."

OK, like I said, we'll support it.