Hi Ziqiao ,thank you for your reply. We’re quite concerned about this issue, as it significantly impacts our app’s functionality on watchOS 26. In its current state, the product has become practically unusable for our users, which is very disappointing for us. Any update or insight from the engineering team would be greatly appreciated.

Hi Ziqiao, We’ve also identified another issue related to data updates. I’ve submitted a new feedback report for this, with the ID FB20552903. Thank you in advance for your help.

Thanks for your suggestion. I’ve submitted the feedback report as recommended, and the issue ID is [FB20344425]. This issue had a critical impact on our app and nearly caused a complete failure of a core functionality. If possible, could you please share the usual process or expected timeline for addressing issues like this? I’d really appreciate any guidance you can provide. 谢谢你了 子乔（希望我没打错）！！！！

Sorry, I missed part of the code. In fact, the error scenario also has a callback. I just sent a local notification and then immediately called completionHandler().