I noticed the touch folder in the "myapp" example in the sdk.
So I'm not sure now what to do for a manual upgrade since the automatic upgrade didn't work for me.
Did you do anything fancy for the upgrade?
I installed the sencha cmd 3.0, went to the sdk folder and ran sencha app upgrade ~/myproject and got an error: http://www.sencha.com/forum/showthre...b2-gt-2.1.0-b3
I did a complete new project with the new "Sencha CMD" and then copied the files (like the touch folder) into my "old" project. Everything fine so far expect I ran into this Ext.Loader problem and my "Production" Build got an ugly error when I try to start it.
So I'm not the only one having problems to upgrade...?
As b3 contains a few things that are important to me, I decided to upgrade 'manually'. I renamed my project folder and created a new project with the 'old' name (that works with the new sencha cmd). Then I copied all my files from the renamed project to the new project. After adding the missing Ext.Loader path I was able to run and then to compile the thing into a native android app.
From what I understand you have done it the other way round. When I noticed that names and folders have changed I decided to copy my OLD stuff (mainly the APP folder) into the new project. This way the new project structure should remain intact.