'loadstop' event stopped working in iOS 12.0 about cordova-plugin-inappbrowser

[gurolayanlar]

Hi,
I found a solution by myself. Remove "loadStop" event from my codes for solution.
Added this code:
$scope.ref = cordova.InAppBrowser.open(my_url, '_blank', 'clearcache=yes,location=yes,toolbar=no'); var loop = setInterval(function() { $scope.ref.executeScript({ code: "document.getElementById('my_special_markdown').innerText" }, function(values) { var myValue = values[0]; if (myValue) { clearInterval(loop); $scope.ref.close(); $scope.myFunction(myValue); } }); }, 300);

[SoumyaAM]

InAppBrowser LoadStop event is not triggering in iOS 12 version. Tried different workarounds, but nothing. Loadstop event is not fired, thus the user not able to proceed the application.
Currently using cordova-plugin-inappbrowser 3.0.0.

[Able1991]

InAppBrowser LoadStop event is not triggering in iOS 12 version. Tried different workarounds, but nothing. Loadstop event is not fired, thus the user not able to proceed the application.
Currently using cordova-plugin-inappbrowser 3.0.0.

use executeScript and setInteraval as advised by gurolayanlar, so you can get a location.href and any necessary data

[scotthmusson]

Any update on this? Still see this issue in 3.1.0. I'm able to get the work-around to work, but it's a real hack.

[Able1991]

The problem is urgent! Now I can not track the success of the payments and close the window as needed
cordova-plugin-inappbrowser 3.0.0, ios 12

[realweb]

Hi,

I noticed from iOS 12+ event LoadStop is almost never fired. I mean "almost" cause sometimes the event is fired, and most of times not.

I applied a "hack" (targeted for ios 12 version) to solve the problem adding a timeout on LoadStart event and if after some time the LoadStop event is not fired I excute desired action. Works, but it´s a dirty hack and I don´t plan to keep this hack for too much time.

Does anyone know a oficial fix for this bug?

regards

[hvaughan3]

Seems to be working fine for me.

[abuturla]

I have noticed that sometimes the loadStop and loadStart events are not firing, although it doesn't appear to be deterministic.

[alexyazvinsky]

I have totally the same issue.

[csleeds]

possible due to content security policy setting?
Try add gap://* at the meta tag for content-security-policy
solution referring from: https://stackoverflow.com/questions/30918553/cordova-deviceready-not-firing-in-ios-until-interacting-with-ios/30918554

[gurolayanlar]

I have same problem, is there solved problem?

[skrpc]

I have the same problem, have tried both with a Content-Security-Policy meta tag with numerous settings and without one altogether. Have tried settings on config.xml and no luck.

Just does not seem to trigger any inAppBrowser event when using iOS 12, I have no problems with iOS 11.

Looking at CDVInAppBrowser.m the webViewDidFinishLoad() and didFailLoadWithError() are not called (breakpoints not hit).

loadstart is called as shouldStartLoadWithRequest() is called in CDVInaAppBrowser.m

[Genarito]

Same problem, in my case any of the events are firing on iOS (11.4), in Android there is not such problem

[JakariaAmin]

Same problem i am facing too, exit method works but loadstop works sometime, some other time it doesn't.

[demym]

I have the same problem on IOS12. Tried different workarounds, but nothing. Loadstop event is not fired, and i cannot determine the result of an authentication page thus making the user proceed to application. Is some fix planned for this ? Using it with Ionic 3. Thanks in advance

[sanjredfield]

Also having the same issue. Loadstop works rather erratically.

[DuBistKomisch]

Thanks @gurolayanlar I used a similar solution, but kept the loadstop event as well, and cleared the interval.

[xmetalmw]

@realweb Any chance you can share how you structured that in your code? I'm running into really inconsistent behaviors in iOS 12 as well and not firing the LoadStop seems to be a critical item. Any more specific tips would be appreciated.

[realweb]

@xmetalmw thanks for your interesting.

Sharing the coding, since it have a lot of embed method, wont help. But explain a little about it, can help.
Since my last post I made chengas regarding the "timer". Actually I was adding it cause the spinner was eternally there. So I added the timer to execute functions and reload the page.

So, the final work around was like this:

First, I turned of the spinner for inapp browser (iOS onluy option). Cause since the LoadStop event was not fired, the spinner was there eternally and this was one of the reasons apple reject the app during the review process.

Second, I started to use the URL on LoadStart method to do what I need to do using the URL parameter. Actually, for my case, I only need a parameter on the URL so dont make no difference if its on LoadStart or LoadStop.

I don´t know if in your app will be enough to use url from LoadStart and "assume" it was fully loaded.

I hope I could help.

thanks