iOS: scrollbar shows after use plugin

[rricamar]

Bug Report

Problem

Hi,

I recently update the plugin's version to v4.0.0 to try #623, that is closed.

But, I'm observing that after the InApp's instance appear, the "default" scrollbar starts to show (I left a .zip with two videos, one with the v3.2.0, and another one with the v4.0.0) on iOS 13.5.

Could be the plugin be interfering with the Ionic's Webview plugin or with the platform detection?

Thank you in advance; let me know if I could help with something.

Zip with the videos: scrollbar-issue.zip

Version information

Ionic:

   Ionic CLI                     : 5.4.13
   Ionic Framework               : @ionic/angular 5.1.1
   @angular-devkit/build-angular : 0.901.7
   @angular-devkit/schematics    : 9.1.7
   @angular/cli                  : 9.1.7
   @ionic/angular-toolkit        : 2.2.0

Cordova:

   Cordova CLI       : 9.0.0 (cordova-lib@9.0.1)
   Cordova Platforms : ios 5.1.1
   Cordova Plugins   : cordova-plugin-ionic-keyboard 2.2.0, cordova-plugin-ionic-webview 5.0.0, (and 24 other plugins)

Utility:

   cordova-res (update available: 0.15.0) : 0.14.0
   native-run                             : 1.0.0

System:

   ios-deploy : 1.10.0
   ios-sim    : 8.0.2
   NodeJS     : v12.16.1 (/Users/rricamar/.nvm/versions/node/v12.16.1/bin/node)
   npm        : 6.14.4
   OS         : macOS Catalina
   Xcode      : Xcode 11.5 Build version 11E608c

Checklist

• I searched for existing GitHub issues
• I updated all Cordova tooling to most recent version
• I included all the necessary information above

[giorgos120]

Hi, @rricamar, did you manage to find a solution/workaround to this issue?
I can confirm that it is still present....

[rricamar]

Hi @giorgos120, I left the project in which I was working a few months after opening the issue, so I don't know if this is solved in the latest versions ... did you try it? Just saw that they released v5.0.0

The only workaround that I found on that days was to keep using v3.2.0 😓 , which I guess that nowadays is really obsolete 😭

[giorgos120]

Sad to hear that.
It is bad that there is no workaround since it is an actually important feature for some app implementations.

indeed v3.2.0 is old enough. The problem still exists though