The problem ocures when you have a component with a store (for example dataview) , promoted to class. You have probably set the store in the class and the initiated object set empty.
With 1.1.2 the instance extended the promoted class, so the store was set. But with 1.2.2 the instance doesn't "extend" the class, so the instance has a property "store" set empty , resulting a error a component is missing a store.
The "fix" is setting the store in the instance. So now I managed to export the project.
2) Store undefined after export
So I "fixed" issue 1. But now, when I start my application. I get errors like "store undefined". When I console.log the component and retrieve the store property, the property was emtpy.
But I also "fixed" that by rebinding the store to the component with the .bindStore() function.
3) Combobox not working
So now I have a combobox. I also get the same store issue so I "fixed" it by rebinding the store to the combobox. That worked. BUT .. When I set the value , the combobox doesn't show the displayField , but just the value I just set.
Fox example I have
display = "my test"
value = "yes"
I set the combobox value to "yes" , it should display "my test" in the combobox , but it shows "yes". When I trigger the combobox by clicking the comboxbox, it makes the request to the server , get the json response and updates the combobox and then it shows the displayField.
I tried to load the store before the component is rendered, but no luck
4) No Ext.reg
2) If you can provide a sample application we could look into this further
3) You are correct in assuming that the store needs to be loaded before the value is set. This will fix this problem.
4) Is the userXType set?
5) We have a bug filed for this DSGNR-1284. This occurs when double clicking on a project that is an unsupported framework type. If you start Designer 2.0 and click on a framework (Ext 4.x or Touch 2.x) and then try to open the project you will see a message along the lines of "This project is targeting an unsupported framework (ext3.x)"
Sencha Architect Development Team
I'm also affected by this bug, I need to manually add all of the Ext.reg() lines now for everystore I have defined. This has happened since moving to 1.2.2 on OSX and upgrading the project, so I can't go back now.
Eventually I want to be using ExtJS 4.x but i'm deliverying a 6+ month project and need to get my first release out on 3.3.x first, otherwise I'll never deliver.