Success! Looks like we've fixed this one. According to our records the fix was applied for
a recent build.
[2.1.0-b3] Ext.Loader path problem
after upgrading from beta2 to beta3 I have to set the SDK path (now in touch/src and not as beta2 in sdk/src) like this:
Why is that?
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:
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.
Originally Posted by rkraus
Thanks for the tip!
Trying to do the same now, but getting this: :-s
sencha-touch-2.1.0-beta3 $ sencha app create Project ~/Work/project
Sencha Cmd v18.104.22.168
[ERROR] UNHANDLED EXCEPTION : No such property : 'create'
They have changed the syntax! Try 'sencha generate app ...'
Oh ha awesome, thanks!
Originally Posted by ingo.hefti
(They don't seem to have updated the sencha command guide yet.)
$ sencha generate app APP_NAME APP_PATH
But you'll still have to update your app.js to contain the correct path to the sdk: