Skip to content

Watch app: restore G7SensorKit's framework reference - #2652

Open
jeremybarnum wants to merge 2 commits into
LoopKit:next-devfrom
jeremybarnum:fix/watch-g7sensorkit-reference
Open

jeremybarnum wants to merge 2 commits into
LoopKit:next-devfrom
jeremybarnum:fix/watch-g7sensorkit-reference

Conversation

@jeremybarnum

@jeremybarnum jeremybarnum commented Nov 3, 2026 •

Copy link
Copy Markdown

#2645 deleted the watch app's G7SensorKit file reference and two of its build entries while moving files into LoopCore. The watch app still imports G7SensorKit (WatchDeviceManagers.swift), so a build without an already-built G7SensorKit fails with "Unable to resolve module dependency: 'G7SensorKit'". This puts back the five lines as they were before #2645.

It also removes three entries #2645 added to the watch app's framework list, for OmnipodKit, RileyLinkKit and RileyLinkBLEKit. They came from Sport Mode's watch app and have no definitions behind them, so they refer to nothing.

LoopWorkspace's next-dev still pins Loop from before #2645, so it builds today; it would break at the next bump of Loop.

🤖 Generated with Claude Code

Jeremy Barnum and others added 2 commits November 3, 2026 00:34
LoopKit#2645 deleted the watch app's G7SensorKit file reference and two of its
build entries while moving files into LoopCore. The watch app still
imports G7SensorKit (WatchDeviceManagers.swift), so a build without an
already-built G7SensorKit fails with "Unable to resolve module dependency:
'G7SensorKit'". This puts back the five lines as they were before LoopKit#2645.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…efinition

LoopKit#2645 also added entries for OmnipodKit, RileyLinkKit and RileyLinkBLEKit
to the watch app's framework list, carried over from Sport Mode's watch
app, with no definitions behind them. They refer to nothing, and the stock
watch app uses none of those kits; this removes them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@dabear

dabear commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

@ps2 This fix should be brought in ASAP as it breaks loop-next-dev when doing a clean build

@jeremybarnum

Copy link
Copy Markdown
Author

@ps2 This fix should be brought in ASAP as it breaks loop-next-dev when doing a clean build

Some additional cleanups now pushed that will help resolve this in a principled way.

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.

2 participants