Skip to content

Adopt async device deletion - #2647

Merged
ps2 merged 1 commit into
next-devfrom
async-device-deletion
Nov 2, 2026
Merged

ps2 merged 1 commit into
next-devfrom
async-device-deletion

Conversation

@ps2

@ps2 ps2 commented Nov 2, 2026

Copy link
Copy Markdown
Collaborator
  • cgmManagerWantsDeletion and pumpManagerWantsDeletion run on the main actor directly, with no continuation or Task hop.
  • The debug menu, testing scenarios, Loop reset and the watch's CGM host await delete().
  • Pump deletion can no longer fail, so the "Could Not Restart" alert that reported a failed prepareForDeactivation is removed.

Tested: LoopTests 426 pass. In the simulator, deleting a G7 (g7sim), the Pump Simulator, and Omnipod after a pod-simulator pod each log "wants deletion", and the screen dismisses afterwards.

Part of the async device deletion change in LoopKit/LoopKit#685, which this depends on. They merge together.

cgmManagerWantsDeletion and pumpManagerWantsDeletion run on the main actor
directly instead of hopping through a continuation or a Task. The debug
menu, testing scenarios, Loop reset and the watch's CGM host await delete().

Pump deletion can no longer fail, so the "Could Not Restart" alert that
reported a failed prepareForDeactivation is removed.
@ps2
ps2 merged commit 29928c1 into next-dev Nov 2, 2026
@ps2
ps2 deleted the async-device-deletion branch November 2, 2026 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant