Closed iruffner closed 8 years ago
Hi iruffner,
Were you able to resolve this? I am also getting the same error. Any help around this would be much appreciated.
Unfortunately, I ended up rolling back to a previous version. I was not able to fix it otherwise.
Anyone had any luck resolving this issue yet?
Hi @iruffner I'm seeing this error also. Could you let me know which version you rolled back to that resolved this issue?
I believe it was 0.2.1, but I'm not 100% sure. I finally ended up rolling the latest version. What I found was that my handler would be called twice. The first call contained a result object with the data I'd expect, and then it was called a second time with no result object and the error message about the popup was closed. I added some special handling to look for that error string and ignore it.
It's a workaround that works for me, but still seems like the popup was closed message should be handled somewhere else upstream.
The issue should be resolved with the latest version as we’ve added more checks about it
I updated to 0.2.4, which also updated the InAppBrowser to 0.5.1. Now, when I use the popup login, I get the result object, but I am also getting the error string back that says "The popup was closed". The login seems successful, so I'm not sure why I'm receiving the error message. Any guidance on why that might be?
Edit: Sorry forgot to say that this is running on iOS 7.1.2.