Corrupted Project and Keyword Test variables

Same as this post, https://community.smartbear.com/t5/TestComplete-Questions/TestComplete-v15-56-software-saving-string-variables-with-Base64/m-p/259130

PMularczyk just looping you in on this issue.

We have opened ticket 00574549 for this.  We're worried other projects will be impacted.

The quality of TC releases has become poorer over the last 2-3 years and we want to have a conversation with our account manager to get some feedback from the Product Manager.  We dont want to make further investments if this is now the norm.  Its dissapointing to see, as I've used it for 12 years and its never been as bad as this.  I'd stake my reputation on TC but not now. 

let me know if you find a stable alternative.  I'm having the same issue and the lack of Firefox support (it's four versions behind) makes some of my projects useless. 

Hello!  This has been happening to our team and I've spent many hours trouble-shooting.

**It's actually  running keyword tests  in the bad version that seems to munge var values**

Installing TestComplete 15.57.2.7 appears to fix the bug.

It will NOT, unfortunately, fix your values.
Our solution was to

1.  Install version 15.57.2.7 and 
     *  Open the last good version of the project file in Notepad++ and copy/paste the good values back into your project, OR

     *  If you are using GitHub Desktop (or any git), you can discard the evil changes made to the project files.

So far, tests are running fine in 15.57.2.7 and var values are intact.

Currently i am unable to download 15.56 exe also it is throwing xml error while downloading, rather i can download 15,55 and 15.57, 

tried in 15.55 without corrupted framework still getting error.

anyone have having 15.56exe pls share 

Cross post from the other thread on this issue;

https://community.smartbear.com/t5/TestComplete-Questions/TestComplete-v15-56-software-saving-string-variables-with-Base64/m-p/259472/highlight/true#M112787

TLDR - "On another note some initial testing of v15.57 on my side, it seems the Base64 encoding issue might be gone, or at least I couldn't recreate it like before, but this was only a quick test I had.

We'll still be treading a bit carefully with the new version, with most testers sticking on v15.55 for now."

I sadly agree with you that it has become very buggy...

i am also getting same issue variables got corrupted and tried to downgrade version still getting the same error.. Any workarounds pls

Variables and their values are saved in either .pjs or .mds file, which is most likely corrupted. If you install a previous version, you are still loading the same .pjs or .mds file with the corrupted values.