Hello Wyatt,
This has happened on systems using Windows 7, 8.1 and 10 (although we have not really used Win 7 in a while) with all versions, Anniversary update, Creator update, Fall Creator update, etc. We only use x64 systems. We are current on TurboActivate (4.0.9.6?) but the issue has been happening for a while. We did update a bit ago to 4.0.9.6 hoping it might resolve the issue but it did not.
At this time, I cannot provide code sniplets. We are using Unity engine with C#. This has been happening occasionally for more than 2 years. We have not been able to find any steps to repro. We have many licenses and have not seen the issue very many times, maybe a couple dozen times. It has been to hard to try and find steps to reproduce. The only consistent thing we have seen is this has only happened to a license which has been edited after the license was created,using web interface.
This is why we were hoping if we provided the license files you might be able to tell us what has changed in the files and tell us under what conditions the activation information would be updated on a license previously activated.
Wyatt wrote:> More information is need to give useful help.> 1. What platform are you on: Window, macOS, Linux?> > 2. What version of the platform? (Windows 10, macOS 10.12, etc.)?> > 3. What architecture of the platform are you on? (x86, x64, armvt?)> > 4. What programming language are you using?> > 5. What version of TurboActivate are you using?> > 6. Can you give a way to reproduce this behavior? Code snippets? A> description, anything?> > > > > My guess is that you're using an old version of TurboActivate and/or you've> not updated your example code to match our latest examples (so, you're not> handling cases where the customer has blocked access to our activation> servers).