[
https://issues.apache.org/jira/browse/CB-10566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341663#comment-15341663
]
Naveen Bellary commented on CB-10566:
-------------------------------------
[~vidhya] , Can you please share me the code of accessing cookie set in
inappbrowser in IOS. I am not able to access it, I need to set default headers
for subsequent angular http calls.
> ios 9.2 in-app browser & cookie handoff
> ---------------------------------------
>
> Key: CB-10566
> URL: https://issues.apache.org/jira/browse/CB-10566
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin InAppBrowser
> Affects Versions: 1.2.0
> Environment: ionic app ( inappbrowser 1.2.0 ) + ios 9.2
> Reporter: Vidhyashankar
> Priority: Minor
> Labels: starter
>
> We are using the inappbrowser to open an external webpage for authentication
> in an ionic app. On a successful auth, we receive auth token as a cookie as
> part of the response in the in-appbrowser. On closing the in-appbrowser, any
> subsequent http calls we make through the core Angular $http service from the
> ionic webview has the cookie and allows us to make calls. This works
> perfectly in Android and pre ios 9.2
> In ios 9.2, there is a delayed hand-off, meaning from the time the
> in-appbrowser receives the token (we close in-app browser then and try making
> the $http call right away) and for us to make a successful $http call takes
> about a minute. In this duration, the cookie is not present in the webview.
> Eventually after a minute or so, the cookie is present and we can make $http
> calls.
> This was working ok with ios 9 and pre ios 9 OS without any delay. I am not
> sure, if this has anything to do with the in-app browser plugin. But i was
> wondering if there is anything i can look at or if anyone has come across a
> similar issue ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
