“DTiPhoneSimulatorErrorDomain Code 2”

I'm trying to publish two frameworks I wrote in Swift on GitHub. https://github.com/nickasd/BoardGameKit https://github.com/nickasd/BoardGameKitHost I want to add the first framework as a dependency to one of my Xcode projects. I click on the + button in the Package Dependencies tab, select BoardGameKit and click Add Package. A sheet opens and after a couple seconds, while the sheet is still open, Xcode crashes. When I try the same steps with the second framework, Xcode survives and finally shows me a confirmation sheet, and clicking on Add Package works as expected. Both repositories look exactly the same to me, except for their name of course. I even force pushed the default, empty Swift package created in Xcode with the Framework template to both repositories, and still only the first one makes Xcode crash, even after deleting all DerivedData folders and restarting Xcode. What could be the issue? I created FB22832333.

Hello everyone, I’m experiencing a WeatherKit issue that occurs consistently on both the iOS 26.2 Simulator and a real device running iOS 26.2. Environment: Xcode: latest iOS: 26.2 Occurs on: Simulator AND physical device WeatherKit usage: via WeatherService API (not manual REST) Location Services: authorized (When In Use / Always) Issue: WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2 The operation couldn’t be completed. Already verified: WeatherKit capability is enabled for the App ID com.apple.developer.weatherkit entitlement is present Bundle ID matches the App ID App is signed with the correct Team ID Behavior is identical on Simulator and physical device Error occurs before any WeatherKit response is returned Questions: Is this a known issue with WeatherKit on iOS 26.2? Are there any known limitations or requirements for WeatherService related to WeatherDaemon validation? Is there a recommended way to diagnose why WeatherDaemon rejects the request with Code=2

I enabled the WeatherKit capability on my App ID (com.saimcan.darkweather, Team 6SWSD6V4ZC) about 12 hours ago. The entitlement is embedded in the binary and the provisioning profile authorizes it, but every request fails at the JWT generation step. Error from the logs: Error Domain=WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2 (null) Relevant log excerpt (iOS 26.4 Simulator, same result on a physical device): [AuthService] Calling process is 3rd party process and has the correct entitlement ... accepting the connection [AuthService] Received proxy request for generating a jwt token. url=https://weatherkit.apple.com [WeatherDataService] Starting to generate JWT token request. bundleIdentifier=com.saimcan.darkweather [AuthService] Signed successfully [WeatherDataService] Make new JWT token request. requestIdentifier=... [AuthService] Failed to generate jwt token ... Code=2 What I have verified: Active Apple Developer Program membership (renewed through April

Description I've encountered a consistent hang/freeze issue in SwiftUI applications when using nested LazyVStack containers with Accessibility Inspector (simulator) or VoiceOver (physical device) enabled. The application becomes completely unresponsive and must be force-quit. Importantly, this hang occurs in a minimal SwiftUI project with no third-party dependencies, suggesting this is a framework-level issue with the interaction between SwiftUI's lazy view lifecycle and the accessibility system. Reproduction Steps I've created a minimal reproduction project available here: https://github.com/pendo-io/SwiftUI_Hang_Reproduction To Reproduce: Create a SwiftUI view with the following nested LazyVStack structure: struct NestedLazyVStackView: View { @State private var outerSections: [Int] = [] @State private var innerRows: [Int: [Int]] = [:] var body: some View { ScrollView { LazyVStack(alignment: .leading, spacing: 24) { ForEach(outerSections, id: .self) { section in VStack(alignment: .leading, spacing: 8) { Text

On iOS 26 with Full Keyboard Access enabled, a UITableView(style: .grouped) with custom cells only enumerates section 0 in the Ctrl+Tab focus order (But it works with arrow keys). Cells in sections 1+ are reachable via arrow keys, and canFocusRowAt fires and returns true when arrows spatially reach them — but Tab leaves the table after the last row of section 0 and jumps to the next focus item outside the table. Same code works correctly on iOS 18.x. focusGroupIdentifier strategies (single ID on the table, same ID across view/table/every cell, unique ID per cell) have no effect. tableView.allowsFocus is true. Is this a known iOS 26? Has anyone else run into this? final class CardCell: UITableViewCell { private let cardView = UIView() override init(style: CellStyle, reuseIdentifier: String?) { super.init(style: style, reuseIdentifier: reuseIdentifier) cardView.backgroundColor = .white cardView.translatesAutoresizingMaskIntoConstraints = false contentView.addSubview(cardView) NSLayoutConstraint.activat

Hi, I'm trying to run our StoreKit unit tests with Xcode26.5 on an iOS26.5 simulator. Host computer has macOS26.5. All tests are failing and in the console I see logs such as [SKTestSession] Error saving configuration file: Error Domain=SKInternalErrorDomain Code=3 (null) [SKTestSession] Error deleting all transactions: Error Domain=SKInternalErrorDomain Code=3 (null) [SKTestSession] Error clearing overrides: Error Domain=SKInternalErrorDomain Code=3 (null) [SKTestSession] Error setting value to 1 for identifier 2 for jp.unext.mediaplayer: Error Domain=SKInternalErrorDomain Code=3 (null) And the simulator asks me to provide my AppleID. Tests have been broken since at least 26.4 The release notes claims that it has been fixed but not for me. https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-26_5-release-notes#StoreKit-Testing-in-Xcode Does anyone else have the same issue? Reported FB22774836 just in case.

Hi all, Has anyone else been getting stuck with the iOS Developer Program enrolment? I've been stalled for nearly two months, and is directly preventing us from releasing app updates to our users. Issue Summary: Our enrolment has been stuck at the status Your enrolment is being processed for approximately two months We have submitted the required details multiple times with no resolution The contact form for email and phone support returns the error: there was a problem processing your request Phone numbers listed for developer support in Ireland are either non-functional or connect to sales support only We contacted contactus.ie at euro.apple.com, were again directed to sales support, and were told the matter would be escalated internally — this was nearly a month ago and we have received no further communication. It's very frustrating as our dev team has deployed two Android updates since. It's really impacting our products and I need to get this resolved asap. It's crazy that onc

Hi all, Has anyone else been getting stuck with the iOS Developer Program enrolment? I've been stalled for nearly two months, and is directly preventing us from releasing app updates to our users. Issue Summary: Our enrolment has been stuck at the status Your enrolment is being processed for approximately two months We have submitted the required details multiple times with no resolution The contact form for email and phone support returns the error: there was a problem processing your request Phone numbers listed for developer support in Ireland are either non-functional or connect to sales support only We contacted contactus.ie at euro.apple.com, were again directed to sales support, and were told the matter would be escalated internally — this was nearly a month ago and we have received no further communication. It's very frustrating as our dev team has deployed two Android updates since. It's really impacting our products and I need to get this resolved asap. It's crazy that onc

Hi Team, We are observing a noticeable performance difference in client-side PDF generation between Safari and Chrome. Use Case We have an AI modal with a “Download PDF” feature. The PDF is generated on the client side using HTML content from the modal. Observation Chrome: PDF generation completes in ~1–2 seconds Safari: Same flow takes ~25–30 seconds Additional Details The functionality works correctly in both browsers, and the PDF downloads successfully. The issue is mainly the increased processing time in Safari. The modal content may include: Large formatted text Markdown/code blocks Images/styled UI We suspect the delay may be related to Safari’s handling of: Canvas rendering DOM-to-image conversion Blob/PDF generation Font/image processing Libraries/approaches involved: html2canvas jsPDF window.print() (in some cases) Question Is this considered expected behavior in Safari/WebKit for client-side PDF generation? Has anyone found effective Safari-specific optimizations or best practices