[CB-680] onNativeReady fires before the server is taking new connections

• Type: Sub-task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.7.0
• Fix Version/s: 1.8.0
• Component/s: cordova-android
• Assignee: Joey Robert Bowser
• Reporter: Joey Robert Bowser
• Created: 09/May/12 23:36
• Updated: 23/Aug/18 07:46
• Resolved: 10/May/12 22:13

Description

This issue is able to be ignored in Android 1.7, but it has come to a head in Android 1.8, since we moved where the Callback Server lives.
D/CordovaLog( 3395): file:///android_asset/www/cordova-1.7.0.js: Line 3570 : JSCallback Error: Request failed.

When this occurs, and you have methods that are called onDeviceReady, while the interfaces exist, there's no way to get the callback, which means that it hangs forever and always fails when using the CordovaWebView branch. This indicates that we are calling onNativeReady prematurely when we go from page to page, and that we have to wait for the server to be ready before calling this.

Issue Links

• relates to: CB-686 window.resolveLocalFileSystemURI doesn't always execute callbacks