Hello, I am testing the sample project provided here: Bringing advanced speech-to-text capabilities to your app. On both macOS 26.0 beta and iOS 26.0 beta, the app crashes immediately on launch with a dyld Symbol not found error related to FoundationModels.framework. It feels like this may be related to testing primarily on newer Apple Silicon devices, as I am seeing consistent crashes on an Intel MacBook and on an older iPhone device. I would appreciate any insight, confirmation, or guidance on whether this is a known limitation or if there is a workaround. Is it planned to be resolved soon? Environment macOS: Device: MacBook Pro (Intel) Processor: 2 GHz Quad-Core Intel Core i5 Graphics: Intel Iris Plus Graphics 1536 MB Memory: 16 GB 3733 MHz LPDDR4X OS: macOS Tahoe Version 26.0 Beta (25A5338b) iOS: Device: iPhone 11 Model Number: MHDD3HN/A OS: iOS 26.0 Xcode: Version: 26.0 beta 3 (17A5276g) Crash (macOS) Abort signal received. Excerpt from crash dump: dyld`__abort_with_payload: 0x7ff80e3ad4a0 <+
Search results for
xcode github
92,012 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
There are multiple report of crashes on URLConnectionLoader::loadWithWhatToDo. The crashed thread in the stack traces pointing to calls inside CFNetwork which seems to be internal library in iOS. The crash has happened quite a while already (but we cannot detect when the crash started to occur) and impacted multiple iOS versions recorded from iOS 15.4 to 18.4.1 that was recorded in Xcode crash report organizer so far. Unfortunately, we have no idea on how to reproduce it yet but the crash keeps on increasing and affect more on iOS 18 users (which makes sense because many people updated their iOS to the newer version) and we haven’t found any clue on what actually happened and how to fix it on the crash reports. What we understand is it seems to come from a network request that happened to trigger the crash but we need more information on what (condition) actually cause it and how to solve it. Hereby, I attach sample crash report for both iOS 15 and 18. I also have submitted a report (that include mor
If your goal is to join a Wi-Fi network, either temporarily or permanently [1], then the API you need is NEHotspotConfigurationManager. NEHotspotConfigurationManager is gated by a single entitlement: com.apple.developer.networking.HotspotConfiguration. In Xcode, that shows up as the Hotspot capability. So, try this: Create a new project from the iOS > App template. Build and run it on your device. In Signing & Capabilities, add the Hotspot capability. Build and run it again. Does that work? [1] Using the terms from TN3111 iOS Wi-Fi API overview. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Hi everyone, I'm having trouble with Network Extensions capability not being included in my provisioning profiles. Here's my setup: Environment: Xcode 16.0 iOS Deployment Target: 17.0 Paid Apple Developer Program ($99/year) Problem: I'm trying to use NEHotspotConfiguration in my app, but getting this error: entitlement What I've done: ✅ Enabled Network Extensions in App ID capabilities ✅ Enabled Access Wi-Fi Information and Hotspot ✅ Created new provisioning profiles after enabling capabilities ✅ Cleaned build folder and rebuilt ✅ Using Automatically manage signing in Xcode Current status: App ID shows all capabilities are enabled Xcode shows Network Extensions capability is present But provisioning profiles still don't include the entitlement NEHotspotConfiguration fails with entitlement error Questions: Has anyone else experienced this issue? Is there a specific way to force Xcode to include the entitlement? Should I try manual provisioning profile creation? Are there any
I haven’t yet watched that video [1] but, in general, I think it does make sense for your view models to be main-actor bound. However, you should keep in mind that there are two ways to achieve that in Xcode 26 beta: Apply @MainActor. Set the Default Actor Isolation build setting to MainActor. There are pros and cons to both approaches, but I suspect that a lot of folks will end up using the second approach for the main app and any libraries that are overwhelmingly UI-focused. I believe that Sima is using the second approach, based on my searching the transcript for the word default. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Summer has been particularly glorious this year, so I’ve spent my lunchtimes riding rather than watching WWDC videos (-:
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
I'm writing an iOS app that shares content with buddies. So my app will run in one language but the shared content will use the locale configured for the buddy. I found this Apple documentation which suggests that locale: (Locale(identifier: is the solution. Apple Documentation But I can't get it to work. Here's sample code. struct LocalizationDemoView: View { @State var isEnglish = true var body: some View { var myLocale: String { isEnglish ? en: de } VStack { Toggle(Switch language, isOn: $isEnglish).frame(maxWidth: 200) HStack { Text((myLocale): ) Text(String(localized: Hello world!, locale: (Locale(identifier: myLocale)), comment: To share)) } } } } And here's the excerpt from the string catalog: { sourceLanguage : en, strings : { Hello world! : { comment : To share, localizations : { de : { stringUnit : { state : translated, value : 🇩🇪 Moin Welt! } }, en : { stringUnit : { state : translated, value : 🇬🇧 Hello world! } } } } } } Has Apple reduced support for string catalogs or is my code wrong? Xcode
Hi All, We are developing our app with an approved External Link Account Entitlement. During the development process (such as installing from Xcode or creating an Ad-hoc build and installing it on a phone), the open() function of the External Link Account API displays the modal our native language. The app only localized to that language. However, after uploading the app with the same configuration to TestFlight, the modal somehow appears in English instead. What could be causing this issue with the External Link Account modal? How can the open() function display the modal in another language when installed from Xcode or an Ad-hoc release build, but in English when installed from TestFlight? How can we show only our native lanugage version only to our Users? Thank you in advance
Hi. I'm currently working on Xcode CI build uploading ipa to TestFlight. Building archive is successful but exportArchive is failed with error exportArchive Failed to Use Accounts. How can I fix this error?
MacOS14.0 Xcode15.1(已登录开发者账号) Build with Jenkins(fastlane) 1.刚登录开发者账号几个小时内,功能正常;而后使用Jenkins构建时会出现Your session has expired. Please log in. 2.如果我在出现错误后,手动打开以下Xcode,而后再进行Jenkins构建,则不会出现错误;(但如果之后关闭Xcode,过一段时间错误还会复现) + xcodebuild -exportArchive -exportOptionsPlist /var/folders/8x/c3qf2sz95jd40fk49d5dbg400000gn/T/gym_config20240119-38953-jl7k5y.plist -archivePath '/Users/smg_ios/Library/Developer/Xcode/Archives/2024-01-19/WinTaxProject 2024-01-19 13.45.59.xcarchive' -exportPath /var/folders/8x/c3qf2sz95jd40fk49d5dbg400000gn/T/gym_output20240119-38953-3u2rch -allowProvisioningUpdates 2024-01-19 13:47:15.691 xcodebuild[44905:206740] DVTPortal: Service '' encountered an unexpected result code from the portal ('1100') 2024-01-19 13:47:15.691 xcodebuild[44905:206740] DVTPortal: Error: Error Domain=DVTPortalServiceErrorDomain Code=1100 Your session has expired. Please log in. UserInfo={payload={ creationTimestamp = 2024-01-19T05:47:15Z; httpCode = 200; protocolVersion = QH65B2; requestUrl = htt
I had the same problem. It works on the real device, but fails systematically on simulator. I run Beta8 on macOS Tahoe and the latest Xcode beta. Error: guardrailViolation(FoundationModels.LanguageModelSession.GenerationError.Context(debugDescription: May contain sensitive or unsafe content, underlyingErrors: [Error Domain=com.apple.SensitiveContentAnalysisML Code=15 Failed model manager query for model com.apple.fm.language.instruct_300m.safety: Model Catalog error: Error Domain=com.apple.UnifiedAssetFramework Code=5000 There are no underlying assets (neither atomic instance nor asset roots) for consistency token for asset set com.apple.modelcatalog UserInfo={NSLocalizedFailureReason=There are no underlying assets (neither atomic instance nor asset roots) for consistency token for asset set com.apple.modelcatalog} UserInfo={NSLocalizedDescription=Failed model manager query for model com.apple.fm.language.instruct_300m.safety: Model Catalog error: Error Domain=com.apple.UnifiedAssetFramework Code=500
Topic:
Machine Learning & AI
SubTopic:
Foundation Models
Tags:
Just a quick reply -- I'll put together a sample project for the feedback report and have it for you tomorrow (Wednesday). I am using Xcode 16.4 running on macOS 15.7 working with a project where the Minimum Deployment Target is iOS 18.0 (I changed it from 17.0 to try using the .onScrollGeometryChange API). I see the problem (i.e., listHeight = 0 on both #Preview and on the Simulator (running the iPad mini (6th generation) 18.1 simulation. More tomorrow -- hopefully with a sample project and an FB#.
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
When I try to make a unit test target for my macOS app that uses Objective-C, running tests fails, and the debugging log shows a message Creating more than one Application. If, on the other hand, when I create the unit test target, I select None as the target to be tested, and then add all my sources to that target, my tests work. So, I can get my testing done, but I think I must be doing something wrong. By the way, along with the error message, there is a stack crawl: 0 CoreFoundation 0x00007ff8140410aa __exceptionPreprocess + 242 1 libobjc.A.dylib 0x00007ff813b660b7 objc_exception_throw + 48 2 Foundation 0x00007ff814f19bd8 -[NSCalendarDate initWithCoder:] + 0 3 AppKit 0x00007ff817030062 -[NSApplication init] + 1718 4 XCTestCore 0x000000010774b0df -[XCTestDriver _createTestBundlePrincipalClassInstance] + 82 5 XCTestCore 0x0000000107749338 -[XCTestDriver _runTests] + 111 6 XCTestCore 0x000000010770f194 _XCTestMain + 126 7 libXCTestBundleInject.dylib 0x0000000106e8982d __copy_helper_block_e8_32s + 0 8 CoreFou
Just tested with most recent Tahoe 26.0 Beta (25A5349a) and Xcode 26.0 beta 6 (17A5305f). Still get a Runningboard has returned error 5.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
I'm using Xcode 15.2 on macOS 13.7.7. A new app project does not reproduce the problem, but I'm not yet seeing the relevant difference. At first I thought it might be because I was using a nonstandard build location, but changing that back to the default didn't fix it. With a breakpoint on -[NSApplication init], the first break has this backtrace frame #0: 0x00007ff81702f9ac AppKit`-[NSApplication init] frame #1: 0x00007ff81702f78e AppKit`+[NSApplication sharedApplication] + 120 frame #2: 0x00007ff81702df79 AppKit`NSApplicationMain + 409 frame #3: 0x000000010e442a91 PlainCalc`main(argc=5, argv=0x00007ff7b1ae7e68) at main.m:14:9 frame #4: 0x00007ff813b93418 dyld`start + 1896 And the second is frame #0: 0x00007ff81702f9ac AppKit`-[NSApplication init] frame #1: 0x00000001103bd0df XCTestCore`-[XCTestDriver _createTestBundlePrincipalClassInstance] + 82 frame #2: 0x00000001103bb338 XCTestCore`-[XCTestDriver _runTests] + 111 frame #3: 0x0000000110381194 XCTestCore`_XCTestMain + 126 frame #4: 0x000000010fafb
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I archived the app via Xcode for App Store Connect. When I upload this build to iPhone via TestFlight everything works fine, but when I send it to Apple they get a black screen. Please tell me what the problem is
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
iOS
App Store Connect
Xcode
TestFlight