Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for

Hello! I'm currently working on Liquid Glass support for my app. I understand that starting with iOS 26, standard buttons like Close or Done have shifted from text buttons to using SF Symbols, as mentioned in the Human Interface Guidelines under Icons. However, on iOS 18 and earlier, the flat text button style remains the standard. I am unsure about the best approach for backward compatibility: Branch by OS version: Keep text buttons for older OS versions and use SF Symbols for iOS 26+. Concern: This increases the number of conditional branches, potentially reducing code readability and maintainability. Adopt SF Symbols universally: Use SF Symbols for all versions. Concern: I feel that SF Symbols do not fit well (look inconsistent or out of place) with the flat design language of iOS 18 and earlier. What would be the recommended approach in this situation?

I’m experiencing a consistent crash of SpringBoard on macOS when running my iOS app in the Simulator. The crash occurs specifically when a critical alert (geofence notification) is triggered by my server and delivered to the app. Xcode version: 16.4 macOS version: 15.5 App uses UNUserNotificationCenter with critical alert notifications related to geofencing. When the critical alert is received, SpringBoard quits unexpectedly on macOS, crashing the Simulator UI to the home screen. The notification is delivered by Firebase, and I have updated to the latest version of that. The console shows: XPC connection interrupted [C:1] Error received: Connection interrupted. [C:1-2] Error received: Connection interrupted. This does not happen when testing on a real device — the app works fine there, however, Springbaord still crashes on macOS. Please advise if this is a known issue or if there’s a workaround. This severely impacts development and testing of location-based critical notifications.

Hello everyone, I’m reaching out from the music publishing side and would appreciate guidance from developers or anyone familiar with TestFlight governance. We’ve identified an app that has been distributed via TestFlight for an extended period (regular renewals, updates, and new TestFlight builds). The app’s core functionality involves publishing copyrighted musical works (sheet music), without authorization from the authors or rightsholders. We have attempted to contact the developer using the contact details available through the TestFlight listing and associated project information. To date, we have received no response, and the TestFlight distribution continues. From our perspective, the developer appears to rely on TestFlight to keep the app off the App Store, where standard copyright enforcement mechanisms would normally apply. My questions are: Does Apple consider long-term, continuously renewed TestFlight distribution to be a form of public distribution? Is there a mechanism within the Apple

I've been experiencing complete TestFlight system failure for 6 days across ALL testing modes with 4 open support cases and zero technical resolution: Support Cases: • 102814191861 (submitted Jan 29) • 102814822980 (submitted Jan 30) • 102814123468 (phone call Feb 3) • 102818476151 (latest update Feb 3) ISSUE DETAILS: App: كيم تحصيلي (ChemTahsili) Bundle ID: com.chemTahsiliApp Build: 1.0.5 (34) SYMPTOMS: ✗ Internal Testing: Users receive The requested app is not available or does not exist ✗ External Testing: System shows Validation Error - Check your entries and try again ✓ Build Status: Shows Valid in App Store Connect ✓ App Status: Waiting for Review ✓ All Agreements: Active (Free Apps, Paid Apps, Banking, Tax Forms) ✓ Account Status: Good standing EVIDENCE THIS IS APPLE'S INFRASTRUCTURE ISSUE: Same build fails in BOTH Internal AND External TestFlight Build is marked Valid and approved for testing All developer configurations verified correct Issue persists across 6 days

Hi all, I’m running into a “double update” effect in SwiftUI when using the @Observable with @State. I’m trying to understand whether this is expected behavior, a misuse on my side, or a potential bug. Setup I have an observable store using the Observation macro: @Observable class AlbumStore { var albums: [Album] = [ Album(id: 1, title: Album 1, author: user1), Album(id: 2, title: Album 2, author: user1), Album(id: 3, title: Album 3, author: user1), Album(id: 4, title: Album 4, author: user1), Album(id: 5, title: Album 5, author: user1), Album(id: 6, title: Album 6, author: user1) ] func addAlbum(_ album: Album) { albums.insert(album, at: 0) } func removeAlbum(_ album: Album) { albums.removeAll(where: { $0 == album }) } } In my view, I inject it via @Environment and also keep some local state: @Environment(AlbumStore.self) var albumStore @State private var albumToAdd: Album? I derive a computed array that depends on both the environment store and local state: private var filteredAlbums: [Album] { let albums =