Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Testing and Deployment

A module with that name already exists in the application

by Retired ‎02-16-2010 10:56 AM - edited ‎02-19-2010 08:38 AM (4,108 Views)

Summary


This article applies to the following:

  • BlackBerry® Device Software versions prior to 4.2.158
  • BlackBerry Device Software versions 4.2.1.67, 4.2.1.68, and 4.2.1.72
  • SDR104306


Problem


If you attempt to install an application that shares common modules with an existing application on the BlackBerry smartphone, the following prompt appears:

"<Application2>" contains a module called "<module_name>". A module with that name already exists in the "<Application1>" application. If you proceed, "<Application1>" will be replaced by "<Application2>". Proceed?

The prompt indicates that the operating system detected a relationship between the two applications based on the common module. This capability was added in case the version of the module in <Application2> differs from the version of the module in <Application1>. This can cause instability on the BlackBerry smartphone, with <Application1> being unable to function correctly.


When using the versions of BlackBerry Device Software specified in the Summary section above, the BlackBerry smartphone user is prompted for confirmation even if the module versions are identical. In later versions of BlackBerry Device Software, the prompt only appears when the versions of the common module are different.


Resolution 1


Proceed with the installation of <Application2> if the versions of the common module are identical.

If the versions of the common module are not identical, the prompt is valid and you must decide whether or not to install the application.


Resolution 2


Install the common module in its own deployment, ensuring that only one copy of the module exists on the BlackBerry smartphone; note that if you do this, the higher-level application might not detect that the common module has already been installed.


Note: You should include dependency checking in the JAD file. This verifies, when an application is being installed, whether a common module has already been installed or has to be installed during this process.


Resolution 3


Use different names for the common module in <Application1> and <Application2>; note that if you do this, a module is effectively duplicated on the BlackBerry smartphone, which unnecessarily uses space.

Contributors
Users Online
Currently online: 33 members 1,949 guests
Please welcome our newest community members: