Search results for

“swiftui”

17,495 results found

Post

Replies

Boosts

Views

Activity

Reply to SystemLanguageModel.Adapter leaks ~100MB of irrecoverable APFS disk space per call
To clarify, this isn't a memory leak, it's an issue with not de-duplicating or evicting copied model weights from a SIP-protected disk space. I'm also not sure the bug is CLI-specific. I definitely observed it with my CLI tool, Junco,, but I have another SwiftUI application where I'm observing the issue as well. Simply running the app from XCode copies the weights & metadata to the location above, and I've only been able to delete the accumulated ~104GB (645 model clones) through Recovery Mode.
Topic: Machine Learning & AI SubTopic: Foundation Models
Apr ’26
Reply to SwiftUI View Not Initialized on Background Relaunch (CoreBluetooth / Cold Start?)
I will leave the discussion of why UI elements are sometimes not initialized for non-UI (background) launches to others who have more expertise on these things. Here, I will address the CoreBluetooth problem you are obviously having due to this behavior. In general it is not a correct pattern to make app-wide non-UI functionality dependent on UI elements like Views. Indeed, CoreBluetooth works at the app level, and needs to be initialized and used at the app level, not hidden behind a view. When the system relaunches your app due to the sensor coming back in range, it is doing so because the expectation is your app needs to take some action and respond to the BLE event that occurred (whether it is the sensor coming in or out of range, new data arriving, connection dropping, etc.) as soon as possible, and it should not be waiting for the app views to be rebuilt after launch, even in the 9 out of 10 case this seems to work for you. The correct use is to bring all CoreBluetooth functionality to the app level. Pr
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Apr ’26
View Navigation Title Disappears on watchOS Target When Built With Xcode 26+
I have a SwiftUI view in a watch companion app, and when I build my app with Xcode 26.2 or 26.3, the navigation title on a presented screen disappears after the watch screen goes dark. So, the navigation title is only visible when the screen is first presented and not again after the watch screen goes dark, for example when the user lowers their arm. Please see the screenshots for a better understanding. Notice that the Bench Press text is not visible in the third image. Also, I’ve confirmed that this does not happen when the app is built with Xcode 16.4. First Image (initial presentation of the screen): Second Image (watch screen goes dark): Third Image (watch screen goes back on, title missing): Although I've confirmed that this is related to Xcode versioning, and it happens on multiple screens, here is the redacted version of this SwiftUI view that is shown in the screenshots, in case it helps: var body: some View { NavigationStack(path: $viewModel.pushedViews) { TabView(selection: $selec
Topic: UI Frameworks SubTopic: SwiftUI Tags:
0
0
124
Apr ’26
Trying to load image & identifier from photo library with PhotosPicker
I'm updating an older Mac app written in Objective C and OpenGL to be a mutliplatform app in SwiftUI and Metal. The app loads images and creates kaleidoscope animations from them. It is a document-based application, and saves info about the kaleidoscope into the document. On macOS, it creates a security-scoped bookmark to remember the user's chosen image. On iOS, I use a PhotosPicker to have the user choose an image from their photo library to use. I would like to get the itemIdentifier from the image they choose and save that into my document so I can use it to fetch the image when the user reloads the kaleidoscope document in the future. However, the call to loadTransferable is returning nil for the itemIdentifier. Here is my iOS/iPadOS code: #if os(macOS) // Mac code #else PhotosPicker(Choose image, selection: $selectedItem, matching: .images) .onChange(of: selectedItem) { Task { if let newValue = selectedItem { scopeState.isHEIC = newValue.supportedContentTypes.contains(UTType.heic) let data = tr
Topic: Media Technologies SubTopic: Photos & Camera Tags:
1
0
1.2k
Apr ’26
MapKit SwiftUI Map with .standard(elevation: .realistic) falls back to 2D in globe mode, while .hybrid(elevation: .realistic) remains 3D
Overview When using SwiftUI Map with .standard(elevation: .realistic) and a globe-style presentation, the map unexpectedly renders as a flat 2D map instead of a 3D globe / realistic terrain view. In the same view, switching to .hybrid(elevation: .realistic) preserves the expected 3D globe behavior. This appears to be a rendering bug or regression specific to the .standard style under globe mode, not an app-level issue. The issue is reproducible in my app’s competition map screen and has also been reported by other developers online. Steps to Reproduce Create a SwiftUI Map. Bind it to a MapCameraPosition. Apply a standard map style with realistic elevation: .mapStyle(.standard(elevation: .realistic)) Configure the UI so the user can switch between: standard + globe hybrid + globe Zoom out / interact with the map in globe mode. Expected Results Map with .standard(elevation: .realistic) should continue to render with globe / 3D realistic terrain behavior, consistent with realistic elevation sup
Topic: App & System Services SubTopic: Maps & Location Tags:
1
0
517
Apr ’26
SwiftUI View Not Initialized on Background Relaunch (CoreBluetooth / Cold Start?)
I have a question regarding cold start and pre-warming behavior on iOS. I’m developing a SwiftUI app that continuously receives data from a BLE device in the background. We’ve observed that after the BLE stream stops, the OS often terminates our app. Later, when the sensor comes back into range, iOS appears to relaunch (or reinitialize) the app. In our app, we use a WindowGroup like this: WindowGroup { AppView(store: store) } We’ve placed our BLE reconnection logic inside a .task modifier in AppView. What’s confusing is this: Most of the time, when the app is relaunched, AppView is created and the .task runs as expected. However, in about 1 out of 10 cases, AppView is not created at all, so the .task does not execute. I’m trying to understand: Under what conditions does iOS relaunch an app without fully initializing the SwiftUI view hierarchy? Is this related to pre-warming or background relaunch mechanisms (e.g., CoreBluetooth state restoration)? What determines whether the WindowGroup and
Topic: UI Frameworks SubTopic: SwiftUI Tags:
2
0
656
Apr ’26
Reply to Can’t paste into Simulator after updating to Xcode 26.4
@dser I don't see that issue on 26.5 beta 2. I went ahead and created a new project in SwiftUI struct ContentView: View { @State private var inputText: String = var body: some View { VStack { TextField(Test, text: $inputText) } } } I was able to copy and paste into the TextField. Can you provide me the steps you doing where you are still seeing the issue? Can you copy and paste the version of your Xcode including the build number? Thanks Albert
  Worldwide Developer Relations.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Apr ’26
