I am also facing this issue.

Build prepared with Xcode 11 and running on iOS 13 simulator with usewkwebview=yes

Any progress on this issue?

This is not a fix but a workaround by playing with the options. I have it working with:

{
  usewkwebview: "yes",
  clearcache: "yes",
  location: "no",
  fullscreen: "yes",
  enableViewportScale: "yes",
  toolbar: "yes",
  hidenavigationbuttons: "yes",
  closebuttoncolor: "#8EA9F6",
  closebuttoncaption: "Close",
  presentationstyle: "fullscreen",
  transitionstyle: "crossdissolve",
  toolbartranslucent: "no",
  toolbarposition: "bottom"
}

The difference maker here is presentationstyle: "fullscreen", which actually prevents the swipe-down closing action. You can only close it using the Close button, which circumvents the bug.

I coupled it with transitionstyle: "crossdissolve" so that it doesn't look like it's sliding up when it opens (which might subliminally indicate to the user they can swipe down to close it).

Same issue here, swiping down to dismiss should atleast trigger an exit event.
More information can be found here: https://medium.com/@hacknicity/view-controller-presentation-changes-in-ios-13-ac8c901ebc4e

This is not a fix but a workaround by playing with the options. I have it working with:

{
  usewkwebview: "yes",
  clearcache: "yes",
  location: "no",
  fullscreen: "yes",
  enableViewportScale: "yes",
  toolbar: "yes",
  hidenavigationbuttons: "yes",
  closebuttoncolor: "#8EA9F6",
  closebuttoncaption: "Close",
  presentationstyle: "fullscreen",
  transitionstyle: "crossdissolve",
  toolbartranslucent: "no",
  toolbarposition: "bottom"
}

The difference maker here is presentationstyle: "fullscreen", which actually prevents the swipe-down closing action. You can only close it using the Close button, which circumvents the bug.

I coupled it with transitionstyle: "crossdissolve" so that it doesn't look like it's sliding up when it opens (which might subliminally indicate to the user they can swipe down to close it).

@timmliu thanks a lot. it worked for me. I have also opend an issue #612. closing it now.

tHANKS AGAIN

This is not a fix. This is just changing it back to how it was before. What if we want to use Pagesheet.
It most be possible to listen for swipe event and dismiss as if we clicked the close button?

Is there any update on this? It means that pagesheet should never be used. It should either be removed as an option or fixed.

Is there any update on this? I actually want to keep the in app browser running after swiping down and hiding it but that as mentioned freezes the app. Is there any work around to minimize the browser, have it running in the background and go back to the app?

Same issue here ...

Is this reproducible in a new, plain Cordova app? A minimal reproduction repository would really help to debug and later fix this issue. More information on how to create one: https://github.com/apache/cordova-contribute/blob/master/create-reproduction.md

I will post a sample app ASAP

@timbru31, here a repo to reproduce :
https://github.com/gnarco/inappbrowser-bug

on iOS, on app launch, it opens "in app browser" with a set predefined options.

• If I click on "close" button everything work perfectly (I can click on "click after" it opens a web page normally, just to simulate a user using an app)
• If I slide the inappbrowser bottom, the app "freeze". I can't click on "click after".

If I switch to : presentationstyle : fullscreen, it works. But in fact, it's just a workaround, because I can't slide to quit anymore :)

Thanks

I got a solution.

In my case, I was using the iab, to show a login portal, from an identity provider (SSO login), and when I got redirected with the user data, I'd navigate the user to the logged in home screen inside the ionic app.

The only modification I needed to do in my code, is to wrap the router.navitage method in a ngZone.run block.
So in my case it wasn't the plugin, it was angular that caused the behaviour.

this.ngZone.run(() => {
    browser.close();
    this.router.navigate(['/home'], { replaceUrl: true });
});

Any update on this issue ?

any update on this?

Hello, i confirm that the code works on iOS 17 ?

Any plan to commit this in main depot ?