incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shazron Abdullah (JIRA)" <>
Subject [jira] [Commented] (CB-1066) window.invokeString is not set on resume
Date Mon, 16 Jul 2012 21:06:34 GMT


Shazron Abdullah commented on CB-1066:

I cannot repro what your findings that "handleOpenURL is not called on resume".
My tests show that it is indeed called on resume when invoked by a url (you can verify by
creating a new project and testing this, to eliminate side-effects)

In any case, the original bug was window.invokeString is not set on resume - which is by design.

> window.invokeString is not set on resume
> ----------------------------------------
>                 Key: CB-1066
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 1.9.0
>         Environment: iOS 4.1
>            Reporter: Rohde Fischer
>             Fix For: 2.0.0
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> When I switch to another application (such as Safari) and follow a link that leads to
my application such as: myapp://some/path the window.invokeString is not set to "myapp://some/path"
as I expect.
> To reproduce, create an custom url schema for the app add this to the app:
> document.addEventListener("resume", function() {
>   console.log("Invoke: " + window.invokeString);
> }, false);
> Exit the app and follow a link that leads to the app.
> I suspect that the bug should be fixed by adding something like this to the resume:
> if (self.invokeString)
>      {
>         // this is passed before the deviceready event is fired, so you can access it
in js when you receive deviceready
>         NSString* jsString = [NSString stringWithFormat:@"var invokeString = \"%@\";",
>         [theWebView stringByEvaluatingJavaScriptFromString:jsString];
>      }
> The code is taken from MainViewController.m

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message