[ad_1]
Now we have an internet app that’s proven in a local app A through SfAuthenticationSession. Now we have one other app B that’s like an auth supplier which is owned by one other group. Most of our performance is designed within the web-app.
The login stream is like this.
- App A launches web-app(in SfAuthenticationSession) and web-app checks for an current session, if no legitimate session exists, web-app launches app B through deeplink asking for login
- App B -after login- will launch web-app once more(in safari browser) with a token that can be utilized with our login APIs, as soon as we get session info from APIs we save them in cookies throughout the web-app.
- after the login completes web-app will use deeplinks to open app A in order that web-app could be proven throughout the app utilizing SfAuthenticationSession
- App A will acknowledge the deeplink and convey up web-app once more in SfAuthenticationSession to point out the UI. We face a problem right here the place SfAuthenticationSession cant learn the cookies and the entire course of repeats as soon as extra(however simply as soon as). Although SfAuthenticationSession can’t learn cookies we will see that we’re already logged into web-app in safari browser
The difficulty is reproducible if the person is fast via step 3, there shall be a immediate in safari browser asking to launch app A. If the person waits right here, the newly launched SfAuthenticationSession can learn cookies. If a delay is added earlier than launching the deeplink the possibilities of getting the login loop reduces.
Is there a recognized subject the place SfAuthenticationSession is “sometimes” not in a position to learn cookies set on Safari? And is there a workaround?
[ad_2]
