Posts under Developer Tools & Services topic

Post

Replies

Boosts

Views

Activity

WWDC24 - Xcode 16 + macOS 15 Beta 1 - Unable to Download Predictive Code Completion Model
Hi Excited to try out the new Xcode Swift code completion ML tools demo'd yesterday at the SOTU. I am running macOS 14.5, using a VM Via Virtualization Framework ( UTM.app) to run macOS 15 Beta 1. Ive installed XCode 16 Beta 1 in my Host OS (macOS 14.5) and was able to successfully install, boot, and set up macOS 15 as a VM client. Ive installed Xcode 16 in my VM Client, and upon launch, was asked to download the Predictive Text model. I see this error: The operation couldn’t be completed. (ModelCatalog.CatalogErrors.AssetErrors error 1.) Domain: ModelCatalog.CatalogErrors.AssetErrors Code: 1 User Info: { DVTErrorCreationDateKey = "2024-06-11 20:11:32 +0000"; } -- Failed to find asset: com.apple.fm.code.generate_small_v1.tokenizer - no asset Domain: ModelCatalog.CatalogErrors.AssetErrors Code: 1 -- System Information macOS Version 15.0 (Build 24A5264n) Xcode 16.0 (23037.4) (Build 16A5171c) Timestamp: 2024-06-11T13:11:32-07:00
10
5
4.2k
Sep ’24
Playground stuck on "Ready to Contine", not executing code
Since updating to Sequoia & Xcode 16, I cannot run any code in a playground. Even the simplest code - import Cocoa print("Hello, world") does not run and hangs on "Ready to Continue MyPlaground". I've tried restarting, force quitting, deleting and reinstalling Xcode, killing 'com.apple.CoreSimulator.CoreSimulatorService' in the activity monitor.
3
0
905
Sep ’24
Upgraded to Sequoia & Xcode 16.0, now build doesn't work
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.0.sdk/usr/include/c++/v1/__format/formatter_floating_point.h:66:30: error: 'to_chars' is unavailable: introduced in macOS 13.3 66 | to_chars_result __r = std::to_chars(__first, __last, __value, __fmt); Which, ok, I can accept that this is true. Except that this worked on Friday, on the same machine running Sonoma and the previous version of Xcode. The project is configured for a deployment target of 12.0, so it should have failed before, but didn't. (This is a CMake-generated xcodeproj, but that also should not have been any change.)
3
1
918
Sep ’24
Failed to download iOS 16.1 simulator runtime
My workflow has been running tests on iOS 15, 16 and 17 for a long time now, but suddenly it started to fail for iOS 15 and 16. The error does not seem to be code related, since it is a Xcode Cloud failure saying: "Failed to download iOS 16.1 simulator runtime". The exact same issue is showing for iOS 15. It works as expected on iOS 17. I have also reported this in the Feedback Assistant: FB14855036 If someone knows a work-around for this issue, I'd be happy to hear about it!
3
2
880
Sep ’24
Upload Symbols Failed on XCode 16
I recently upgraded to MacOS Sequioa 15.0 and had to update to Xcode 16 as a result. I am using iOSAppSDK.framework and now when I want to archive and distribute an app to TestFlight I get this warning... The archive did not include a dSYM for the iOSAppSDK.framework with the UUIDs[...]. Ensure that the archive's dSYM folder includes a DWARF file for iOSAppSDK.framework with the expected UUIDs. Everything worked fine before the update. Even though it seems that the app is deployed correctly, at least from the Developer web site, the version is not actually updated. Can you help me fix this?
1
2
8.4k
Sep ’24
"Command SwiftCompile failed with a nonzero exit code" error by [Product] - [Archive]
The app in question was recently distributed on September 4,2024. This time, there have been some minor improvements. To test new version on my iPhone, compiling is done completely. But when I archive it for distribution, I get the following error. While running pass #985712 SILFunctionTransform "DeadArgSignatureOpt" on SILFunction "@$s15Petty_treasurer12PhotosViewerC8onReturnyyF". for 'onReturn()' (at /Users/ymdakr/MyAppli/Petty_accountant/Petty_accountant/PhotosViewer.swift:173:11) Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var LLVM_SYMBOLIZER_PATH to point to it): 0 swift-frontend 0x0000000107a5b0fc llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 56 1 swift-frontend 0x0000000107a59350 llvm::sys::RunSignalHandlers() + 112 2 swift-frontend 0x0000000107a5b6c8 SignalHandler(int) + 292 3 libsystem_platform.dylib 0x000000018deae584 _sigtramp + 56 4 swift-frontend 0x0000000103cb3c54 swift::AbstractFunctionDecl::isDistributedTargetInvocationResultHandlerOnReturn() const + 356 5 swift-frontend 0x0000000103cb3c54 swift::AbstractFunctionDecl::isDistributedTargetInvocationResultHandlerOnReturn() const + 356 6 swift-frontend 0x000000010305cc74 canSpecializeFunction(swift::SILFunction*, swift::CallerAnalysis::FunctionInfo const*, bool) + 444 7 swift-frontend 0x000000010305c2e4 (anonymous namespace)::FunctionSignatureOpts::run() + 212 8 swift-frontend 0x0000000103247554 swift::SILPassManager::runFunctionPasses(unsigned int, unsigned int) + 3448 9 swift-frontend 0x0000000103240d74 swift::SILPassManager::executePassPipelinePlan(swift::SILPassPipelinePlan const&) + 252 10 swift-frontend 0x000000010327d084 swift::SimpleRequest (swift::SILPipelineExecutionDescriptor), (swift::RequestFlags)1>::evaluateRequest(swift::ExecuteSILPipelineRequest const&, swift::Evaluator&) + 56 11 swift-frontend 0x00000001032609e8 swift::ExecuteSILPipelineRequest::OutputType swift::Evaluator::getResultUncached(swift::Evaluator&, swift::ExecuteSILPipelineRequest)::'lambda'()>(swift::ExecuteSILPipelineRequest const&, swift::ExecuteSILPipelineRequest::OutputType swift::evaluateOrFatal(swift::Evaluator&, swift::ExecuteSILPipelineRequest)::'lambda'()) + 412 12 swift-frontend 0x00000001032636c4 swift::runSILOptimizationPasses(swift::SILModule&) + 440 13 swift-frontend 0x00000001027db3f8 swift::CompilerInstance::performSILProcessing(swift::SILModule*) + 1160 14 swift-frontend 0x0000000102405d68 performCompileStepsPostSILGen(swift::CompilerInstance&, std::__1::unique_ptr>, llvm::PointerUnion, swift::PrimarySpecificPaths const&, int&, swift::FrontendObserver*) + 1376 15 swift-frontend 0x00000001024056e4 swift::performCompileStepsPostSema(swift::CompilerInstance&, int&, swift::FrontendObserver*) + 2888 16 swift-frontend 0x0000000102408228 performCompile(swift::CompilerInstance&, int&, swift::FrontendObserver*) + 1680 17 swift-frontend 0x0000000102406f58 swift::performFrontend(llvm::ArrayRef, char const*, void*, swift::FrontendObserver*) + 3572 18 swift-frontend 0x000000010238e01c swift::mainEntry(int, char const**) + 3680 19 dyld 0x000000018daf3154 start + 2476 Command SwiftCompile failed with a nonzero exit code Previously distributed version is also giving the same error. Development environment: Xcode 16, macOS Sonoma 14.6.1 Run-time configuration: iOS 18
4
0
611
Sep ’24
[iOS 18 DB7] Unable to trust certificates
I bought a new iPhone 16, iOS18 (22A3354). Data is synced from the old device. The old device has a certificate under Settings - General - "VPN & Device Management". The iPhone16 device is not synced to the certificate. After I manually added it on my iPhone16, I didn't find the certificate in Settings - General - About - certificate trust settings. I tried restarting and reimporting, it still doesn't work. Erase the iPhone and re-import the certificate, which is successfully trusted. I tried another iPhone 15 device, upgraded to iOS18. After the certificate is imported, the certificate is successfully trusted. The problem seems to be related to data synchronization to iOS18 devices. Is this just a bug? Is there any solution?
3
6
1.2k
Sep ’24
Xcode 16 RC validate build bitcode error
I just swapped over to Xcode 16 and archived my build. I have ENABLE_BITCODE = NO in my Build settings (it's listed under user defined settings). When I go to validate the build, I get a failure "Invalid Executable, ***.framework contains bitcode". Nothing about my project settings has changed. If i swap back to Xcode 15 everything's fine when I validate. One thing I noticed though is that if I go through the process of validating, on the confirmation screen for Xcode 16 RC, the line about Bitcode: Not included does not exist like it does if I hit the confirmation screen in Xcode 15.
9
6
18k
Sep ’24
ASWebAuthenticationSession issue on iOS 18 simulator
We have some third-party SDKs do not support arm64 simulator, so we excluded arm64 for Any iOS Simulator SDK in Excluded Architectures. But in this case, ASWebAuthenticationSession will display abnormally. We submitted FB14853757 during the beta period, but have not received any response. This issue still exists in the official version. I hope it can be resolved. Thank you!
9
8
2.1k
Sep ’24
Package.resolved discrepency
We are using a workspace file and have noticed that when we run fastlane commands that utilize xcodebuild command line arguments to run the export localization command from commandline, and it seems that it uses the xcodeproj package.resolved instead of the workspace package.resolved. This is causing issues as the xcodeproj package resolved will not update at all so is on old version of dependencies that cause xcodebuild commands to fail. Why is there multiple package.resolved files and why does the xcodeproj not stay updated with what is in the workspace resolved file? Why won't the xcodeproj resolved file update when I'm opening the xcodeproj file and selecting specific dependencies and telling it to update the package.
0
0
361
Sep ’24
When AppEnum or AppEntity is introduced into the iOS18 Widget file, xcode compilation will report an error: Error collecting extracted types: The file “SmartPlusWidgetControl.swift” couldn’t be opened because the text encoding of its contents can’t b
When AppEnum or AppEntity is introduced into the iOS18 Widget file, xcode compilation will report an error: Error collecting extracted types: The file “SmartPlusWidgetControl.swift” couldn’t be opened because the text encoding of its contents can’t be determined.
0
0
199
Sep ’24
The requested device could not be found because multiple devices matched the request.
I'm facing this issue intermittently since using Xcode 16 beta 4 on macOS 14.5 when starting xcodebuild build with -destination option. 20:56:07 ▸ xcodebuild: error: Unable to find a device matching the provided destination specifier: 20:56:07 ▸ { platform:iOS Simulator, OS:15.4, name:iPhone 13 Pro } 20:56:07 ▸ The requested device could not be found because multiple devices matched the request. ( 20:56:07 ▸ "<DVTiPhoneSimulator: 0x151fb1fe0> {\n\t\tSimDevice: iPhone 13 Pro (CB36E92A-C32D-481C-A407-28123ABEBF66, iOS 15.4, Shutdown)\n}", 20:56:07 ▸ "<DVTiPhoneSimulator: 0x151fb4070> {\n\t\tSimDevice: iPhone 13 Pro (0EBBCB9A-5FBA-4998-903B-1415315D1533, iOS 15.4, Shutdown)\n}" 20:56:07 ▸ ) This mac is mac mini 2023 M2 Pro 32GB memory, running with multiple simruntimes installed: $ sudo xcrun simctl runtime list Password: == Disk Images == -- iOS -- iOS 17.5 (21F79) - 9FC1CFB3-33A4-4F31-AF40-BAB448F6FA0D (Ready) iOS 16.4 (20E247) - 3BFB66B1-075B-4B17-951C-B691BAC41C73 (Ready) iOS 17.2 (21C62) - C8D4111F-1F7A-4FC2-AC6A-BF68A47EEDCE (Ready) iOS 17.4 (21E213) - 0B8ECC25-EF76-4744-9D77-8256A57D1605 (Ready) iOS 18.0 (22A5326g) - 7217B9B2-A113-4B6B-915E-CAB70431B415 (Ready) iOS 17.0.1 (21A342) - C4FE430B-DD3F-4108-B2E7-B13A04989863 (Ready) iOS 15.4 (19E240) - CAB77B36-B6D3-4F5D-8956-E7A3105AC910 (Ready) iOS 18.1 (22B5023e) - 9E53F2C6-BA91-421C-848F-F78043179361 (Ready) -- tvOS -- tvOS 17.2 (21K364) - 8A9929AE-0521-498D-884A-F87BD16612CD (Ready) tvOS 16.4 (20L494) - 3354C9A4-E177-4030-98F2-0735970E1607 (Ready) tvOS 17.4 (21L224) - 724CD6DA-EAC2-4076-A578-C84872A36E5E (Ready) tvOS 15.2 (19K50) - 0AE51520-B1E2-4ED9-80A4-717291FC5E96 (Ready) tvOS 18.0 (22J5335e) - E839E471-AA01-46E1-A4AD-DF4B98B46525 (Ready) tvOS 17.5 (21L569) - C432547A-F7EF-4B34-AD43-D3E839CB49E1 (Ready) tvOS 17.0 (21J353) - 6A08D50B-D9BF-4496-A5C5-FE21373B11DD (Ready) tvOS 18.0 (22J5324f) - B2C7CA72-AAE6-4DF9-A4B0-26A0EB9462F7 (Ready) -- watchOS -- watchOS 11.0 (22R5318h) - 56250DF3-CF78-4C5D-B502-0B53DE16ABEB (Ready) watchOS 10.4 (21T214) - CC71D3D3-EA19-4F0B-BF3E-388D686AB300 (Ready) watchOS 10.0 (21R355) - 3623992D-88CF-41CB-8091-AF1F8CE16717 (Ready) watchOS 10.2 (21S364) - C0666241-AA31-4CF7-98B9-EA5394331DC6 (Ready) watchOS 9.4 (20T253) - EED82B11-589D-41AF-B290-844F59AECECB (Ready) watchOS 10.5 (21T575) - 0D749B4E-DC69-4F27-8982-510AB985B822 (Ready) watchOS 8.3 (19S51) - 8123ABC7-5465-4467-A5DA-CE9C50E1081D (Ready) watchOS 11.0 (22R5328f) - 648646A0-A370-48A4-881B-15B2422DE698 (Ready) -- xrOS -- xrOS 2.0 (22N5297g) - C2C8E4EE-3738-4706-823E-2B4138CE90BE (Ready) xrOS 1.0 (21N305) - 29EAB8D4-160D-4A3B-AB7C-7325D205AC4C (Ready) xrOS 2.0 (22N5286g) - 1F92EE9A-A5F9-45F7-8075-7FD7BC4EF81E (Ready) xrOS 1.1 (21O209) - DB15F0B2-C9E4-424D-9A50-8D6EDB131142 (Ready) xrOS 1.2 (21O5565d) - 83A26410-A8A8-41F6-A5A1-E0A7E24B8BA0 (Ready) I've never seen this kind of simulator missing error. Nor installing any duplicate runtime(s) on the same machine because it will show error message like 'unable to use this runtime' on xcrun simctl runtime list. Could anyone give me a tip of avoiding this kind of error?
3
0
1.2k
Sep ’24