Best practices for 2.1.x to 2.2 beta migration

[afromogli]

Hi folks!

I have a question regarding migration from one minor release to another. Currently I have an Sencha Touch app which is setup using Sencha Touch 2.1. However I want to use the 2.2 beta since Windows Phone 8 support is desired.

How do I perform the migration in the best way? Is there any Sencha CMD command I can run to upgrade or should I just manually copy the files? If I have to copy manually, which files must be upgraded?

Thanks,
Aram

[mitchellsimoens]

Should be able to do:

sencha app upgrade /path/to/touch-2.2.0

[afromogli]

Should be able to do:

sencha app upgrade /path/to/touch-2.2.0

Tried it, it worked! Thanks

[gkatz]

does sencha app upgrade does goes over the app code and changes stuff? for example changes to custom components? or does it just change the library along with some other 'references'.
can you please elaborate? (the docs does not explain this)
thanks.

[mitchellsimoens]

It won't go over all your code, it will do things like update the .sencha and touch directories. It'll also go over the index.html and app.js files and if they are changed then it will try to merge the files which can look bad when merged (we have a feature request to handle it better).

[ingo.hefti]

from my experiences an upgrade will/may change/replace:

• index.html
• app.js
• app.scss
• packager.json
• resources/icons
• resources/loading
• resources/startup

replacing the resources is an older problem.

so make sure you have a backup of your stuff before you upgrade...

[P.verbrugge]

I tried to upgrade using the given command, but it fails on CMD v.3.1.1.274.

I have a Sencha Touch 2.1 app that I want to upgrade to 2.2. However, when I execute the command i get the following:
- [INF] Loading configuration for framework directory ...
- [ERR] null

Path to my touch 2.2 folder is correct.

[ingo.hefti]

I wouldn't invest too much time into this. Upgrading a ST app is a continuous source of trouble. What I usually try to do is the following:

• rename your project (f.e. from MyProject to MyProjectSave)
• use CMD to create a new project, name = MyProject
• copy all your stuff from save into the new project like app folder (remove it first), app.js, resources and css (if applicable), etc.
• then try to run the app and adjust what's still missing.

Note, that app.js has a slightly different structure (header) now. So it's better to copy YOUR part from the saved app.js into the new one.

[P.verbrugge]

Thanks for the tip. I will look into that. Somehow the upgrade never seems to work normally. :-(

[ingo.hefti]

... Somehow the upgrade never seems to work normally. :-(

my thoughts!