Geek Answers Handbook

The latest change to this product was changed by a new version of Sencha Cmd - version mismatch

I am trying to add the sencha cmd package to my build process. But the last step, when I need to pack the application, fails with the above error.

I do not understand that this is a newly created application that came from the SVN repo. Sencha cmd is the last one since I just updated. So my question is when he claims that the application was last modified by a newer version of sencha cmd , is it harmful to me?

2 wrong things:

  • The application cannot be modified with a newer version, because I just upgraded the sencha cmd build version to the latest version version.
  • The application was created by Sencha cmd in the past, but it would be older than the current machine on the assembly.

So I remained puzzled how to solve this. How does Sencha Cmd “know” that the application was last modified by another version? Is there any file in the folder of my application that may be corrupted so that it considers the version to be the latest? And that Sencha Cmd is still related to my application code base?

+4
source share
4 answers

You can run the new version of Cmd in update mode. I think this is really intended to update the Sencha Touch version, but if you just point it to the current version (2.1), it will just update.

So, for example, run the line below with the last Cmd:

Update sencha application [directory where 2.1 is]

First, make sure you migrate a copy of your .js application, but as the new version handles this, just revert the old version after the upgrade. Also keep in mind that it will update your "Touch" directory, so make sure it is copied as well.

Once the update is started and you return the app.js file, your project should now build with the latest cmd.

+4
source

If you created / created your application using Sencha Cmd, you will have related information ( workspace.cmd.version , app.cmd.version ) in the following files:

 PROJECT_ROOT/touch/cmd/sencha.cfg // This is SDK requirements PROJECT_ROOT/.sencha/workspace/sencha.cfg // This is workspace build config PROJECT_ROOT/.sencha/app/sencha.cfg // This is app build config

You can try the fudging version of Cmd in these files and let us know if this works :)

+1
source

After updating the sencha --noframework application, be sure to run the "sencha app refresh" update to update the .sencha metadata.

+1
source

This misleading error message refers to changing the version of the Sencha Cmd tool on the computer you are using. You can upgrade the Cmd scaffolding with the following command:

 sencha app upgrade --noframework

From: 'sencha help app upgrade'

 Options * --noframework, -no - Upgrade only the Sencha Cmd scaffolding and not the SDK

Definitely back up your application before upgrading. The update team will warn you of conflicts that need to be resolved (for example, user changes in app.js). When you open these files, the differences will be noted in the standard diff format:

 <<<<<<< Generated /* This file is generated and updated by Sencha Cmd. You can edit this file as needed for your application, but these edits will have to be merged by Sencha Cmd when it performs code generation tasks such as generating new models, controllers or views and when running "sencha app upgrade". Ideally changes to this file would be limited and most work would be done in other places (such as Controllers). If Sencha Cmd cannot merge your changes and its generated code, it will produce a "merge conflict" that you will need to resolve manually. */ ... >>>>>>> Custom ...

Eliminate the conflicts (delete → → → the lines of X and make sure that the correct lines are included in your file), and you should be configured. The most likely file for conflict is app.js - it would be nice to compare your backup version of this file with your modified version to be sure of the changes.

This means that all developers working in the application must run the same version of Cmd, so keep that in mind.

0
source

More articles:


All Articles