cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CB-11136) InAppBrowser fails to close with WKWebView OAuth
Date Thu, 30 Jun 2016 21:51:10 GMT


ASF GitHub Bot commented on CB-11136:

Github user alesveselka commented on the issue:
    Hi, sorry for confusion.
    There is already an open PR solving exactly same thing as this PR (
    I understood from discussion below that its not really good systematic solution, but at
this time it's only solution that solves the problem and so I need the PR merged in order
to used this plugin.
    So I fork the repo and merged same PR and mistakenly had set origin to this original repository.
    If you want to merge this contribution, please merge @ephemer 's solution (,
or maybe someone else comes with alternative one in the meantime ... 

> InAppBrowser fails to close with WKWebView OAuth 
> -------------------------------------------------
>                 Key: CB-11136
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin InAppBrowser, Plugin WKWebViewEngine
>    Affects Versions: 4.1.0
>         Environment: iOS 8+ with WKWebView
>            Reporter: Geordie Jay
>            Assignee: Shazron Abdullah
>   Original Estimate: 3h
>  Remaining Estimate: 3h
> Launching InAppBrowser from Cordova iOS Platform 4+ with its WKWebView for OAuth (e.g.
Facebook or Google login) fails to close as it should.
> The reason is that the entire WKWebView thread seems to pause when another view controller
is presented. This can be confirmed by inspecting the WKWebView session in Safari, running
`'')` and then trying to enter another command into that Safari
> I made a hacky but working version of this that animated in the InAppBrowser's view manually,
rather than 'presenting' the ViewController in the traditional iOS style. In that instance
the WKWebView thread continues as normal and receives the confirmation to close the other
InAppBrowser when the OAuth process is complete.
> Maybe there is a better way around this, but at the moment this is a big usability fail
for all WKWebView users.
> What do you all think, is the 'not-actually-presenting' way of presenting the InAppBrowser
acceptable? Would be happy to make a pull request along these lines if it is.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message