Software Archive
Read-only legacy content
Announcements
FPGA community forums and blogs have moved to the Altera Community. Existing Intel Community members can sign in with their current credentials.

InAppBrowser plugin's inconsistent behavior in windows phone 8

Sam_Deepak
Beginner
860 Views

 

Hi,

I am using InAppBrowser plugin to call remote JSON API in terms of providing additional layer of protection for  consuming it. It works fine in android.

In windows phone 8.x, I am facing a strange issue. When executing functions that reside in scripts from the page loaded in InAppBrowser, it sometimes gives me an error saying "Unspecified error." in plugins/cordova-plugin-inappbrowser/src/windows/InAppBrowserProxy.js.

The strange thing is that it randomly throws this error sometimes and sometimes it works. I tried all techniques I could think of and read from internet. Could someone please help me resolve this issue.

0 Kudos
4 Replies
PaulF_IntelCorp
Employee
860 Views

Sam, this is another one I would search StackOverflow for help, we don't yet have enough experience with the new Cordova Windows platforms to know all the quirks.

0 Kudos
Sam_Deepak
Beginner
860 Views

Hi Paul,

Same here, I searched everywhere, I could not a find a solution or workaround for this. Please let me know if you come across anything.

 

0 Kudos
Sam_Deepak
Beginner
860 Views

Hi Paul,

It seems that this error occurs when you execute scripts many times, i.e., I call a remote Json API using this InAppBrowser and while calling second API sometimes this error occurs.

So what I did is, I closed the InAppBrowser every time, I am done with an API call and created a new instance of InAppBrowser for every API call. It works. I could not understand how this works in Android regardless of how many times it calls multiple  calls using same InAppBrowser instance.

 

0 Kudos
PaulF_IntelCorp
Employee
860 Views

This is probably due to a difference in the memory management implementations between the two platforms. An Android webview is not representative of a Windows webview or an iOS webview, they are quite different "under the hood" -- just like browsers from different vendors have different behavior.

0 Kudos
Reply