“swiftui”

Title: tvOS 26 SwiftUI .searchable is overlapped by the sidebar collapse button I'm seeing what appears to be a SwiftUI layout issue on tvOS 26 involving .searchable and sidebar-based navigation. When a sidebar is collapsed, tvOS shows the system sidebar toggle/collapse control in the upper-left corner. A SwiftUI .searchable field placed locally on the Search page is positioned too close to the top of the screen, causing the sidebar control to overlap the search field. Environment tvOS 26 SwiftUI Tested on a physical Apple TV Xcode 26 Example structure My app originally used: NavigationSplitView { SidebarView() } detail: { SearchView() } The search modifier is applied only to the Search page: struct SearchView: View { @State private var searchText = var body: some View { ScrollView { // Search content } .searchable( text: $searchText, placement: .automatic ) } } The .searchable modifier is not applied to NavigationSplitView or the root view. When the sidebar is collapsed,

Reality Composer Pro 3 cannot create a new project or open an existing project on my Mac. After I select Create New Project or Open Existing Project, the operation begins but the project editor never appears. The Reality Composer Pro process remains alive and idle, and no standard crash report is generated. Environment: MacBook Pro Mac15,9 Apple M3 Max, 48 GB unified memory macOS 26.6 (25G72) Reality Composer Pro 3 Beta 4, version 3.080.0.1.500.1 Built-in display only Steps to reproduce: Quit Reality Composer Pro. Launch /Applications/RealityComposerPro.app. Select Create New Project. Observe that the editor never appears. Open Existing Project fails in the same way. The problem is reproducible 100% of the time with Reality Composer Pro 3 Beta 2, Beta 3, and Beta 4. I have also reproduced it: With a completely blank new project With an existing project In a clean local macOS user account In Safe Mode With no external displays With local paths and iCloud disabled After verifying adequate free disk space and se

Hi all! I have an issue how to handle depending data with live changes via .onReceive action. To show my issue I made a simple example with decimal/hex calculation in Swift Playground on macOS 26: import SwiftUI import Combine @Observable class AppData { @Published var baseValue : Int = 0 var intValue: String { get { String(baseValue) } set { guard let v = Int(newValue) else { fatalError(Can't set int!)} baseValue = v } } var hexValue : String { get { String(baseValue, radix: 16).uppercased() } set { guard let v = Int(newValue, radix: 16) else { fatalError(Can't set hex!)} baseValue = v } } } struct ContentView: View { @State var model = AppData() var body: some View { VStack { HStack { Text(Decimal Value) TextField(Decimal Value, text: $model.intValue) .textFieldStyle(.roundedBorder) .onReceive(Just(model.intValue)) { newValue in let allowedCharacters = 0123456789 let filtered = newValue.filter { allowedCharacters.contains($0) } if let v = Int(filtered) { model.baseValue = v } else { fatalError(Eeek

I am thinking about making an app that lets you experiment and prototype SwiftUI views in iOS. I was wondering if allowing user to have limited state/storage and functionally, for example a toggle connected to an if else in a view, would be allowed or disallowed by guideline 2.5.2. The app would probably use JavaScript in the background to simulate swift execution, but may use something else.

import Playgrounds import FoundationModels #Playground { do { let session = LanguageModelSession() let response = try await session.respond( to: Explain SwiftUI in one sentence. ) print(response.content) } catch { print(Error: (error)) } }``` I tested Foundation Models with this simple code, and it generated this error: Error Domain=ModelManagerServices.ModelManagerError Code=1026 (null) UserInfo={NSMultipleUnderlyingErrorsKey=(n)} I tried restarting my Mac and Apple Intelligence, but that didn't work. What did work was updating Xcode and the simulators to the latest possible version.

Environment Platform: iOS iOS versions tested: : 26.5.2, 26.5 Xcode: 26.3 Language: Swift UI framework: SwiftUI App distribution: App Store Device models tested: : iPhone 17, iPhone 16, iPhone 15 pro max, iPhone 17 pro max Issue We are experiencing an issue where the app icon does not update to the latest app icon after an app update on some devices. Initially, our app used Apple's alternate app icon functionality through setAlternateIconName to dynamically change the app icon. However, we observed that the alternate icon was not being updated correctly on some devices. As it was not working , we removed the alternate icon approach and changed the primary/default app icon in the application itself. We then submitted an updated app version with the new default icon. After updating the app, the new app icon is displayed correctly on some devices, but on some other devices the previous/old app icon continues to be displayed, even though the app has been successfully updated to the latest version. The is

Circling back on the LocalLM Lab arc. With v0.7, we've moved from prompt experimentation into real app development on Apple's Foundation Models local AI. The LocalLM Lab SDK lets you build that same on-device model and MCP client this thread has covered directly into your own app, with real tool and data access (Slack, Todoist, GitHub, Notion, Linear, plus Calendar, Reminders, Contacts and Location). And you can ship your app including through the Mac App Store. This is a big improvement over version 0.6, where the localai-cli toolkit needed LocalLM Lab installed and running. On the other hand, the SDK (LocalLMLabSDKCore) doesn't relay through anything; it links FoundationModels and a real MCP client directly into your own binary and is totally self-contained. The example included in the SDK, Plate Today, has actually been built into a sandboxed test app and verified working, with a signed path to a Mac App Store .pkg (Apple Distribution signing + provisioning profile pipeline). That's verified signable and s