TA 3.2 retrocompatibility

Yes, we made a number of changes and fixes in TA 3.3 making the activation data backwards incompatible. This means if a customer activates with a version of your app that uses TA 3.3+ and then they downgrade your app to a version that uses TA 3.2.2 or lower then they'll have to reactivate.

LimeLM is smart enough to know the computer is the same, though, so it won't really be a problem (it won't use another "activation slot").

Unfortunately these changes were unavoidable (we didn't take them lightly).

Also, I should note the activation data is forwards compatible. So if the user activates with TA 3.2.2 or below, and then they install your app with TA 3.3 or above then they won't notice anything different -- they'll still be activated without having to do anything.

Hello Wyatt,

No, you didn't understand. There is a real problem. Real one.

When I check LimeLM dashboard, I have 2 activations for the same computer :- one for the version with TA 3.3 (the previous activation)- a new one for the version with TA 3.2 that I just reactivate

LimeLM doesn't recognize the computer as the same.

In that case, if I run again my product with TA 3.3, then run my product with TA 3.2 : the product with TA 3.2 is deactivated, so I reactivate it ---> one more activation on LimeLM dashboard !

For the rest, I don't care about reactivation if my customers downgrade, but loosing activations is a real problem for them. This is not acceptable at all.I sent you a separate email with a video to show you the behavior.

Thank you for explanation and fix. Philippe

Hey Philippe,

The reason this is happening is because on Mac and Linux we improved the "hardware fingerprint" algorithm. Let's say a user activates your app using TA 3.2.2 or below. Then they download and install the new version of your app using TA 3.3 or above. The user will still be activated and it will still use the same activation data (it won't replace the old activation data).

The next time you call Activate() or IsGenuine() then the new fingerprint an activation data will be use (meaning the user won't be able to rollback to the old version -- not without having to reactivate).

Will your customers be running an old version of your app side-by-side with the new version of your app?

Also, you shouldn't call IsGenuine() on every start. Call IsGenuineEx() and specify how many days you want between online verification. We recommend every 90 days, but even if you sett it to check every 1 day then that's better than calling IsGenuine() on every start.

Ok. Thank you for the explanations.