The problem is we have customers that have source control create copies of metadata that sends Architect into a fit creating duplicate components. So to counteract this I created a check when you load a meta file to be sure the userClassName inside the meta matches the file name it was read in from. The issue you guys are having is because the case is incorrect.
The Work around:
Rename the files w/ the proper case on disk prior to opening your project.
I'm going to have to change the file casing on write when users alter their userClassName by just case or simply be case insensitive with the meta validation. A bit more investigation is necessary.
thanks! This is crazy, but I can't seem to install it though...
I uninstalled what I had, I even deleted the sencha architect folder in c / program files x86 (I'm using win7), after installing these versions and opening it, it says its version 2.2.2. It's strange but under control panel it's version is 2.2.1...but the point is that when I want to open my project (2.2.1) it wants to upgrade it..
Just curious about what files you are reading from to compare to the metadata file. The reason I ask is that we use Architect exclusively to create the UI and never touch the generated JS files outside of Architect so I am not sure how the casing for the files got changed or are different from what is in the Architect project.
Just look to see if I need to fix something on my end of this.
Any chance of knowing when the service release will be available. Being that we are on an older version now we are notified when starting Architect that there is a new version every day. So it will be difficult to know when the version of the fixed is actually released.