18 Apr 2013 3:04 PM #1
Unanswered: CMD 184.108.40.2064 upgrade doesn't work
I used the current version of CMD to create a starter app based on the 2.1 sencha touch framework. I pointed a web browser to the folder and the sample app came up and worked fine.
Then I used CMD to upgrade the sample app to 2.2. There were no conflicts in the output. When I looked at the site in a browser the header didn't have the proper color or height. It was chewed in the conversion.
When I run CMD it doesn't display a notice saying there's an upgrade so I should be on the current version.
I just stared using sencha and from the little bit of research I've done it sounds like it's better to generate a new app based on an updated framework and copy your files to that folder than try to run upgrade on the current app.
Has anyone else had this issue?
22 Apr 2013 4:57 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
I personally don't have issues with upgrading, my app.js usually has a conflict as I have to change it as the apps continue to evolve.Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services firstname.lastname@example.org
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.