Embedded Collection View in SwiftUI offset issue
I have a collection view that covers all the screen and it is scrolling behavior is paging. This collection view is embedded in a UIViewRepresentable and used in a SwiftUI app. The issue is that when users rotate the devices, sometimes the CollectionView.contentOffset get miscalculated and shows 2 pages. This is the code that I'm using for the collectionView and collectionViewLayout: class PageFlowLayout: UICollectionViewFlowLayout { override class var layoutAttributesClass: AnyClass { UICollectionViewLayoutAttributes.self } private var calculatedAttributes: [UICollectionViewLayoutAttributes] = [] private var calculatedContentWidth: CGFloat = 0 private var calculatedContentHeight: CGFloat = 0 public weak var delegate: PageFlowLayoutDelegate? override var collectionViewContentSize: CGSize { return CGSize(width: self.calculatedContentWidth, height: self.calculatedContentHeight) } override init() { super.init() self.estimatedItemSize = .zero self.scrollDirection = .horizontal self.minimumLineSpacing = 0
Topic: UI Frameworks SubTopic: General Tags:
6
0
457
Apr ’26
CKRecordZone deleted when second user accepts zone-wide CKShare
I'm seeing a critical issue where a custom CKRecordZone is consistently deleted server-side when a second iCloud account interacts with a zone-wide CKShare. I've reproduced this 20+ times across two days and have exhausted every client-side fix I can think of. Looking for guidance on what might be going wrong. Setup Container: iCloud.com.cohencooks (production app on App Store) Custom CKRecordZone in owner's private database Zone-wide CKShare(recordZoneID:) (iOS 15+ zone sharing) SwiftData with ModelConfiguration(cloudKitDatabase: .none) — no automatic CloudKit mirroring Acceptance via CKFetchShareMetadataOperation → CKContainer.accept(metadata) (no UICloudSharingController) Minimal reproduction // 1. Owner creates zone + share let zone = CKRecordZone(zoneName: MyZone) try await privateDB.save(zone) let share = CKShare(recordZoneID: zone.zoneID) share[CKShare.SystemFieldKey.title] = My Share as CKRecordValue share.publicPermission = .readWrite let (results, _) = try await privateDB.modifyRecords(saving: [shar
Topic: App & System Services SubTopic: iCloud Tags:
1
0
559
Apr ’26
CKRecordZone deleted when second user accepts zone-wide CKShare
I'm seeing a critical issue where a custom CKRecordZone is consistently deleted server-side when a second iCloud account interacts with a zone-wide CKShare. I've reproduced this 20+ times across two days and have exhausted every client-side fix I can think of. Looking for guidance on what might be going wrong. Setup Container: iCloud.com.cohencooks (production app on App Store) Custom CKRecordZone in owner's private database Zone-wide CKShare(recordZoneID:) (iOS 15+ zone sharing) SwiftData with ModelConfiguration(cloudKitDatabase: .none) — no automatic CloudKit mirroring Acceptance via CKFetchShareMetadataOperation → CKContainer.accept(metadata) (no UICloudSharingController) Minimal reproduction // 1. Owner creates zone + share let zone = CKRecordZone(zoneName: MyZone) try await privateDB.save(zone) let share = CKShare(recordZoneID: zone.zoneID) share[CKShare.SystemFieldKey.title] = My Share as CKRecordValue share.publicPermission = .readWrite let (results, _) = try await privateDB.modifyRecords(saving: [shar
Topic: App & System Services SubTopic: iCloud Tags:
3
0
497
Apr ’26
Reply to Detect hardware keyboard with SwiftUI
Hi @Dokug, To detect the presence of a hardware keyboard, you can utilize the isHardwareKeyboardInputExpected property. It signifies that a hardware keyboard is connected and available for input. It's part of UIKit, but you could, for example, use .onReceive in SwiftUI to monitor the keyboardWillShow notification, and update a @State property accordingly. Best, -J
Topic: App & System Services SubTopic: Hardware Tags:
Apr ’26
iOS 26: Interactive sheet dismissal causes layout hitch in underlying SwiftUI view
I’ve been investigating a noticeable animation hitch when interactively dismissing a sheet over a SwiftUI screen with moderate complexity. This was not the case on iOS 18, so I’m curious if others are seeing the same on iOS 26 or have found any mitigations. When dismissing a sheet via the swipe gesture, there’s a visible hitch right after lift-off. The hitch comes from layout work in the underlying view (behind the sheet) The duration scales with the complexity of that view (e.g. number of TextFields/layout nodes) The animation for programmatic dismiss (e.g. tapping a “Done” button) is smooth, although it hangs for a similar amount of time before dismissing, so it appears that the underlying work still happens. SwiftUI is not reevaluating the body during this (validated with Self._printChanges()), so that is not the cause. Using Instruments, the hitch shows up as a layout spike on the main thread: 54ms UIView layoutSublayersOfLayer 54ms └─ _UIHostingView.layoutSubviews 38ms └─ SwiftUI.ViewGr
Topic: UI Frameworks SubTopic: SwiftUI Tags:
3
0
703
Apr ’26
Detect hardware keyboard with SwiftUI
In an application we are developing, we would like to show a (non-interactable) textfield when a hardware keyboard is connected to the iPad. Therefore my question: Using SwiftUI, is it possible to detect the presence of a hardware keyboard and store that state inside a boolean like isHardwareKeyboardConnected?
Topic: App & System Services SubTopic: Hardware Tags:
1
0
910
Apr ’26
Flutter iOS Project: WidgetKit Extension Not Embedding / Build Cycle Error
Hi, I need your opinion about an issue we faced while trying to implement an iOS widget in our Flutter app. Here is what we did and the problems we encountered: We created a Widget Extension (SwiftUI + WidgetKit) inside the existing Flutter iOS project. The widget files were generated correctly (Widget.swift, WidgetBundle.swift, Info.plist, etc.). However, during the integration, we faced multiple issues: Build Cycle Error We repeatedly got: “Cycle inside Runner; building could produce unreliable results” This was related to embedding the widget extension into the Runner target. Embed Problems Sometimes Xcode did not automatically create the “Embed App Extensions” phase. When we added it manually → build cycle errors appeared. When we removed it → the widget was not embedded at all (no PlugIns folder in Runner.app). Duplicate / Conflicting Embed The extension appeared both in: “Embed Foundation Extensions” “Frameworks, Libraries, and Embedded Content” Removing one often broke the build or removed the
Topic: App & System Services SubTopic: Widgets & Live Activities Tags:
3
0
564
Apr ’26
Widget layout issue: Unexpected padding/content inset on specific widget types
Hello everyone, I am currently developing a suite of widgets for my iOS app using SwiftUI and WidgetKit. While the initial widgets (let's call them Widget A, B, and C) render perfectly, I am encountering a strange layout issue with a new widget (Widget D). The Issue: On the Home Screen, Widget D appears to have an unwanted internal padding or squeezed content inset, even though it shares a similar structural implementation with the other functional widgets. Technical Details: I am using .frame(maxWidth: .infinity, maxHeight: .infinity) on the main container to ensure the content fills the available space.
Topic: App & System Services SubTopic: Widgets & Live Activities
0
0
376
Apr ’26
Reply to SystemLanguageModel.Adapter leaks ~100MB of irrecoverable APFS disk space per call
To clarify, this isn't a memory leak, it's an issue with not de-duplicating or evicting copied model weights from a SIP-protected disk space. I'm also not sure the bug is CLI-specific. I definitely observed it with my CLI tool, Junco,, but I have another SwiftUI application where I'm observing the issue as well. Simply running the app from XCode copies the weights & metadata to the location above, and I've only been able to delete the accumulated ~104GB (645 model clones) through Recovery Mode.
Topic: Machine Learning & AI SubTopic: Foundation Models
Replies
Boosts
Views
Activity
Apr ’26
Reply to SwiftUI View Not Initialized on Background Relaunch (CoreBluetooth / Cold Start?)
I will leave the discussion of why UI elements are sometimes not initialized for non-UI (background) launches to others who have more expertise on these things. Here, I will address the CoreBluetooth problem you are obviously having due to this behavior. In general it is not a correct pattern to make app-wide non-UI functionality dependent on UI elements like Views. Indeed, CoreBluetooth works at the app level, and needs to be initialized and used at the app level, not hidden behind a view. When the system relaunches your app due to the sensor coming back in range, it is doing so because the expectation is your app needs to take some action and respond to the BLE event that occurred (whether it is the sensor coming in or out of range, new data arriving, connection dropping, etc.) as soon as possible, and it should not be waiting for the app views to be rebuilt after launch, even in the 9 out of 10 case this seems to work for you. The correct use is to bring all CoreBluetooth functionality to the app level. Pr
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Apr ’26
View Navigation Title Disappears on watchOS Target When Built With Xcode 26+
I have a SwiftUI view in a watch companion app, and when I build my app with Xcode 26.2 or 26.3, the navigation title on a presented screen disappears after the watch screen goes dark. So, the navigation title is only visible when the screen is first presented and not again after the watch screen goes dark, for example when the user lowers their arm. Please see the screenshots for a better understanding. Notice that the Bench Press text is not visible in the third image. Also, I’ve confirmed that this does not happen when the app is built with Xcode 16.4. First Image (initial presentation of the screen): Second Image (watch screen goes dark): Third Image (watch screen goes back on, title missing): Although I've confirmed that this is related to Xcode versioning, and it happens on multiple screens, here is the redacted version of this SwiftUI view that is shown in the screenshots, in case it helps: var body: some View { NavigationStack(path: $viewModel.pushedViews) { TabView(selection: $selec
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
0
Boosts
0
Views
124
Activity
Apr ’26
Trying to load image & identifier from photo library with PhotosPicker
I'm updating an older Mac app written in Objective C and OpenGL to be a mutliplatform app in SwiftUI and Metal. The app loads images and creates kaleidoscope animations from them. It is a document-based application, and saves info about the kaleidoscope into the document. On macOS, it creates a security-scoped bookmark to remember the user's chosen image. On iOS, I use a PhotosPicker to have the user choose an image from their photo library to use. I would like to get the itemIdentifier from the image they choose and save that into my document so I can use it to fetch the image when the user reloads the kaleidoscope document in the future. However, the call to loadTransferable is returning nil for the itemIdentifier. Here is my iOS/iPadOS code: #if os(macOS) // Mac code #else PhotosPicker(Choose image, selection: $selectedItem, matching: .images) .onChange(of: selectedItem) { Task { if let newValue = selectedItem { scopeState.isHEIC = newValue.supportedContentTypes.contains(UTType.heic) let data = tr
Topic: Media Technologies SubTopic: Photos & Camera Tags:
Replies
1
Boosts
0
Views
1.2k
Activity
Apr ’26
MapKit SwiftUI Map with .standard(elevation: .realistic) falls back to 2D in globe mode, while .hybrid(elevation: .realistic) remains 3D
Overview When using SwiftUI Map with .standard(elevation: .realistic) and a globe-style presentation, the map unexpectedly renders as a flat 2D map instead of a 3D globe / realistic terrain view. In the same view, switching to .hybrid(elevation: .realistic) preserves the expected 3D globe behavior. This appears to be a rendering bug or regression specific to the .standard style under globe mode, not an app-level issue. The issue is reproducible in my app’s competition map screen and has also been reported by other developers online. Steps to Reproduce Create a SwiftUI Map. Bind it to a MapCameraPosition. Apply a standard map style with realistic elevation: .mapStyle(.standard(elevation: .realistic)) Configure the UI so the user can switch between: standard + globe hybrid + globe Zoom out / interact with the map in globe mode. Expected Results Map with .standard(elevation: .realistic) should continue to render with globe / 3D realistic terrain behavior, consistent with realistic elevation sup
Topic: App & System Services SubTopic: Maps & Location Tags:
Replies
1
Boosts
0
Views
517
Activity
Apr ’26
SwiftUI View Not Initialized on Background Relaunch (CoreBluetooth / Cold Start?)
I have a question regarding cold start and pre-warming behavior on iOS. I’m developing a SwiftUI app that continuously receives data from a BLE device in the background. We’ve observed that after the BLE stream stops, the OS often terminates our app. Later, when the sensor comes back into range, iOS appears to relaunch (or reinitialize) the app. In our app, we use a WindowGroup like this: WindowGroup { AppView(store: store) } We’ve placed our BLE reconnection logic inside a .task modifier in AppView. What’s confusing is this: Most of the time, when the app is relaunched, AppView is created and the .task runs as expected. However, in about 1 out of 10 cases, AppView is not created at all, so the .task does not execute. I’m trying to understand: Under what conditions does iOS relaunch an app without fully initializing the SwiftUI view hierarchy? Is this related to pre-warming or background relaunch mechanisms (e.g., CoreBluetooth state restoration)? What determines whether the WindowGroup and
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
2
Boosts
0
Views
656
Activity
Apr ’26
Reply to Can’t paste into Simulator after updating to Xcode 26.4
@dser I don't see that issue on 26.5 beta 2. I went ahead and created a new project in SwiftUI struct ContentView: View { @State private var inputText: String = var body: some View { VStack { TextField(Test, text: $inputText) } } } I was able to copy and paste into the TextField. Can you provide me the steps you doing where you are still seeing the issue? Can you copy and paste the version of your Xcode including the build number? Thanks Albert
  Worldwide Developer Relations.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Apr ’26
Embedded Collection View in SwiftUI offset issue
I have a collection view that covers all the screen and it is scrolling behavior is paging. This collection view is embedded in a UIViewRepresentable and used in a SwiftUI app. The issue is that when users rotate the devices, sometimes the CollectionView.contentOffset get miscalculated and shows 2 pages. This is the code that I'm using for the collectionView and collectionViewLayout: class PageFlowLayout: UICollectionViewFlowLayout { override class var layoutAttributesClass: AnyClass { UICollectionViewLayoutAttributes.self } private var calculatedAttributes: [UICollectionViewLayoutAttributes] = [] private var calculatedContentWidth: CGFloat = 0 private var calculatedContentHeight: CGFloat = 0 public weak var delegate: PageFlowLayoutDelegate? override var collectionViewContentSize: CGSize { return CGSize(width: self.calculatedContentWidth, height: self.calculatedContentHeight) } override init() { super.init() self.estimatedItemSize = .zero self.scrollDirection = .horizontal self.minimumLineSpacing = 0
Topic: UI Frameworks SubTopic: General Tags:
Replies
6
Boosts
0
Views
457
Activity
Apr ’26
CKRecordZone deleted when second user accepts zone-wide CKShare
I'm seeing a critical issue where a custom CKRecordZone is consistently deleted server-side when a second iCloud account interacts with a zone-wide CKShare. I've reproduced this 20+ times across two days and have exhausted every client-side fix I can think of. Looking for guidance on what might be going wrong. Setup Container: iCloud.com.cohencooks (production app on App Store) Custom CKRecordZone in owner's private database Zone-wide CKShare(recordZoneID:) (iOS 15+ zone sharing) SwiftData with ModelConfiguration(cloudKitDatabase: .none) — no automatic CloudKit mirroring Acceptance via CKFetchShareMetadataOperation → CKContainer.accept(metadata) (no UICloudSharingController) Minimal reproduction // 1. Owner creates zone + share let zone = CKRecordZone(zoneName: MyZone) try await privateDB.save(zone) let share = CKShare(recordZoneID: zone.zoneID) share[CKShare.SystemFieldKey.title] = My Share as CKRecordValue share.publicPermission = .readWrite let (results, _) = try await privateDB.modifyRecords(saving: [shar
Topic: App & System Services SubTopic: iCloud Tags:
Replies
1
Boosts
0
Views
559
Activity
Apr ’26
CKRecordZone deleted when second user accepts zone-wide CKShare
I'm seeing a critical issue where a custom CKRecordZone is consistently deleted server-side when a second iCloud account interacts with a zone-wide CKShare. I've reproduced this 20+ times across two days and have exhausted every client-side fix I can think of. Looking for guidance on what might be going wrong. Setup Container: iCloud.com.cohencooks (production app on App Store) Custom CKRecordZone in owner's private database Zone-wide CKShare(recordZoneID:) (iOS 15+ zone sharing) SwiftData with ModelConfiguration(cloudKitDatabase: .none) — no automatic CloudKit mirroring Acceptance via CKFetchShareMetadataOperation → CKContainer.accept(metadata) (no UICloudSharingController) Minimal reproduction // 1. Owner creates zone + share let zone = CKRecordZone(zoneName: MyZone) try await privateDB.save(zone) let share = CKShare(recordZoneID: zone.zoneID) share[CKShare.SystemFieldKey.title] = My Share as CKRecordValue share.publicPermission = .readWrite let (results, _) = try await privateDB.modifyRecords(saving: [shar
Topic: App & System Services SubTopic: iCloud Tags:
Replies
3
Boosts
0
Views
497
Activity
Apr ’26
Reply to Detect hardware keyboard with SwiftUI
Hi @Dokug, To detect the presence of a hardware keyboard, you can utilize the isHardwareKeyboardInputExpected property. It signifies that a hardware keyboard is connected and available for input. It's part of UIKit, but you could, for example, use .onReceive in SwiftUI to monitor the keyboardWillShow notification, and update a @State property accordingly. Best, -J
Topic: App & System Services SubTopic: Hardware Tags:
Replies
Boosts
Views
Activity
Apr ’26
iOS 26: Interactive sheet dismissal causes layout hitch in underlying SwiftUI view
I’ve been investigating a noticeable animation hitch when interactively dismissing a sheet over a SwiftUI screen with moderate complexity. This was not the case on iOS 18, so I’m curious if others are seeing the same on iOS 26 or have found any mitigations. When dismissing a sheet via the swipe gesture, there’s a visible hitch right after lift-off. The hitch comes from layout work in the underlying view (behind the sheet) The duration scales with the complexity of that view (e.g. number of TextFields/layout nodes) The animation for programmatic dismiss (e.g. tapping a “Done” button) is smooth, although it hangs for a similar amount of time before dismissing, so it appears that the underlying work still happens. SwiftUI is not reevaluating the body during this (validated with Self._printChanges()), so that is not the cause. Using Instruments, the hitch shows up as a layout spike on the main thread: 54ms UIView layoutSublayersOfLayer 54ms └─ _UIHostingView.layoutSubviews 38ms └─ SwiftUI.ViewGr
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
3
Boosts
0
Views
703
Activity
Apr ’26
Detect hardware keyboard with SwiftUI
In an application we are developing, we would like to show a (non-interactable) textfield when a hardware keyboard is connected to the iPad. Therefore my question: Using SwiftUI, is it possible to detect the presence of a hardware keyboard and store that state inside a boolean like isHardwareKeyboardConnected?
Topic: App & System Services SubTopic: Hardware Tags:
Replies
1
Boosts
0
Views
910
Activity
Apr ’26
Flutter iOS Project: WidgetKit Extension Not Embedding / Build Cycle Error
Hi, I need your opinion about an issue we faced while trying to implement an iOS widget in our Flutter app. Here is what we did and the problems we encountered: We created a Widget Extension (SwiftUI + WidgetKit) inside the existing Flutter iOS project. The widget files were generated correctly (Widget.swift, WidgetBundle.swift, Info.plist, etc.). However, during the integration, we faced multiple issues: Build Cycle Error We repeatedly got: “Cycle inside Runner; building could produce unreliable results” This was related to embedding the widget extension into the Runner target. Embed Problems Sometimes Xcode did not automatically create the “Embed App Extensions” phase. When we added it manually → build cycle errors appeared. When we removed it → the widget was not embedded at all (no PlugIns folder in Runner.app). Duplicate / Conflicting Embed The extension appeared both in: “Embed Foundation Extensions” “Frameworks, Libraries, and Embedded Content” Removing one often broke the build or removed the
Topic: App & System Services SubTopic: Widgets & Live Activities Tags:
Replies
3
Boosts
0
Views
564
Activity
Apr ’26
Widget layout issue: Unexpected padding/content inset on specific widget types
Hello everyone, I am currently developing a suite of widgets for my iOS app using SwiftUI and WidgetKit. While the initial widgets (let's call them Widget A, B, and C) render perfectly, I am encountering a strange layout issue with a new widget (Widget D). The Issue: On the Home Screen, Widget D appears to have an unwanted internal padding or squeezed content inset, even though it shares a similar structural implementation with the other functional widgets. Technical Details: I am using .frame(maxWidth: .infinity, maxHeight: .infinity) on the main container to ensure the content fills the available space.
Topic: App & System Services SubTopic: Widgets & Live Activities
Replies
0
Boosts
0
Views
376
Activity
Apr ’26