10-14-2009, 12:31 PM
Thumbs Must Hurt
Join Date: Oct 2005
Post Thanks: 0
Thanked 0 Times in 0 Posts
| | Upgrading an Application via BES Push
Please Login to Remove!
Hi there. I hope this is the correct forum for this question (I also posted in the BESAdmin corner).
We recently deployed an application for a client, using .cod/.alx files (via a BES push). The BES is version 4.1.6 for Domino.
We later had to upgrade the application, again, using .cod/.alx files. The file names were RENAMED for the upgrade, from helloWorld01.cod/hellowWorld01.alx to helloWorld02.cod/hellowWorld02.alx. The Internal project name remained the same. The BES did NOT recognize this as an "upgrade", and pushed out a second application.
I haven't seen any documentation from RIM which states that this isn't supported.
When I deploy the exact same application via a URL download (using .cod/.jad files), the application upgrades fine (even with renamed .cod/.jad files). The device does in fact recognize the application as an "upgrade" (same internal file name) and it works fine. I would have expected the BES to handle this the same way.
Thanks for any insight!