Activation Data Storage Locations

Hey Mike,

You're building functionality based on internal layout that has changed in the past (for technical reasons) and may change in the future (again, for technical reasons). There's no guarantee that that folder will be used in the future.

And not only are you "blowing away the local activation data" for your own application, but you're "blowing away" the activation data for any other product that uses TurboActivate.

So... don't do that. You'll infuriate your customers who will wonder why a handful of their apps stop working for no reason.

Can I ask why you don't just use the Deactivate() or the DeactivationRequestToFile() functions? Those functions accomplish what you're trying to do.

This blowing away of all of the User's application is precisely what I am hoping for.

We have a deployed MAC application that has a modal user registration window for entering in a new license.

We also seem to have a bug where our registration window is in a strange and non-reproducible state in which we think that there is a valid registered key (also verified on the LimeLM server) yet not fully (this is the bug).

There is a customer of ours who has paid money and trying to register their product... and can't. A far more severe situation than you described.

We are simply trying to get the customer out the deadlock state that our application has managed to get him into.

I have no desire to use this in any sort of "normal" way. In fact, we do use the Deactivate() function when our application is actually registered and thinks that there is a valid license.. Our problem is that the App never, ever gets registered and when the registration window is exited, the app closes... Deadlock.

Again, we can not reproduce this problem and really have no idea why it is happening at this point. We just need to get our customer going.

Please help me blow away anything on his local MAC that is any vestige of TurboActivate. I'm sure that there are plenty of ways to do this programmatically (i.e. with a special utility/app that we could cook in the next day or two) but this is will serve only to make a bad situation worse...

HELP!!!

It depends on whether you're using TA_SYSTEM or TA_USER, because the activation data is stored in the "application support" folder for either the user (for TA_USER) or the system (for TA_SYSTEM):

TA_SYSTEM: /Library/Application SupportTA_USER: /Users/<user>/Library/Application Support

The product key data is stored in [application support]/.AppleThe activation data is stored in [application support]/.System

(notice that both are "hidden directories" because they start with a ".".

If you can reproduce this behavior or if it happens again, please let us know. We want to know about any bugs you or your customers find so that we can fix them for you and our other customers.

Also note this is behavior for TurboActivate 3.4.x -- it was different in previous version, and it may be different in future versions.

Thank you, I will let you know if anything interesting turns up.