09-13-2008 02:07 PM
Stange situation. Could you please give me a hint, how can I overcome that ?
Solved! Go to Solution.
09-13-2008 03:18 PM - edited 09-13-2008 03:19 PM
Did you change the app's version? That's what triggers the loader to update.
Once you "add" the app, the loader will automatically check for new versions.
09-14-2008 02:51 AM
Yes I changed the application version number in JDE project properties window.
New version is greater (1.01) than version of existing app (1.0)
09-14-2008 12:51 PM - edited 09-14-2008 02:51 PM
Here is my take on what is happening here.
You have added an alx, to the App Loader, so it knows which cods you are trying to load to the device. If you add another alx, with the same cods, it rejects this, telling you 'no additional applications'. In this case, it should probably say 'application cods already added'.
Now the App Loader is sometimes its own worst enemy, but it tries to be clever and it will remember, for each alx you have added, the level of the alx. So if you go in and change that alx to a later level, the app loader will tell you, that you need to update. If you change it to an earlier level (i.e. lower) it will tell you that you are downgrading, and then will ignore the downgrade (which can be a might annoying...). When doing this, in my experience, it takes no notice of the compilation date of the cod file - this is only done on the level details in the alx.
So in your case, you should just update the alx that the App Loader is pointing to each time you upgrade (and sign) the cods involved..
09-14-2008 01:31 PM
alx file is also updated. Both files: cod and alx are updated.
alx file contains bigger version number: 1.01
existing application version is 1.0
could you please explain - what else shall I update in this case?
09-14-2008 02:26 PM
The source of the problem is in version number format.
If I want to use 1.01 version, the previous number has to be 1.00
In this case new version recognized properly.
Thank you. The issue is now solved.