Skip to content

[WIP] Use GeometryReader instead of pulling UIApplication.shared.connectedScenes - #2497

Open
Camji55 wants to merge 4 commits into
LoopKit:next-devfrom
Camji55:pull-request/fix-connected-scene-bug
Open

[WIP] Use GeometryReader instead of pulling UIApplication.shared.connectedScenes#2497
Camji55 wants to merge 4 commits into
LoopKit:next-devfrom
Camji55:pull-request/fix-connected-scene-bug

Conversation

@Camji55

@Camji55 Camji55 commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Potential fix for #2495

@Camji55 Camji55 changed the title Use GeometryReader instead of pulling UIApplication.shared.connectedScenes [WIP] Use GeometryReader instead of pulling UIApplication.shared.connectedScenes Aug 25, 2026
@marionbarker

Copy link
Copy Markdown
Contributor

Test

Started with next-dev branch, commit 16aa5b1

Since I am also testing Xcode 27 beta 5, I needed to make some updates in addition to the Loop change, and I'm doing some OmnipodKit testing at the same time.

  • Loop to this PR (32c7ff8)
  • LoopKit to tip of next-dev (Xcode 27)
  • TrueTime.swift to tip of master (Xcode 27)
  • OmnipodKit to fix/inplay-eager-connect-watchdog

Build with Xcode 27 beta 5 onto iPhone SE 3rd generation running iOS 26.6

Since we don't know how to reproduce the error, can't tell if this fixes anything. But I am getting these messages in Xcode:

Invalid sheet detent height: 0.0
Type: Fault | Timestamp: 2026-08-25 19:13:48.644696-0700 | Library: SwiftUICore | Subsystem: com.apple.SwiftUI | Category: Invalid Configuration | TID: 0x5c279

I rebuilt with Loop next-dev branch and still see the error messages in debug log, so that is not related to this code change

Invalid sheet detent height: 0.0
Type: Fault | Timestamp: 2026-08-25 19:18:44.352372-0700 | Library: SwiftUICore | Subsystem: com.apple.SwiftUI | Category: Invalid Configuration | TID: 0x5cacb

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