06-09-2010 11:10 AM
This issue is occurring only on BES 5.0. It doesn't happen on BES 4.1.
After my application is installed, it does some initial setup, deletes its CodeModuleGroup and creates a new CodeModuleGroup for itself with a different name. After waiting for a while, the BES pushes the app again. Is it possible that does this because it detects that the original CodeModuleGroup no longer exists? All the original code modules are still present.
Any help is appreciated.