AppointmentManager.ShowAddAppointmentAsync always returns empty string
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- operating-systems
Research direction
Start with Scenario2_Add.xaml.cs at the linked AppointmentManager.ShowAddAppointmentAsync call and reproduce the issue by following the listed steps on the Windows 11 configuration. Trace why the calendar window closes immediately without an exception. Done means the calendar remains open for adding or cancelling an appointment and the call no longer always returns an empty string.
Written by the indexing model from the issue text.
Description
Which sample are you reporting a bug in?
Scenario2_Add.xaml.cs
Example: Scenario2_Add.xaml.cs
Describe the bug
After calling AppointmentManager.ShowAddAppointmentAsync calendar window shows up and disappears immediately, returns empty string. Doesn't throw any exceptions.
https://github.com/microsoft/Windows-universal-samples/blob/7d37b035c2701f189097a5503c9c8e854934479d/Samples/Appointments/cs/Scenario2_Add.xaml.cs#L44C8-L44C8
To Reproduce
Steps to reproduce the behavior:
- Open app
- Click on Add an Appointment
- Click on Add Appointment button
- Calendar shows up and disappears
Expected behavior
Calendar window should show up and await for me to add or cancel appointment.
Screenshots
This is after calendar window disappears
Configuration
Windows 11 22H2 22621.1928, C#, Visual Studio 2019 Professional
Additional Context
We tried using sample on different machine with similar specs and outcome was the same
- Dominant language
- JavaScript
- Stars
- 9.7k
- Forks
- 7.8k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/Windows-universal-samples
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
microsoft/Windows-universal-samples#1442 · 6 comments ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
microsoft/Windows-universal-samples#1440 · 3 comments · 1 reaction ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/Windows-universal-samples#1437 · 3 comments ·
All issues in microsoft/Windows-universal-samples
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100