After updating my Xcode to the latest, I am unable to download an installed app container from the Xcode Devices screen. This currently works with older versions of Xcode with the same app on the same iPad. This worked with older versions of Xcode on the same MacBook as well (including the Xcode 26 beta before updating to the official release yesterday) The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { DVTErrorCreationDateKey = 2025-09-18 20:31:01 +0000; NSURL = file:///Users/thomsk2/Desktop/com.test.polarisdev%202025-09-18%2015:30.53.744.xcappdata/AppData/Library/Caches/; } The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { NSURL = file:///Users/thomsk2/Desktop/com.test.polarisdev%202025-09-18%2015:30.53.744.xcappdata/AppData/Library/Caches/; } Failed to perform I/O operations. Domain: com.apple.dt.remoteservices.error Code: 11001 Failure Reason: Cannot open destination file /Users/thomsk2/Desktop/c
Search results for
build disappears
49,245 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I am able to sign my application when logged in to the machine, however when build is running in CI (Jenkins), I get this: Warning: unable to build chain to self-signed root for signer.. We just renewed or certificates, so I am not sure about previous procedure, but it used to work without temporary keychain and stuff, I believe. What should be the recommended way to sign an application on CI? What keychain should we use? system? temporary? other method? Thanks, Itay
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
I have wrapped the (if let banjo) block in a dummy function and it builds. Only issue is where to run the function. I'd be happy with it running first in the program. As soon as I boot up. I suppose I could put a button in the content view that runs the function, which I assume would make the network call. Is that ok?
Here's some things to try: login to developer.apple.com and check and see if com.os.hub.mth2 inadvertently was registered in your personal account instead of your developer account. If it was, delete it from your personal account. Login to developer.apple.com and check and see if you have a wildcard app id registered in your account. If you do, delete it. If you're using automatic code signing you can delete the invalid certificates in the Keychain Access app. Xcode will download the correct certificates next time you run a build. If that doesn't help, consider opening a support incident so I can take a look at the settings on your machine. https://developer.apple.com/support/technical/
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Hello @pablo_figueroa , thank you for your question! Because you are using Unity to build your project, it's difficult for us to know exactly what might be breaking. I highly recommend sending feedback using Feedback Assistant with your attached project, and then including the ticket number here, so we can look more closely. Additionally, I recommend reaching out to Unity on their developer forums in case anyone there has experienced a similar issue. In the Frameworks, Libraries and Embedded Content section of your Xcode project, do you see your framework listed there? It should be set to Embed & Sign. If I recall correctly there is a checkbox in Unity in the inspector for your plugin under the visionOS tab at the bottom, Add to Embedded Binaries, that may help. You can check out our documentation here. Let me know if you have any more questions! Thank you!
Topic:
Spatial Computing
SubTopic:
General
Tags:
We are working on a general USB device management solution on macOS for enterprise security. Our goal is to enforce policy-based restrictions on USB devices, such as: For USB storage devices: block mount, read, or write access. For other peripherals (e.g., USB headsets or microphones, Raspberry Pi, etc.): block usage entirely. We know in the past, kernel extensions would be the way to go, but as kext has been deprecated. And DriverKit is the new advertised framework. At first, DriverKit looked like the right direction. However, after reviewing the documentation more closely, we noticed that using DriverKit for USB requires specific entitlements: DriverKit USB Transport – VendorID DriverKit USB Transport – VendorID and ProductID This raises a challenge: if our solution is meant to cover all types of USB devices, we would theoretically need entitlements for every VendorID/ProductID in existence. My questions are: Is DriverKit actually the right framework for this kind of general-purpose USB device control? No.
Topic:
App & System Services
SubTopic:
Drivers
Tags:
Is anyone else experiencing NavigationStack title disappearing in iOS 26? Hey everyone, I just updated to iOS 26 and I'm running into a really frustrating issue with my app. Wondering if anyone else is seeing this or if I'm missing something obvious. What's happening: My navigation titles are completely blank when the app first loads, but then magically appear when I scroll down. It's super weird and makes my app look broken at first glance. My setup: I'm using NavigationStack with some pretty standard stuff: Navigation title with .navigationTitle() A toolbar with a settings button ScrollView content with a gradient background Here's basically what I have: NavigationStack { ScrollView { VStack(spacing: 24) { // My app content here - cards, etc. ForEach(myItems) { item in // Content cards } } .padding() } .background( LinearGradient( gradient: Gradient(colors: [ Color.surfacePrimary, Color.surfacePrimary.opacity(0.95), Color.surfaceSecondary.opacity(0.3) ]), startPoint: .top, endPoint: .bottom ) ) .na
I am not having trouble deciding what to do in my code if I get a non URL value in banjo. I'm using the same URL that I think I will always use, and that won't change. And that I'm checking is valid. That being the case I've tried pasting the code you gave me into xcode and it still won't build. Here's what I put in xcode let myString = https://www.alphavantage.co/query?function=TIME_SERIES_DAILY&symbol=AAPL&apikey= ********* if let banjo = URL(string: myString) { let Lulah = URLSession.shared.dataTask(with:banjo ) { myDatastring , response , error in} Lulah.resume() } else { myDatastring=nil url } I'm getting a build error on the line starting if let banjo. The build error is: Statements are not allowed at the top level and is tied to the first word, if. Thank you for your generous help.
I’m building a document-based macOS app using SwiftUI with an AppKit NSDocument. By default, when the window has no toolbar, the document title and proxy icon (with the edited state dot and standard saving controls) appear nicely centered in the title bar. However, as soon as I attach a toolbar - even an empty one - the document proxy moves to the leading edge of the title bar. Is there a way to keep the document proxy/title centered in a document-based SwiftUI app while also using a toolbar? Or is the left-alignment now the only supported behavior when a toolbar is present? Thanks in advance for any guidance.
I have exactly the same problem, and would appreciate some guidance on whether hang diagnostics on macOS actually work. The same as the original poster above, the Simulate MetricKit Payload debug option works fine, and a crash is delivered immediately on restarting the app. No sign of any real hang reports though, even after deliberately causing hangs in the app. It’s my understanding that they should be delivered immediately, but even after waiting several days there’s still nothing. I’ve tried debug, release, and TestFlight builds. Any guidance as to what I could possibly be missing would be great! Thank you.
Topic:
App & System Services
SubTopic:
General
Tags:
This is still broken in Xcode 26 Stable builds
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
Xcode build done. 0.7s Failed to build iOS app Uncategorized (Xcode): Unable to find a destination matching the provided destination specifier: { id:42969747-3560-448B-8EB3-CB5ED88D75C1 } Available destinations for the Runner scheme: { platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:00008132-0004256C34A1801C, name:My Mac } { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device } { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device } Could not build the application for the simulator. Error launching application on iPhone 17.
Hello Having trouble getting associated domain to work in our project. It was working when we used Branch, but our company wants to host the domain ourselves. This is a multi-scheme project, using .xcconfig files to define the correct entitlement per Build. The relevant entitlement file has: com.apple.developer.associated-domains applinks:bm.ddcas.ai in the ....{other irrelevant test associated domains....} The project Team and App ID are taken from the Identifiers screen where the Identifier capabilities has 'associated domains' ticked on. I've also checked elsewhere on AppleDeveloper/Connect to be sure. When we used Branch with domain key app links: bmstores.app.link this worked fine. With https://bm.ddcas.ai (our own host) which is publicly available and has an aasa file in both the main directory and /.well-known, typing this in safari or anything just doesn't attempt to link to the App. The iPhone is in developer mode, and using the developer menu associated domains diagnostic tool, typing https
I have a strange problem. My code works perfectly on my iPhone, i.e. on a real iPhone, but when I upload the build version to TestFlight, it no longer works. I use React Native. The issue is as follows: I have created a code for Grid View that runs automatically when another person joins the stream. It works locally without any problems, but unfortunately the public version does not work. What could be the reason for this?
Device: iPhone 15pro, ios26.0 (23A 341) IOS version: 26.0 (23A 341) When using position: sticky; bottom: 0, the div is expected to stick to the bottom of the viewport when the browser toolbar hides while scrolling. However, it stops at the height where the toolbar was, instead of moving down with the disappearing toolbar. In the image below, the red-bordered navigation shows the situation where it does not stick to the bottom. i