Release 3.0.2 Private Cloud

The following sections describe known issues and issues fixed in this release.

Platform Mobile Known Issues

PSC00260312 Cannot use CORS with HTTP Forms authentication in Firefox
It is not possible to use Firefox to run an OpenEdge Mobile Web App that uses a cross-domain request to log into a Mobile Web application that uses the HTTP Forms authentication model. If you do, the the login fails, throwing an NS_ERROR_FAILURE error object.

PSC00260382 Mobile Native Apps are not validating a Web site's credentials
"The process for connecting to a secured Web site using SSL/HTTPS involves verifying the Web site's server credentials against a local copy of the issuer's Certificate Authority (CA) certificate. This CA certificate verifies the authenticity of the Web site's identity. If for any reason, the Web site's server certificate fails the authentication, a warning is displayed notifying the user that the Web site's certificate is not trusted.

In Mobile Native Apps, the verification to ensure the Web site's authenticity is not occurring, with the result that the SSL/HTTPS connection is successfully established. Without this verification, a potential security problem exists where a connection can be inadvertently made to a fraudulent Web site."

PSC00258300 Some browsers display a prompt for credentials when Session.logout() is called
When a Mobile Web App calls the progress.data.Session logout() method and the security model in effect is HTTP Basic, some browsers display a dialog box that prompts for a user name and password. The only way to dismiss the dialog box is to cancel out of it -- even entering valid credentials does not cause it to go away. If the user does cancel out of the dialog box, the logout proceeds as expected. However, there should not be any dialog box displayed at all. Chrome and Opera are two browsers known to display this dialog box; Safari and Firefox do not.

PSC00253432 Mobile client can't use CORS if service uses Basic or Form authentication
OE Mobile supports two types of Mobile Apps: Mobile Web Apps and Native Apps (using Apache Cordova). Access to OpenEdge Mobile services from a Mobile App client is through the JSDO or REST web service

PSC00283298 JSDO doc unclear about when members return null
The documentation on JSDO methods and properties is not clear about when null or undefined is returned. In other words, in some cases, not yet identified, the documentation says that a given method or property returns null when, in fact, it returns undefined; or the opposite: that another method or property returns undefined when, in fact, it returns null.

PSC00311388 Old theme files need to be updated for library 3.0
The header of popups in Mobile projects updated to library version 3.0 may not show correctly. To fix this issue the theme used by the project needs to be updated to the latest version (1.4.x).

PSC00311035 Changes to popup implementation
The implementation of popups in the code generated by the Mobile App Builder has changed to use "popups" instead of "dialogs" in JQuery Mobile (dialogs are deprecated in JQuery Mobile 1.4.0 and will be removed in 1.5.0).
As a result of these changes, nested popups are not allowed. A second popup cannot be opened from a popup. Also, the page show event of a container may not fire when returning from the popup to the container. Applications using popups need to be tested thoroughly to ensure that the application logic executes as expected.

PSC00311705 Private Cloud Mobile Push Notifications URL
The documentation for the Platform Mobile Push Notification API lists http://api.mobile.rollbase.com as the base URL. Rollbase Private Cloud Users need to use https://api.appdesigner.app.infiniteblue.com instead.