microsoft / microsoft/WindowsAppSDK

Inconsistent behavior of the AppointmentStore API

Open
#1,852 4 comments 5 reactions 1 assignee View on GitHub

@MythiliM is already working on this.

Since Jan 4, 2022.

transfer-to-platform
Dominant language
C++
Stars
4.7k
Forks
471
Avg merge
3d 13h
Merged PRs (30d)
28

Description

Describe the bug

I use the AppointmentStore in my app Ink Calendar to display and edit users' appointments. However in the past year the API has become unstable and unreliable. I have experienced the issue personally and have had users email me upset this feature stopped working.

There are a few failures of the API but the one most important to me is when the AppointmentStore.ShowEditNewAppointmentAsync(Appointment) method returns an empty string instead of a RoamingID of the new appointment. Normally this would mean the user canceled the "Add" but from first hand experience I know this happens even when the new appointment is accepted.

Once the AppointmentStore gets into this error state all of the appointment data becomes stale and does not update. It is unclear why this error state occurs or how to recover the AppointmentStore to get current appointment information from the operating system.

Steps to reproduce the bug

Here is a GitHub repro I made to reproduce this issue.
https://github.com/TheJoeFin/AppointmentStoreReproBug

Expected behavior

AppointmentStore returns up-to-date appointment information for the users' calendars.
AppointmentStore returns a RoamingID when adding a new appointment.

Screenshots

No response

NuGet package version

No response

Packaging type

Packaged (MSIX)

Windows version

Windows 11 (22000), May 2021 Update (19043), October 2020 Update (19042), May 2020 Update (19041), November 2019 Update (18363), May 2019 Update (18362)

IDE

Visual Studio 2022-preview, Visual Studio 2022, Visual Studio 2019

Additional context

This is a UWP API and since it is not open source I do not know the best place to get support on this issue I'm having. I have posted this issue to several other Microsoft Support pages with no success. Please let me know the best place or person to help get this issue resolved.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.