-
Notifications
You must be signed in to change notification settings - Fork 214
Login Screen Loses Provided User Email on Device Orientation in Android #1622
Comments
No new features will be implemented on ADAL. The team's efforts are on improving MSAL, the next-gen auth library. MSAL's wiki contains a migration guide from ADAL. Only regressions, high severity issues and security issues will be fixed on ADAL. Other issues are likely to have already been fixed in MSAL. If not, please log them and the team will prioritise them. |
@dinobu : We may have to address the same type of issue in MSAL, thus pls. open the issue there. We believe it's relatively simple to move from ADAL to MSAL however should you need assistance we are happy to help. |
@dinobu I am able to reproduce the issue in MSAL. would you mind opening an issue there? thanks. cc: @henrik-me |
I'll link this issue, as, I think, they are related. |
@dinobu : We would like to make this experience better. What is preventing you from moving to MSAL? |
No plans to move to MSAL but we are using Xamarin.Forms app (all 3 platforms) to authenticate with AzureAD, if you can provide me good guide to move to MSAL, I will take a look. But again, this is not planned to do, it is just my personal interest that I would like to take a look. We still need the ADAL fix. |
Thanks, I have already read both of these but will still take another look. Much appreciated. |
@dinobu Great...if you have any questions, let us know. |
Any movement on the hot fix for ADAL to resolve this issue? |
Sorry @dinobu , but this is not a regression and we will not fix this in ADAL. I am not sure when we'll be able to take a look at it in MSAL, but feel free to propose smth if you are so inclined. We accept contributions. |
@dinobu this fix will be in the 5.1.1 release, which will be out this week. Fix is also in MSAL and will be in next MSAL release. |
Included in 5.1.1 release |
I have Xamarin.Forms application that authenticates user against Azure AAD. That all works fine but on Android, device orientation looses user email on the Microsoft authentication screen.
Here, my device is in Portrait mode and I have entered user email:
If I enter user email and click on Next, I land on screen prompting me to enter password. If I now rotate device on Android, it will return me back to the screen above but notice, the screen has lost my previously entered user email, it is blank now
This is not happening on IOS devices, only Android. Device rotation should not return me back to screen prompting for user email not should it loose that information. Similarly, If I have entered password half way through and device is rotated, I should be just able to continue entering the rest of my password.
How do I prevent the rotation on this Sign in screen from loosing already entered user name and re-prompting for it? I dont want to disable rotation.
My MainActivity has already ConfigChages.Orientation attribute like below:
, but this is not resolving the issue and I think the reason is that AcquireTokenAsync is probably using WebView which refreshes itself on device rotation on Android. How do I prevent this? I dont think your API provides a way around this which is very annoying issue on mobile devices.
The text was updated successfully, but these errors were encountered: