Using Xcode to build and deploy the app to my watch, this is what I get:
“Waiting to reconnect to Apple Watch. Previous preparation error: Transport error." And then “Connecting to Apple Watch. Xcode will continue when the operation completes.”
And these messages continue to switch between each other.
Sometimes the watch to connect and the application starts, but more often a scenario occurs with endless reconnection.
I'm using: MacOS 14.4.1 (MacBook Pro 2019; 1.4 GHz Quad-Core Intel Core i5), Xcode 15.3, Watch OS 10.2 (Apple Watch SE 1), iOS 17.1.1 (iPhone 15 Pro).
Methods I tried:
Connecting Macbook, iPhone and Watch to the same WIfi network;
Disabling Watch (and IPhone) from the "Devices and Simulators" menu and setting up Watch (and IPhone) from the beginning.
Any help?
Dive into the vast array of tools, services, and support available to developers.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
We have a Xcode project consisting of:
A mix of Swift and Objective-C code app code ~ 1600 source files.
Roughly around 35 {XC}Frameworks. Some of them are binary and some of them are getting built as a dependency to our app, etc.
Binary libraries.
Most of the frameworks built together with app code are Objective-C or Swift-based, which have their own amount of sources files and framework dependencies.
The binary frameworks mostly contain cross-platform C++ code.
Our (the poor developers) frustration is that almost all time when we do a insignificant change (or even just tap Cmd-R without any changes) in Swift-file or Objective-C file (.m) and then build again then big sh*t show starts again...
For example:
Frameworks may get rebuilt even though they are not touched.
Tons of app-level files get built again even though no interface changes, etc. was made.
Module verifier keeps verifying modules not touched at all, which takes really long time.
Xcode 16 didn't seems to improve the situation - on the contrary.
Example of an untouched framework that for unknown reason goes trough this every time we build:
I know it is hard to come with ideas to solve this for an unknown larger project. But do other people with similar-size projects also experience this or is re-building not an issue for you?
Cheers!
I've recently installed Xcode Version 15.0 (15A240d) and when I set a breakpoint it doesn't stop on the line of code where the breakpoint is set. Rather, it opens another window with the hex code. If I press F6 it doesn't highlight the next line of code, but I can see that it moved because the variables are changing.
Is this a known bug? I have tried all the usual stuff like deleting derived data and restarting everything. I have even deleted com.apple.dt.Xcode directory in ~/Library/Caches. to set things back to the defaults. The only thing I haven't done yet is reinstall Xcode.
Unfortunately, this is very bad timing as I need to get my app finished for the iOS17 and WatchOS 10 release.
I am using the latest version of Xcode 16, and I have created a GPX file in my project. However, I am unable to see or select the file to simulate the GPS location. I have attempted to uninstall and reinstall Xcode completely, but the issue persists. Has anyone encountered a similar problem? How can I resolve this? Thank you.
Our UITests are failing because Simulator won't start up. What can I do here?
Workflow Settings:
Sequoia 15.1
Xcode 16.1
Testing on iPad and iPhone 17.5 simulators
Thank you in advance
I've upgrade my macbook m3 pro to macOS 15, I have 2 iPhones (12 Pro and 16 Pro) - both on iOS 18 and have 3 versions of Xcode installed (15.4, 16.0, 16.1-2 beta)
For the past week I'm unable to develop on my physical device and checked all the threads in this forum for a workaround to disable the "Connect via Network".
If I'm not connected to VPN on any of my devices, I get the process attached via network after ~20 minutes, but if I try to do it while on VPN it takes forever (not even sure, can't spend 1 hour waiting to be attached or not)
What can I do to disable the "Connect via Network" and why is enabled by default and greyed out?
Description
When starting the iOS simulators on macOS-15 intel image, the following assertion happens: The same issue not showing for macOS 15-arm64 image. Here is the issue details: https://github.com/actions/runner-images/issues/10925 raised by multiple users.
AVPIdentity: AppleVirtualPlatformHostKey.mm:234: Assert: platformExpert, value: 0
AVPIdentity: AppleVirtualPlatformHostKey.mm:234: Failed to get AppleVirtualPlatformARMPE service.
The Simulators worked fine the day before the above issue was posted. What changed? Did something update?
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
Feedback Assistant
macOS
Virtualization
Simulator
When my mac is upgraded to 13.7, some shortcuts to Xcode are not available, such as command + left, command + right, command + Backspace
xcode 15.2, mac m2 mini, 14.2.1 sonoma
i need a pdf file to stage my app for screen shots for the market. icloud wont sync, cant drag files to the home screen or any screen, it just does not work.
i am at the end of my rope here, i just need some screen shots, my app is approved and ready
am i wrong>? is there a way to do this or is it just broken now in the name of (lazy) security?
edit--the more i read the more i angry and frustrated i get. this is broken and will not be fixed. i need to just workaround via email. so happy my second 100 dollar developer subscription bill is coming up!
After not happening to me for a few months, this issue has started hitting me again with currently %100 reproducability.
If turn on VPN on my Mac then instantly the developer certificates within the keychain become untrusted.
But that's not all, if VPN is then turned off the certificates do not revert to their trusted status but remain untrusted.
The consequence of this is that if VPN is turned on and then a build is perform, it fails, and the only way to fix things is to delete the cert(s) from they keychain and re-install them.
As a remote worker, having this happen several or even dozens of times a day is incredibly annoying and frustrating.
This issue has been occurring for literally years, sometimes it occurs very often, others while its quiet for a while, and has spanned multiple versions of Xcode and Mac OS. So whatever the cause is its endemic. It doesn't just affect myself, but all the members in my development team.
I'm currently using Xcode 14.1 RC 2 and Monterey but I've seen this issue occur with many versions of Xcode and Mac. (I'm using Cisco AnyConnect Secure Mobility Client).
If the VPN is somehow interfering/affecting the connectivity aspect when an attempt is made by Xcode to validate the certificate, then why does it not rectify itself after turning off VPN?
This is so so so so annoying.
Can somebody please comment on why this happens and if there's a way to prevent it.
I am getting the following warning printed in the console while my app is running
Invalid profile 'c2ci': tags 'gTRC' and 'desc' overlap
Console metadata specifies it comes from ColorSync at com.apple.colorSync
How to fix this? It prints a lot in the console.
Hi, I'm setting up Xcode and after updating MacOS to 15.2 and Xcode to 16.2, I cannot download the Predictive Code Completion Model. I've done some research and I haven't found any solution, specially since most people suggest that it randomly fixed itself, which for me hasn't been the case. I've tried restarting my Mac, uninstalling and reinstalling Xcode multiple times, I've also reinstalled MacOS from Recovery and haven't found any success (I'm also not running Xcode inside a VM, as I've seen this can cause some problems in this case).
This is the error that I receive when I attempt to download the model:
And here are the details:
The operation couldn’t be completed. (IDELanguageModelKit.IDEModelDownloadAdapter.(unknown context at $11eba9a90).DownloadError error 3.)
Domain: IDELanguageModelKit.IDEModelDownloadAdapter.(unknown context at $11eba9a90).DownloadError
Code: 3
User Info: {
DVTErrorCreationDateKey = "2024-12-26 23:09:25 +0000";
}
--
There was an error processing the asset.
Domain: IDELanguageModelKit.IDEModelDownloadAdapter.(unknown context at $11eba9a90).DownloadError
Code: 3
--
System Information
macOS Version 15.2 (Build 24C101)
Xcode 16.2 (23507) (Build 16C5032a)
Timestamp: 2024-12-26T17:09:25-06:00
For the record, I'm a new developer and I'm still learning, so thank you very much!
We have an existing app in which we have implemented AppShortcuts. The snippet view works fine in iOS 17 while in iOS18 beta, it doesn't able to fetch color from xcassets. If we use system colours or UIColor it's working fine.
Not working
Color("progressColor")
Working
Color(uiColor: UIColor(named: "progressColor")!)
Color.red
Color(hex: "3881d3") // Note: We created Color extension to generate color from hex string.
Hi,
After updating to Sequoia and the newest Xcode, I ran some Mac apps from Xcode. No code was changed, but suddenly, I'm getting:
Can't find or decode reasons
Failed to get or decode unavailable reasons
Can't find or decode disabled use cases
NSBundle file:///System/Library/PrivateFrameworks/MetalTools.framework/ principal class is nil because all fallbacks have failed
One problem (I think) is that - Mac/System/Library/PrivateFrameworks/MetalTools.framework/MetalTools is an alias with no original that can be found.
However, the MetalTools does exist in, for example, /Library/Developer/CommandLineTools/SDKs/MacOSX15.1.sdk/System/Library/PrivateFrameworks (and Mac ones).
The app is very simple/
Any suggestions? I have an Intel Mac.
Thank you!
-Ashley
I have an developer account and I want to delete it.How do I do that?
Hi! Predictive code completion once worked, but on Xcode relaunch another download got issued and it's failing.
Anybody can help?
The operation couldn’t be completed. (ModelCatalog.CatalogErrors.AssetErrors error 1.)
Domain: ModelCatalog.CatalogErrors.AssetErrors
Code: 1
User Info: {
DVTErrorCreationDateKey = "2024-10-27 17:00:22 +0000";
}
--
Failed to find asset: com.apple.fm.code.generate_small_v1.base - no asset
Domain: ModelCatalog.CatalogErrors.AssetErrors
Code: 1
--
System Information
macOS Version 15.0.1 (Build 24A348)
Xcode 16.0 (23051) (Build 16A242d)
Timestamp: 2024-10-27T19:00:22+02:00
Topic:
Developer Tools & Services
SubTopic:
Xcode
Happy to have a new MacBook Pro M4 now - the new machine was setup from time machine backup of my old MacBook Pro M1.
Sadly Predictive Code Completion does not work on the new M4 (it was working great on the M1).
Xcode shows as downloaded component:
Predictive Code Completion Model [com.apple.fm.code.generate_small_v1.base: 500.1.81600.13.200772,0] [com.apple.fm.code.generate_safety_guardrail.base: 1.6.81619.13.200716,0] [com.apple.gm.safety_deny.input.code_intelligence.base: 32024010.20241007.171244.100.377,0] [com.apple.gm.safety_deny.output.code_intelligence.base: 32024010.20241007.171244.100.377,0] (Installed)
Things I already tried:
Removed and reinstalled Xcode 16 (also latest beta).
Disabled/enabled Xcode Editor Settings for predictive code completion
Many many reboots
Removed Xcode cache
Maybe the downloaded Model is somehow locked to the old machine?
How can I remove, redownload or reinstall it again?
Thank you very much.
Tobias
Is there any way to stop previews from live updating? It's constantly running and that's nice when I'm developing, but I'd like it to pause updating when I'm not using the Xcode. It heats up my m1 air and drains unnecessary power reducing the battery levels significantly.
Hi,
I work on a iOS application which includes several local swift packages containing modularised code. Each of those local swift packages has a test target defined in their respective Package.swift, and when opening a local package folder standalone in Xcode, then the tests run without issues.
However I would like in the main app's test plan to add the local package test targets and have them all run together when the main app's default test plan is run. Xcode allows me to select local package test targets within the main app's test plan (also within Test portion of the main app's scheme), however attempting to build for testing throws a "Module '…' was not compiled for testing".
Any ideas on how to achieve this goal (run local package tests in conjunction with main app's tests) and avoid that error?
Thanks
Peter
Hi.
Just update my MacBook Pro M1 with sequoia and Xcode and I got huge problem with preview on simply swiftui pages.
This is the full report I got when the preview crash but if I run the app on the device or the simulator it works fine. How can I solve this situation?
the crashing thread is number 6 which reports this:
Thread 6 Crashed:: Dispatch queue: com.apple.root.user-initiated-qos
0 XOJIT 0x240b899f8 llvm::Error llvm::detail::UniqueFunctionBase<llvm::Error, llvm::jitlink::LinkGraph&>::CallImpl<xojit::ReplacementManager::Plugin::modifyPassConfig(llvm::orc::MaterializationResponsibility&, llvm::jitlink::LinkGraph&, llvm::jitlink::PassConfiguration&)::'lambda'(llvm::jitlink::LinkGraph&)>(void*, llvm::jitlink::LinkGraph&) + 1784
1 XOJIT 0x240c1b46c llvm::jitlink::JITLinkerBase::runPasses(std::__1::vector<llvm::unique_function<llvm::Error (llvm::jitlink::LinkGraph&)>, std::__1::allocator<llvm::unique_function<llvm::Error (llvm::jitlink::LinkGraph&)>>>&) + 76
2 XOJIT 0x240c1ab68 llvm::jitlink::JITLinkerBase::linkPhase1(std::__1::unique_ptr<llvm::jitlink::JITLinkerBase, std::__1::default_delete<llvm::jitlink::JITLinkerBase>>) + 72
3 XOJIT 0x240c2158c llvm::jitlink::link_MachO_arm64(std::__1::unique_ptr<llvm::jitlink::LinkGraph, std::__1::default_delete<llvm::jitlink::LinkGraph>>, std::__1::unique_ptr<llvm::jitlink::JITLinkContext, std::__1::default_delete<llvm::jitlink::JITLinkContext>>) + 3608
4 XOJIT 0x240c20400 llvm::jitlink::link_MachO(std::__1::unique_ptr<llvm::jitlink::LinkGraph, std::__1::default_delete<llvm::jitlink::LinkGraph>>, std::__1::unique_ptr<llvm::jitlink::JITLinkContext, std::__1::default_delete<llvm::jitlink::JITLinkContext>>) + 72
5 XOJIT 0x240c19cc8 llvm::jitlink::link(std::__1::unique_ptr<llvm::jitlink::LinkGraph, std::__1::default_delete<llvm::jitlink::LinkGraph>>, std::__1::unique_ptr<llvm::jitlink::JITLinkContext, std::__1::default_delete<llvm::jitlink::JITLinkContext>>) + 80
6 XOJIT 0x240c0acc0 llvm::orc::ObjectLinkingLayer::emit(std::__1::unique_ptr<llvm::orc::MaterializationResponsibility, std::__1::default_delete<llvm::orc::MaterializationResponsibility>>, std::__1::unique_ptr<llvm::MemoryBuffer, std::__1::default_delete<llvm::MemoryBuffer>>) + 256
7 XOJIT 0x240bfcbfc llvm::orc::BasicObjectLayerMaterializationUnit::materialize(std::__1::unique_ptr<llvm::orc::MaterializationResponsibility, std::__1::default_delete<llvm::orc::MaterializationResponsibility>>) + 60
8 XOJIT 0x240be3f08 llvm::orc::MaterializationTask::run() + 44
9 XOJIT 0x240b97e1c invocation function for block in (anonymous namespace)::GCDTaskDispatcher::dispatch(std::__1::unique_ptr<llvm::orc::Task, std::__1::default_delete<llvm::orc::Task>>) + 108
10 libdispatch.dylib 0x1801774ec _dispatch_call_block_and_release + 24
11 libdispatch.dylib 0x180178de0 _dispatch_client_callout + 16
12 libdispatch.dylib 0x18018b864 _dispatch_root_queue_drain + 1208
13 libdispatch.dylib 0x18018bf60 _dispatch_worker_thread2 + 232
14 libsystem_pthread.dylib 0x104db7b38 _pthread_wqthread + 224
15 libsystem_pthread.dylib 0x104db6934 start_wqthread + 8
Full Report