Thank you for reporting this bug. We will make it our priority to review this report.
Ext JS Premium Member
Upgraded to build 309, rendered all of my previous projects unusable.
I upgraded to Sencha Designer 2 build 309 today, and now it seems I am unable to load any projects I had built in any previous versions of Ext Designer or Designer 2. Every time I try to load a project, I get the following prompt:
"The project was built with a previous version of Designer, and needs to be upgraded. Is it OK to upgrade?
I click Yes, I get a message that the conversion was successful (why do I even need to convert a project created in a previous build of Designer 2?). I can see my project on screen for a brief flash, but when the process finishes, the project is empty. No applications, controllers, views, models, or stores.
Worse yet, the process seems to be permanent, as re-opening the project does not give me the chance to roll back the conversion or perform it again.
Be warned! Build 309 rendered my project unusable. "Thank God for source control", as one other user put it. In the meantime, I need to keep working, what should I do?
If you must revert to an earlier build like 298, you can do the following.
Delete the 309 build .ion from the following location and then start the app.
C:\Documents and Settings\<username>\Local Settings\Application Data\Sencha, Inc\Sencha Designer 2.0\
C:\Users\<username>\AppData\Local\Sencha, Inc\Sencha Designer 2.0\
~/.local/share/data/Sencha, Inc./Sencha Designer 2.0/
Mac OS X
~/Library/Application Support/Sencha, Inc./Sencha Designer 2.0/
Could you please share the project with us that will no longer open? > 309 will have a few critical fixes that may address your issues.
Ext JS Premium Member
I may have been unclear. The project will open, but it's entire contents have been blown away during the "conversion" process. I'm attaching the project, but I think the damage has already been done.
Follow-up question: can I rebuild a project from the exported JS files? I have the most current version of those, and they are my only hope of getting a working project again.
Zip the entire directory up
And be sure to include any hidden files... The only thing that should have happened in the "upgrade process" was to rename the hidden directory from .metadata to a normal directory named metadata.
explore the project using cmd or terminal and see if a .metadata/ directory exists. If so then rename this directory to metadata/ (no dot) and reopen project