Migrate Hybrid Apps

Migration changes may be required to take advantage of new Hybrid App features.

Migrate Hybrid Apps from 2.1 ESD #3 to 2.2

A Hybrid App developed in an earlier release (such as 2.0, 2.1, 2.1 ESD #2, and 2.1 ESD #3) should be compatible in a 2.2 Hybrid Web Container unless it uses PhoneGap 1.4.1 functionality (PhoneGap broke backward compatibility with its release of the new and renamed Cordova 2.0 library).

To use new 2.2 Hybrid Web Container functionality, manually reconstruct the Hybrid App to use the new JavaScript API files shipped in the folder: SUP_HOME \MobileSDK22\HybridApp\API\Container.

The Designer in Sybase Unwired Platform 2.2 SP02 generates code using the new JavaScript API. Earlier versions did not use the new JavaScript API to generate code, and generated 2.1 ESD #3 compatible Hybrid Apps instead.

Additional notes for in-place upgrades:
  • The 2.2 Android Hybrid Web Container is an in-place upgrade from 2.1 ESD #3, if you built it from a template source keeping the same “Application id.” In other words, Hybrid Apps that are already deployed remain intact on the device after the upgrade, and the old binaries are replaced with the 2.2 Android Hybrid Web Container binaries. See the Android matrix in Hybrid Web Container Migration Paths for Android.

  • The 2.2 BlackBerry Hybrid Web Container is not upgraded but coexists with other versions. See the BlackBerry matrix in Hybrid Web Container Migration Paths for BlackBerry.
  • The 2.2 iOS Hybrid Web Container is an in-place upgrade from any earlier version, if you built it from template source keeping the same “bundle id.”. In other words, Hybrid Apps that are already deployed remain intact on the device after the upgrade, and the old binaries are replaced with the 2.2 iOS Hybrid Web Container binaries. See the iOS matrix in Hybrid Web Container Migration Paths for iOS (the Applications Build from Source Code section).
  • The 2.1 ESD #3 to 2.2 iOS Hybrid Web Container from the Apple App Store is an in-place upgrade. See the iOS matrix in Hybrid Web Container Migration Paths for iOS (Applications Downloaded from Apple's App Store).
  • The 2.2 Windows Mobile Hybrid Web Container coexists. See the Windows Mobile matrix in Hybrid Web Container Migration Paths for Windows Mobile.

HttpAuthDCNServlet no longer uses the "admin" security profile to authenticate users when an application user name does not include a security configuration name. Instead, if the user name includes a security configuration, HttpAuthDCNServlet uses it. For Workflow DCN, where the user name may not include a security profile, HttpAuthDCNServlet uses the value of the requested "security parameter" to authenticate the user. This should not affect your Hybrid Apps, but is useful to know if you are developing Hybrid Apps that take advantage of DCN updates.

Related reference
Hybrid Web Container Migration Paths for Android
Hybrid Web Container Migration Paths for BlackBerry
Hybrid Web Container Migration Paths for iOS
Hybrid Web Container Migration Paths for Windows Mobile