[InAppBrowserEvents] Change in Apache Cordova repository causes UI to be unresponsive on iOS

[InAppBrowserEvents] Change in Apache Cordova repository causes UI to be unresponsive on iOS

  
Forge Component
(0)
Published on 2017-03-10 by Rui Barbosa
0 votes
Published on 2017-03-10 by Rui Barbosa

Hi,

Just letting you know that current (23.8.2018) version of Apache's InAppBrowser (https://github.com/apache/cordova-plugin-inappbrowser) is breaking the experience on iOS 10 & 11.

After inAppBrowser is closed, Outsystems UI does not respond to any user input. App is working, as it can interact with push notification deep links, but UI is completely dead even after sending app to background or waiting extensive periods of time.

This was unacceptable as we are doing login through this component, so as a solution I changed the extensibility configuration to point to supported Outsystems version of this plugin: https://github.com/OutSystems/cordova-plugin-inappbrowser.git#1.7.0-os

Another workaround is to create a fork from Apache repo, I tried with a fork from commit at August 1, 2018, which also worked just fine.

br,

-Mikko(N)

Mikko Nieminen wrote:

Hi,

Just letting you know that current (23.8.2018) version of Apache's InAppBrowser (https://github.com/apache/cordova-plugin-inappbrowser) is breaking the experience on iOS 10 & 11.

After inAppBrowser is closed, Outsystems UI does not respond to any user input. App is working, as it can interact with push notification deep links, but UI is completely dead even after sending app to background or waiting extensive periods of time.

This was unacceptable as we are doing login through this component, so as a solution I changed the extensibility configuration to point to supported Outsystems version of this plugin: https://github.com/OutSystems/cordova-plugin-inappbrowser.git#1.7.0-os

Another workaround is to create a fork from Apache repo, I tried with a fork from commit at August 1, 2018, which also worked just fine.

br,

-Mikko(N)

Thank yo Mikko for this workaround.

I was having the same issue with iOS but now as per your suggestion, it is working smooth.


Cheers,

Debasis Sahoo