Launching a Server-initiated Hybrid App on the Device

When you click the Hybrid Apps menu item in the Hybrid Web Container, only the latest version of the Hybrid Apps appear. When you click the icon for a particular Hybrid App, the Hybrid App version that is associated with the notification is launched, whether it is the latest version or not.

Example

You develop a Hybrid App that has both client-initiated and server-initiated starting points. You deploy the initial version, which is called version 1, and a notification is sent.

Next, make some changes and deploy a second version, version 2. Again, a notification is sent.

There are now three ways that this Hybrid App can be launched, and the way that it is launched determines which version of the Hybrid App is launched:

• If you launch the application from the Hybrid Apps menu item, the last deployed version of the Hybrid App, in this case, version 2, is launched. Although version 1 of the Hybrid App still exists somewhere on the device, it is never used as long as you launch the Hybrid App from the Hybrid Apps menu.
• If you launch the Hybrid App by opening the initial notification, the version that corresponds with the latest version that existed at the time the notification was sent, is used. In this case, that is version 1; it does not matter that a later version (version 2) exists.
• If you launch the Hybrid App by opening the second notification, the version that corresponds with the latest version that existed at the time the notification was sent is used. In this case, that is version 2.