Backwards Compatibility between Cycle 2.21 and Previous Versions

This article is in reference to Bug 9924: Null values in the default path settings cause incompatibility with opening projects between versions. 

Cycle 2.21 introduced some new default setting values for the cycle2settings.json file that are incompatible between versions. This causes difficulties with users downgrading from Cycle 2.21 to an earlier version if the need arises. Users will find that when installing an earlier version (for example, Cycle 2.19), they will not be able to open or create a new project. 

When a user encounters this issue it is because there are some values in their cycle2settings.json file that are incompatible between versions. In particular, this would be any setting where the default value is displayed as “null”: 

•  "CustomChromeBrowserLocation" : null

•  "IEDriverLocation" : null

•  "EdgeDriverLocation" : null

•  "ChromeDriverLocation" : null

Note that if a user is a brand new user who started working with Cycle in Cycle 2.21 or later they are more likely to encounter this scenario. A user who was on a previous version of Cycle prior to Cycle 2.21 would have inherited their old cycle2settings.json file from previous versions, which would avoid this issue. 

To fix this: 

1. Close Cycle 

2. Navigate to C:\Users\<MyUser>\AppData\Roaming\Cycle\config

3. Delete the cycle2settings.json file 

4. Reopen Cycle