Hi everyone, I’ve run into a strange issue while building my app with Xcode 26 beta 6 (targeting iOS 26). When I include an app icon created using Icon Composer, the build time jumps to over 5 minutes. During this time, I noticed that a utility called AssetCatalogSimulatorAgent is consuming a significant amount of CPU. If I remove the Icon Composer-generated icon from my target, the build completes in about 40 seconds. This behavior is consistent across multiple builds. Has anyone else experienced this? Is there a known workaround or optimization for icons created with Icon Composer? I’d love to keep using the new icon format, but the build time is becoming a real bottleneck. Thanks in advance!
Search results for
Swift 6
49,193 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I am trying to add webhook subscriptions for TestFlight build processing completion and TestFlight beta build review completion events. These were showcased in the WWDC25 session: https://developer.apple.com/videos/play/wwdc2025/324/ Currently, I am able to receive webhook events for distribution updates, and the corresponding checkmark option is available in the App Store Connect portal. However, there is no checkmark option in the portal to subscribe to beta build-related events. In the video, there is clearly a checkmark option for the beta review event subscription (at 4:55). The current documentation also does not mention beta processing and beta review event subscriptions. It only lists the event types that are visible in the web portal: https://developer.apple.com/documentation/appstoreconnectapi/webhookeventtype When I try to add the BUILD_BETA_DETAIL_EXTERNAL_BETA_STATE_UPDATED event (as shown in the video at 6:10) via the PATCH API request, I get the below error. errors: [ { id: ****-****-*
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect API
Tags:
Developer Tools
App Store Connect
App Store Connect API
I've been wondering what is the memory limit for network extensions. Specifically, I'm using the NEPacketTunnelProvider extension point.The various posts on this forum mention 5 MB and 6 MB for 32-bit and 64-bit respectively. However I find that (at least on iOS 10) the upper limit seems to be 15 MB. Is this the new memory limit for extensions?
I had no trouble replacing the View menu with code similar to the following: override func buildMenu(with builder: any UIMenuBuilder) { super.buildMenu(with: builder) if builder.system == .main { let cmd = UIKeyCommand(title: Hello, image:nil, action:#selector(doStuff), input: 1, modifierFlags: .command) let menu = UIMenu(image: nil, options: .displayInline, children: [cmd]) if let view = builder.menu(for: .view) { let newView = view.replacingChildren([menu]) builder.replace(menu: .view, with: newView) } } } With that code the View menu only shows the one menu item I created. Tested with Xcode 26 beta 7 running on a simulated iPad running iPadOS 26 beta 6.
Topic:
UI Frameworks
SubTopic:
UIKit
I had been too swamped to be able to continue this conversation because of the highly prioritized work related to WWDC25, and after that I lost the track of this thread. Sorry for that. Thanks to another developer reaching out via DTS with the same issue, I am now picking up this thread, which hopefully is not too late. I'd like to confirm that I can now reproduce the issue. As folks have mentioned, the issue happens only in an Xcode project using folders, not groups. I've always used groups which helps me better organize files logically, and so had not seen the issue before. Xcode 26 Beta 6 doesn't fix the issue. Before the issue is fixed from the system side, the workarounds folks mentioned, like using groups instead or giving the new model version a name alphabetically ordered to the last, sound good to me. Best, —— Ziqiao Chen Worldwide Developer Relations.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Anytime I have 1 item, then add another, the app crashes with the following error: Swift/IntegerTypes.swift:8835: Fatal error: Double value cannot be converted to Int because it is either infinite or NaN I'm not working with Int values though, so I'm not sure why this is happening. It's also not point me towards any specific line. I've printed out all of the values being used for the chart and none of them are showing as infinite or NaN. The data being used is created in a View. @State private var pieChartData: [PieChartDataPoint] = [] Then in the onAppear and onChange its gets loaded using the following function: func getPieChartDataPoints() -> [PieChartDataPoint] { self.map({ PieChartDataPoint(label: $0.name, value: $0.monthlyAmount()) }) } That's an extension on a SwiftData model type I have called Recurring. @Model final class Recurring { var id = UUID() enum Kind: String, CaseIterable, Codable { case income = Income case bill = Bill func plural() -> String { switch self { case .income: Inc
We are developing a cross platform c++ application. We also use some objective-c (no swift) and specific Apple frameworks like AVFoundation, CoreML in the MacOs version of our software. We use Apple Clang as compiler when building for MacOs. As our code is primarily c++ we would like to use the latest and greatest c++ 20 features. So we are looking into using vanilla clang instead, the builds with vanilla clang seem to work fine, however our concern is that we might have overlooked possible issues that could arise. So our question is whether there are specific things we need to address when switching compilers, are there things that we need to be aware of? In the end we just want to know if switching compilers won't cause problems we can't oversee. So we would like to know if others took the same steps and what your thoughts/experiences are regarding this?
Topic:
Developer Tools & Services
SubTopic:
General
I created a Radar for this FB14766095, but thought I would add it here for extra visibility, or if anyone else had any thoughts on the issue. Basic Information Please provide a descriptive title for your feedback: iOS 18 hit testing functionality differs from iOS 17 What type of feedback are you reporting? Incorrect/Unexpected Behavior Description: Please describe the issue and what steps we can take to reproduce it: We have an issue in iOS 18 Beta 6 where hit testing functionality differs from the expected functionality in iOS 17.5.1 and previous versions of iOS. iOS 17: When a sheet is presented, the hit-testing logic considers subviews of the root view, meaning the rootView itself is rarely the hit view. iOS 18: When a sheet is presented, the hit-testing logic changes, sometimes considering the rootView itself as the hit view. Code: import SwiftUI struct ContentView: View { @State var isPresentingView: Bool = false var body: some View { VStack { Text(View One) Button { isPresentingView.toggle() }
No. Inline works fine. Building on iOS 18.4, Xcode 16.3, Swift 6
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
Your crash report is only partially symbolicated. To be completely clear what happened in your app, you might consider fully symbolicating your report. The details of how to do so is covered in this article. Having said that, your crash report indicates that the main thread (thread 0) was blocked when SwiftUI initialized a tab view (frame 8). Your app got involved into the process (frame 4, 5), and eventually ran into _dispatch_once_wait (frame 3) and __ulock_wait (frame 0): Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 libsystem_kernel.dylib 0x1df207f70 __ulock_wait + 8 1 libdispatch.dylib 0x196334c3c _dlock_wait + 56 2 libdispatch.dylib 0x196367408 _dispatch_once_wait.cold.1 + 148 3 libdispatch.dylib 0x196334b98 _dispatch_once_wait + 60 4 MyApp 0x10047b7d4 0x100360000 + 1161172 5 MyApp 0x100563524 0x100360000 + 2110756 6 SwiftUI 0x19369cbd4 Tab<>.init<>(_:systemImage:value:content:) + 300 7 MyApp 0x1005628a8 0x100360000 + 2107560 8 SwiftUI 0x1931b5780 TabView.
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
We are currently using Swift to develop our Apple application, and we are considering switching to a cross-platform solution as part of our technical evaluation. Recently, React Native (RN) has been revitalized, and it supports application hot updates, allowing us to update the app without going through the app store release process. Additionally, we have conducted some market research and found that many apps are using RN and leveraging its hot update functionality for app updates. I would like to know whether RN's hot update feature is compliant with Apple's policies and if there is any risk of the app being removed from the App Store. I hope to receive some guidance on this matter. Please do not delete this post—this is just a help-seeking post from an iOS developer without any malicious intent.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Hello there! I’m currently stuck with Xcode 26.0 beta 6 (17A5305f), as I can’t download the latest SDK/Simulator for iOS 26.0 beta 6 (23A5324a). The download constantly fails for days now with the following error message: (-67061 invalid signature (code or signature have been modified) Domain: SimDiskImageErrorDomain Code: 5 User Info: { DVTErrorCreationDateKey = 2025-08-26 21:11:30 +0000; unusableErrorDetail = ; } -- (-67061 invalid signature (code or signature have been modified) Domain: SimDiskImageErrorDomain Code: 5 User Info: { unusableErrorDetail = ; } -- System Information macOS Version 15.6.1 (Build 24G90) Xcode 26.0 (24208.7) (Build 17A5305f) Timestamp: 2025-08-26T23:11:30+02:00 I’ve already tried re-downloading the Xcode beta 6 from the Apple Developer site. I’ve also tried restarting my Mac and even tried to use the command line to install iOS 26 beta SDK via xcodebuild -downloadPlatform iOS -exportPath ~/Downloads (as noted here). This lead to the same error message. Ca
Yes, we see a lot of crashes like this in our apps, too. But we can't reproduce it. OS Version: iPhone OS 18.6 (22G86) Release Type: User Baseband Version: 2.70.02 Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Reason: *** -[__NSSingleObjectArrayI objectAtIndex:]: index 2 beyond bounds [0 .. 0] Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: OurAppName [72412] Triggered by Thread: 0 Last Exception Backtrace: 0 CoreFoundation 0x1950500c0 __exceptionPreprocess + 164 (NSException.m:249) 1 libobjc.A.dylib 0x1924e9abc objc_exception_throw + 88 (objc-exception.mm:356) 2 CoreFoundation 0x1950418c8 -[__NSSingleObjectArrayI objectAtIndex:] + 308 (NSSingleObjectArray.m:18) 3 PrintKitUI 0x1f34d4518 -[UIPrintPaperSizeOption listItemSelected:] + 88 (UIPrintMoreOptions.m:896) 4 PrintKitUI 0x1f34a0a0c -[UIPrintOptionListViewController tableView:didSelectRowAtIndexPath:] + 116 (UIPrintOptionCells.m:103) 5 UIKitCore 0x
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
I am also encountering the same issue. None of the alarms scheduled are firing. The alarm I scheduled for 6:00 AM was fired at 6:45
Topic:
App & System Services
SubTopic:
General
FYI: I tested this using the new releases published this week, and this issue still exists. Specifically, I observed the issue when: Developing in Xcode beta 7 (17A5305k) running iOS 26 SDK beta 6 (23A5324a) in the simulator Running the sample code above on a physical iPhone running iOS 26 beta 8 (23A5330a)
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags: