-
Notifications
You must be signed in to change notification settings - Fork 38
Closed
Labels
Description
Describe the bug
In a clean system environment, start the sample application without logging in to the Microsoft account, try to log in to the Microsoft account, after selecting the account type (such as MSA), the account panel exits, and subsequent login steps cannot be performed.
The problem was found in Clock
- Is this bug a regression in the toolkit? If so, what toolkit version did you last see it work:
Steps to Reproduce
Steps to reproduce the behavior:
- Start a brand new virtual machine
- Open the Clock app
- Click the login button in the lower left corner
- Choose an account type instead of logging into an existing account
- Observe behavior
Expected behavior
User can log into new account
Screenshots
None
Environment
NuGet Package(s): 7.1.1
Package Version(s): 7.1.1
Windows 10 Build Number:
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [ ] October 2018 Update (17763)
- [ ] May 2019 Update (18362)
- [x] Insider Build (build number: 22000)
App min and target version:
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [ ] October 2018 Update (17763)
- [ ] May 2019 Update (18362)
- [x] Insider Build (22000)
Device form factor:
- [x] Desktop
- [ ] Xbox
- [ ] Surface Hub
- [ ] IoT
Visual Studio
- [ ] 2017 (version: )
- [ ] 2019 (version: )
- [ ] 2019 Preview (version: )
- [x] 2022 (version: 17.2.3)
Additional context
It's not 100% reproducible, but for some specific devices it's reproducible almost every time