Sencha Architect won't open the project I have successfully working on yesterday. Until I closed SA everything was fine - no errors neither in SA nor in deployed JS generated. Then when I reopened the project next day, SA started to crash with an "unknown error":

Removing Sencha folder under my AppData\Local and reinstallation of SA don't help. Other projects (including earlier versions of that one) open fine. New projects can be also created and saved, only happens with particular project.

I'd say project source is corrupted (also I see no obvious errors in its JSONs myself), but no project files have been modified outside of SA, the development has been done entirely in SA. If they were corrupted, that was probably done by SA itself.

OS version: Windows 7 64bit
Sencha Architect version: 2.1.0.000640.

The problematic project archive is attached. 2012-10-16.xda (the problem is the same for the archive and for the imported project).

Noticed a couple of irregularities in project files, e.g. xds profject file and Application and Explorer metadata files were listing 'Folder' model which was actually renamed to TreeNode (for some reason renaming has been reflected while code worked fine in browser before I closed SA).

One of my stores I have converted from XML store into JSON store was still had {"type": "xmlstore"} in its metadata file while other properties were changed to JSON store one. So store type and properties didn't tally and project was crashing when opened.

There were other issues I've found with renamed entities, but only that one was fatal.

It looks like a HUGE problem to me Edits seem to be fine while the project is in memory and your application works properly, then you save the project and not all the edits you've done are actually stored.

I'm only starting with the product so my code is probably not following best practices. Empty store is there to access it later in runtime and populate it dynamically. It'd be better probably to create the store dynamically as well for that purpose, but that's easier for me at the moment.

I still consider that a bug because I believe it shouldn't be possible to make fatal changes to the project using the system itself and even not writing any code.

Also while looking through project source JSONs I discovered many other cases when renamed / transformed entities retained part of their properties from the previous version and part from the proper one (some of them I have posted above).

Sorry for my tone in the messages above, but that looked extremely strange to me. Is there an explanation by any chance or that is a system issue?