Avalanche: Why can't I import configuration spf file which exported from the same version of Avalanche?

Avalanche: Why can't I import configuration spf file which exported from the same version of Avalanche?

If you are seeing this error when importing an spf from a different release please see FAQ13780 In rare instances a project xml may overwrite the original xml version tag, this can occur for example if two different versions of Avalanche Commander are opened when creating a new project. To correct the spf version information for these specific cases: • Close Avalanche Commander • Go to project saving path (You can find the path by create a new project. Or by trying to modify an existing project path location by Right Clicking project on the left panel --> Change Path) • Go to project folder: ..\"project name"\tests   (Default Project location is: C:\Users\Windows_Username\AppData\Roaming\Avalanche ) • Edit testname.xml, the 3rd line, change version info to “22”, save file.(Notes: See FAQ10849 for Avalanche xml chart) • Reopen the Avalanche Commander GUI and export/import the configuration file again WARNING - Incorrectly editing project xml files or changing xml version tags to force importing to an earlier release may result in test corruption or unexpected behavior. Always back up your spf and project directory prior to making any changes.  Scenario using MULTIPLE VERSIONS OF Avalanche Commander: In some scenarios when using MULTIPLE VERSIONS of Avalanche Commander, You might need to export a project from older version to a more recent one or viceversa, For this you should be aware of closing the Avalanche Commander properly (plus killing all java.exe or javaw.exe processes BEFORE OPENING ANOTHER VERSION of Avalanche Commander). Or you might experience some weird behaviors as some variables stay on memory and this can affect paths, versioning, project saving locations or UI rendering issues between versions.  For example you are working on AVC v4.91, but then close AVC v4.91 and NOT KILL THE JAVA RTE (java.exe or javaw.exe), then open AVC v4.88, once in version v4.88 you try to export any project and save it to local computer, then this project saved into apparent v4.88; After this you decide to move/save this same SPF project into a different computer and tried to be imported into same version AVC v4.88 but you get this error message, when you go to project folder (Default is: C:\Users\Windows_Username\AppData\Roaming\Avalanche) and search for project folder, then subfolder tests and open the project/test xml file you will find that version does not match, this was because some variables remained in memory and when saved the project those variables were used to create the SPF Project. To validate the correct version (newest one) your test needs to reach, you can make sure to close all avalanche commander windows, kill Java RTE processes and then open the destination version. Then from this version, create a new project from scratch and go to the same folder where this project was saved and verify the test / project xml file to find the destination version number. Now with this information you will know which should be the destination version that your imported test should reach once imported properly.