The Test target not build for not such file or directory: 'CoreGraphics'. Not sure why I get this error, but I configured the target without forgetting the variables BUNDLE_LOADER with $(BUILT_PRODUCTS_DIR)/MyExistingApp.app/MyExistingApp value and TEST_HOST with $(BUNDLE_LOADER) value. App target (not the test target), the Symbols Hidden by Default build setting its equal to NO, unlike the Test target that is set to YES. Any variable more for this? I'm not sure if I should take anything into account when using Xcode 26.1.1 and Swift Testing framework.
Search results for
file uri scheme
79,851 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
We are encountering the same issue since Xcode 16. We run XCTest and Swift Testing. For us it is flaky, sometimes some local Packages (SPM) are missing in the .xcresult file, resulting in a Coverage of 0% for these packages
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Environment macOS Version: 26.1 Xcode Version: 16.2 Description I'm developing a custom file system using FSKit and have encountered an issue where the removeItem(_:named:fromDirectory:) method in my FSVolume.Operations implementation is not being invoked when attempting to delete files or directories through Finder or the command line. Implementation My volume implements the required FSVolume.Operations protocol with the following removeItem implementation: func removeItem( _ item: FSItem, named name: FSFileName, fromDirectory directory: FSItem ) async throws { logger.info(remove: (name)) if let item = item as? MyFSItem, let directory = directory as? MyFSItem { directory.removeItem(item) } else { throw fs_errorForPOSIXError(POSIXError.EIO.rawValue) } } Steps to Reproduce Mount the custom FSKit-based file system using: mount -F -t MyFS /dev/diskX /tmp/mountpoint Create files using Finder or terminal (works correctly - createItem is called) Attempt to delete a file
I'm developing a custom file system using FSKit. After testing some example projects on github and have encountered an issue where the removeItem(_:named:fromDirectory:) method in my FSVolume.Operations implementation is not being invoked when attempting to delete files or directories through Finder or the command line. Environment: macOS: macOS 26.1 Xcode: 16.2 / 17A400 Sample Project: https://github.com/KhaosT/FSKitSample https://github.com/debox-network/FSKitBridge My volume implements the required FSVolume.Operations protocol with the following removeItem implementation: func removeItem( _ item: FSItem, named name: FSFileName, fromDirectory directory: FSItem ) async throws { logger.info(remove: (name)) if let item = item as? MyFSItem, let directory = directory as? MyFSItem { directory.removeItem(item) } else { throw fs_errorForPOSIXError(POSIXError.EIO.rawValue) } } Steps to Reproduce: Mount the custom FSKit-based file system Create files using Finder or terminal (works
My xcodeproject file got corrupted in a way or the other as the entitlement file location was zeroed while the file was still there. Very sorry for the noise... Please delete the post if possible.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I have a Hypervisor Framework App that works on MacOS 14 and 15 but fails on MacOS 26. To reproduce: hv_vm_config_t vm_config = hv_vm_config_create(); result = hv_vm_create(vm_config); result == HV_DENIED /* (0xfae94007) */ (from per the header file - not present on the online documentation) com.apple.security.hypervisor is set, no other VMs are running (no Virtualization Framework and no Hypervisor Framework). I have tried various entitlements with no success. Sandbox is off.
Hello, I am currently implementing External Purchase Link and External Purchase Custom Link and am encountering an issue where both ExternalPurchaseLink.canOpen and ExternalPurchaseCustomLink.isEligible always return false under all test conditions. I would like to confirm whether my setup is missing any required steps or whether this behavior is expected. Below are the details of my current environment and configuration: 🔧 1. Development Environment Xcode: 16.3, 16.4, 26.0 beta 4 Devices: iPhone running iOS 26.2 beta iPhone running iOS 16.7.12 macOS 15.5 (real device testing) Simulator iOS 18.0 Build Type: Local development build using a Developer Provisioning Profile Sandbox account signed in during testing 🔑 2. Entitlements (Developer site & Xcode) In Certificates → Identifiers → App ID, both capabilities are enabled: StoreKit External Purchase StoreKit External Purchase Link The .entitlements file in Xcode includes: com.apple.developer.storekit.external-purchase = YES com.apple.developer.st
Feedback FB21154711 I have this code struct ContentView: View { var body: some View { VStack { Link( www.apple.com, destination: URL(string: https://apple.com)! ) .buttonStyle(.bordered) } .padding() } } and get error when tapped unable to make sandbox extension: [2: No such file or directory] 0.5 Potential Structural Swift Concurrency Issue: unsafeForcedSync called from Swift Concurrent context. 0.5
Topic:
Accessibility & Inclusion
SubTopic:
General
Tags:
I want to use FileProvder to implement the function of recovering from the recycle bin (the cloud recycle bin does not move, and after the local recycle bin is restored, the upload event is triggered again), but testing shows that the current recovery from the recycle bin is through the modifyItem event, and the CreateItem event is not triggered again to upload locally restored files Implement the deletion of undelivered files (dateless) without moving them to the recycle bin, which currently appears to be achieved by granting file. dash permission. But it is possible for the content of a file to be manually verified by the user. How can this be solved? How can we dynamically monitor whether a file is dataless Thank you for your reply. Could you please help answer my question
I think FSKit modules have to be sandboxed, but since you're not planning to be on the App Store and thus don't need to care about App Review, have you looked at the temporary exception entitlements (https://developer.apple.com/library/archive/documentation/Miscellaneous/Reference/EntitlementKeyReference/Chapters/AppSandboxTemporaryExceptionEntitlements.html)? You might find the file access ones useful.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Hi everyone, I’m experiencing a persistent issue when trying to download the iOS Simulator Runtime 26.1 on Xcode (version 26.1). The download always fails with the following error Download failed due to a bad URL. (Catalog download for com.apple.MobileAsset.iOSSimulatorRuntime) Domain: com.apple.MobileAssetError.Download Code: 49 I’m located in Brazil, so I initially thought it might be region-related, but I’ve already tried several attempts to fix it, including: Using VPNs for the US and Europe Installing the Xcode 26.2 beta Downgrading Xcode to earlier versions Reinstalling the same version of Xcode Restarting Xcode and my Mac Switching networks Clearing simulator support/device files Unfortunately, nothing has resolved the issue. Is anyone else facing this problem? Does anyone know a workaround or a manual way to download/install the iOS 26.1 simulator runtime? Thanks in advance!
Thanks for the update. The HTTP 301 and 302 is not supported for requests to AASA files, I don’t know how was working previously. TN3155: Debugging universal links | Apple Developer Documentation#Host-and-verify-your-AASA Upon installation, you can access the file sw_utils located within the sysdiagnose directory. Please provide me with the error message that occurs when the application attempts to retrieve the AASA file. It is likely that the HTTP response redirect is the cause of the application’s inability to fetch the file again. You still can see the try on the file. When you mentioned that the request is not being made at all, I am perplexed. The system will consistently make the request if you have configured the AASA file URL within the application to download. Naturally, it will cease attempting to download the file after encountering the redirect. Therefore, it is crucial to obtain the log file and troubleshooting steps from the
Topic:
App & System Services
SubTopic:
General
Tags:
Hello Apple Developer Community, I'm experiencing an issue on macOS where ASWebAuthenticationSession fails to display its authentication window. The session is created successfully and start() returns true, but: no UI is shown, presentationAnchor(for:) is never invoked, the completion handler is never called, and no errors appear in Console.app or Xcode logs. This happens both when using the session via a Flutter plugin and when calling ASWebAuthenticationSession directly from Swift. Environment macOS 14.6 (Sonoma) Xcode latest stable Target: macOS 10.15+ App type: sandboxed macOS app, hardened runtime enabled The project also includes a Login Item (SMAppService) target Redirect URI scheme: myapp-auth://callback Problem Description When I trigger authentication, the logs show: [AuthPlugin] Starting ASWebAuthenticationSession... After that: no authentication sheet appears, presentationAnchor(for:) is never called, the completion handler is not invoked. The main window is visible and active wh
Topic:
Community
SubTopic:
Apple Developers
@bradpriddy Thank you for the post and the link to the code, this is really good with a great description as well as the comprehensive list of devices where the device fails to receive a push-to-start token. I believe is a bug however, regrettably, I am not an expert in the APN start token and update token. However, I believe the most expedient course of action, to resolve the issue is to submit a bug report with a zip file containing the code you have provided and a concise summary of the problem. Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
Worldwide Developer Relations.
Topic:
App & System Services
SubTopic:
Widgets & Live Activities
Tags:
I'm glad I found this thread because we're experiencing exactly the same thing. We're uploading a large-ish (hundreds of MB) file to AWS S3 and using a BGContinuedProcessingTask to show the progress. The actual upload happens in the background using the AWS S3 SDK. Everything goes fine until we lock the screen, then the BGContinuedProcessingTask is expired even though the upload is still ongoing. Is there any resolution on the horizon for this issue? Would it help if I file a Feedback Assistant report or can I join an existing one?
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags: