We have a PWA written in Angular for which we use AzureAD (using ng-adal) for the login.
When we log in, a series of redirects are being made until we get back to our app (with the auth ticket). If we configure the "manifest.json" to display:browser, everything works as expected. The problem comes if we set it up as display:standalone. This way, when we install it in Android we get the look and feel of a native app (no browser chrome, splash screen,...) but the login breaks.
The effect we get is that the AzureAD page opens in a browser view (expected), but the redirection to our page is still on the browser view (with an X button in the to left corner). In this "browser view" we are authenticated, but if we use the X button, this view is closed and we go back to the PWA but remain unauthenticated.
Any idea of what might be happening?
Thanks!
Added a quick example (it's a test for another thing).
The icon at the top right corner redirects to another domain which redirects back to this page. If we add the app to an Android home screen (it does not add all the icons as I have not configured the PWA manifest completely, but the effect is view-able), we see that clicking on the icon, a web view opens to go to the first redirect but remains open for the second redirect back.
What I would expect is that the second redirect will goback to my PWA without the web-view chrome.
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙；凝视深渊过久,深渊将回以凝视…
