Verified Ted's commit as being valid. The push IDs are now not discarded immediately on page unload but after the expiry mechanism detects them as not being used.
Verified camera test in Bridgeit demo. The blocking connection now runs after the photo was loaded (and the page reloaded).

When I try to use any of the features in Bridgeit ICEmobile-SX will crash with a NullPointerException:

at org.icemobile.client.android.icemobilesx.ICEMobileSX.a(Unknown Source)
at org.icemobile.client.android.icemobilesx.ICEMobileSX.onNewIntent(Unknown Source)
.....

I'm using Nexus 7 with Android version 4.3.

To reproduce on Android, install ICEmobile-SX and load the BridgeIt demo

http://labs.icesoft.com/bridgeit

Invoke the camera and return to the page to observe that listen.icepush is stopped.

The push connection resumes on android with the above onBeforeUnload handler removed, so the question is what side effects there are under current PushID cleanup.

icepush.js (application.js) contains the following onBeforeUnload behaviour:

        onBeforeUnload(window, function() {
            delistPushIDsWithBrowser(pushIdentifiers);
            pushIdentifiers = [];
        });

On desktop browsers this is called when the user closes the window or navigates away from the page. On Android/Chrome, this is called when the browser goes into the background. Since the PushIDs are cleared, resuming the connection upon returning to the browser has no effect.

We now have a more accurate PushID cleanup mechanism, perhaps the above code can simply be removed.

Mircea, please look at whether pause/resume can be added to icepush as an automatic feature; if not, it might make more sense to use the events in bridgeit.js for this.

The BridgeIt demo currently contains:

window.addEventListener("pageShow", function ()

, false);

window.addEventListener("pagehide", function ()

, false);

This works on the iPhone, but the push connection is not being paused and resumed on android (likely because it does not support
pagehide and pageshow events). Further, Deryk's example does not contain the above code, so is likely working from the connection status detection (heartbeat not received).

One possibility is to resume the push connection in bridgeit.js since it can detect that the browser has been invoked.