Search results for

file uri scheme

79,854 results found

Post

Replies

Boosts

Views

Activity

Reply to ScreenCaptureKit sample initially omits application with NSWindowSharingType NSWindowSharingNone
Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: UI Frameworks SubTopic: General Tags:
Nov ’25
Reply to VisionOS Enterprise API Not Working
Hi @vision_pro_developer2000 I'm unable to reproduce the no camera frames issue when building the app with a valid Enterprise.license file. However, I can reproduce the issue when any of the following conditions occur. Verify that none of these apply to your setup Expired or outdated license: Ensure you're using the most recently issued Enterprise.license file, not an expired version. Incorrect filename: The file must be named exactly Enterprise.license (case-sensitive, no variations). License not properly replaced: The placeholder Enterprise.license must be completely replaced with your actual license file; copying and pasting the file's contents into the placeholder file will not work. Team mismatch: Confirm you're building the app using the same Apple Developer team that the license was issued to. Test your license setup Add the snippet below to your app to confirm your app has main camera API access. Refer to this video for a detailed walkthrough. // A
Topic: Spatial Computing SubTopic: ARKit Tags:
Nov ’25
Xcode Cloud Builds Failing with 7-8 Errors - Builds Stuck in "Processing" on App Store Connect
Hey there. I'm experiencing a critical issue with Xcode Cloud builds for my macOS application (bundle ID: com.mymind.mymind-mac) where builds fail in Xcode Cloud with 7-8 errors, yet all logs indicate successful completion. Additionally, when manually uploading builds, they become stuck in Processing status indefinitely on App Store Connect. Issue Details: Problem: Xcode Cloud reports 7-8 build errors but logs show no fatal errors Secondary Issue: Builds uploaded to App Store Connect remain in Processing status indefinitely Platform: macOS application with Safari Web Extension Xcode Version: 26.1.1 (26B100) - Xcode 26.1 Build Environment: Xcode Cloud What Works: Package dependency resolution completes successfully Archive creation succeeds (** ARCHIVE SUCCEEDED **) Export succeeds (** EXPORT SUCCEEDED **) Provisioning profiles are created correctly Code signing completes without errors Manual upload to App Store Connect completes What Fails: Xcode Cloud: Build process fails with 7-8 errors, but no correspondi
Topic: Developer Tools & Services SubTopic: Xcode Cloud
3
0
248
Nov ’25
Reply to Lock Contention in APFS/Kernel?
F_FULLFSYNC is basically always going to be relatively slow. The API operates on a file handle, but flushing the volume to a coherent state is a broader operation the final I/O command is a device command. All of that makes it a fairly heavy operation. Gotcha, thanks for the background! On that note, I did my research—to our mutual peril—and found a comment (https://news.ycombinator.com/item?id=25204202) that cited sqlite's codebase, noting that fdatasync() on HFS+ doesn't yet flush the file size if it changed correctly. Some folks on the postgres mailing list also appear to be a bit uncertain about the current situation: https://www.postgresql.org/message-id/flat/CA%2BhUKGLv-kvrtA5QEL%3Dp%3DdYK0p9gsMXJaVhUFu%2BA-KyFrFi%3D2g%40mail.gmail.com#fe6d1c5665a381687842758fd5b245d4. I'm a newbie when it comes to understanding C code, but looking over kern_aio.c, I see two seemingly contradictory comments. On lines 658–659: * NOTE - we do not support op O_DSYNC at this point since we do not support t
Topic: App & System Services SubTopic: Core OS Tags:
Nov ’25
Reply to Apple Pay appears in Stripe Payment Sheet but closes immediately when attempting payment (React Native iOS)
Hi, sorry to hear you're having issues with Apple Pay. Given you're using Apple Pay through a third party API (in this case Stripe's), you may need to reach out to them to determine the cause. To try and help, if you've confirmed Apple Pay on the Web is working on the same device with the same merchant identifier, then you should be able to rule out any issues with cards available on the device or the device region, and it suggests more of an issue with the underlying integration between the third party library and the native PassKit APIs. Because the Apple Pay sheet appears, and allows you to attempt to authorise a transaction, this should also rule out any entitlement or code signing issues for the app as well. It may be worth checking to see if the device is logging anything, which may provide some insight as to why it's failing. You can do this using Console on macOS with the device connected, and selecting it in the side menu. In particular, filtering on PassbookUIService should reduce most of the unnece
Topic: App & System Services SubTopic: Apple Pay Tags:
Nov ’25
Local Swift Package does not update in my project
in my xcode project, i created a new package by going through File > New > Package, just like they said in https://developer.apple.com/documentation/xcode/organizing-your-code-with-local-packages I have a package, but the problem is, whenever I made any changes in the package's source code, it never showed in the main project. I can import the package just fine, but the package does not show anything. no added apis, functions, nothing. Im using Xcode 26.0.1
Topic: Developer Tools & Services SubTopic: Xcode Tags:
0
0
38
Nov ’25
Reply to Building SimpleAudioDriver example
Ok, I found this in dmesg/syslog: [46147.634755]: DriverKitSampleA[6170] triggered unnest of range 0x1fc000000->0x1fe000000 of DYLD shared region in VM map 0x853f7106fc70fc7d. While not abnormal for debuggers, this increases system memory footprint until the target exits. [46147.634762]: DriverKitSampleA[6170] triggered unnest of range 0x1fe000000->0x200000000 of DYLD shared region in VM map 0x853f7106fc70fc7d. While not abnormal for debuggers, this increases system memory footprint until the target exits. [46148.219526]: Sandbox: ContextStoreAgent(448) allow file-read-data /Users/daniel/Library/Developer/Xcode/DerivedData/DriverKitUserClientSample-haxyygamobxzqybcidlsjqhbccev/Build/Products/Debug/DriverKitSampleApp.appSandbox: ContextStoreAgent(448) allow file-read-data /Users/daniel/Library/Developer/Xcode/DerivedData/DriverKitUserClientSample-haxyygamobxzqybcidlsjqhbccev/Build/Products/Debug/DriverKitSampleApp.app/ContentsSandbox: ContextStoreAgent(448) allow file-read-data
Topic: Code Signing SubTopic: Entitlements
Nov ’25
Reply to When xcode is tried again, it always fails to install the app
Thank you for sharing the post. This appears to be a coredevice issue to me. Have you filed a bug report? You should update your Xcode version to the latest version as well as you macOS. If still happening on the latest version, please file a bug: 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: Developer Tools & Services SubTopic: Xcode Tags:
Nov ’25
Reply to App rejected under 4.3
Thank you for your post. If you disagree with the outcome of the review, we recommend submitting an appeal to the App Review Board. When filing your appeal, make sure to: Provide specific reasons why you believe your app complies with the App Review Guidelines. Submit only one appeal per rejection. Respond to any requests for additional information before submitting an appeal. Once you have submitted the appeal we can escalate it to the App Review Board for review. The App Review Board will contact you directly as soon as they've completed their investigation.
Topic: App Store Distribution & Marketing SubTopic: App Review
Nov ’25
Reply to DEXT (IOUserSCSIParallelInterfaceController): Direct I/O Succeeds, but Buffered I/O Fails with Data Corruption on Large File Copies
The error occurred when fio attempted to verify the second 1MB data block (starting at offset 1,048,576). So what's IS there? And what should have been? These test use hashes for verification because it's the quickest way to validate the data, but the question I'm interested in here is what your driver actually put on disk. Part of my concern here is that unless you artificially cut power to the device, we shouldn't have needed any explicit cache sync as part of the copy. The system should have flushed all of it's buffers to your DEXT as part of unmount and you should have flushed them to disk shortly after that. If this is really about cache flushing, that's the failure case I'd really be concerned* about here, not the individual copy. *Failure to flush a file loses file data. Failure to flush file system blocks loses volumes. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic: App & System Services SubTopic: Drivers Tags:
Nov ’25
Reply to Lock Contention in APFS/Kernel?
I'm sorry for the delay in submitting a feedback item; a cross-country move happened. Not a problem, I've got plenty to keep my busy! That leads to here: I've submitted FB21093202. So, looking over the bug, there are a few things I want to clarify: F_FULLFSYNC is basically always going to be relatively slow. The API operates on a file handle, but flushing the volume to a coherent state is a broader operation the final I/O command is a device command. All of that makes it a fairly heavy operation. On the APFS side, the specific concern I have here is about the performance dip at high core count. That's partly because of the immediate issue and mostly because our core count has been increasing, and we need to be watching for these concurrency bottlenecks. Cross platform comparisons are very tricky here because the platforms are (ideally) making different design decisions based on the specifics of of their particular use case and user base. For example, in an enterprise/server environment, there's an ar
Topic: App & System Services SubTopic: Core OS Tags:
Nov ’25
Getting crashes when using QLPreviewPanel on AddressBook items
My app (FindAnyFile) provides a Finder-like interface in which it also offers a QuickLook preview command, which invokes [[QLPreviewPanel sharedPreviewPanel] makeKeyAndOrderFront:nil]; Now, if it shows .abcdp files, it often, but not always, crashes. This has been happening for many macOS versions, at least since 10.15, up to 26.1. Also, it does not seem to matter which SDK/Xcode I build with, as I used several and all versions lead to the crash. The issue rather appears to be inside the QLplugin for the AB file (ABCardCollectionView etc.). I am able to trace this crash in Xcode. There are a LOT of errors and warnings coming up, and eventually the qlplugin throws an ObjC exception which in turn brings down my entire app (and here I thought that the XPC system was designed to expressly avoid such crashes). Possibly significant errors are: CNAccountCollectionUpdateWatcher 0x6000025cf800: Update event received, but store registration failed. This event will be handled, but the behavior is undef
Topic: UI Frameworks SubTopic: AppKit Tags:
0
0
71
Nov ’25
Reply to checkResourceIsReachableAndReturnError or fileExistsAtPath for security scoped resources
Thanks, I'll check explicitly for the combination of NSCocoaErrorDomain and NSFileReadNoSuchFileError then. For anyone ending up in this thread, note that NSFileNoSuchFileError is not the same error as what's being reported by checkResourceIsReachableAndReturnError. The error is: Domain=NSCocoaErrorDomain Code=260 The file “write-single-file.txt” couldn’t be opened because there is no such file. UserInfo={NSURL=file:///Users/torarne/write-single-file.txt, NSFilePath=/Users/torarne/write-single-file.txt, NSUnderlyingError=0xa83590c90 {Error Domain=NSPOSIXErrorDomain Code=2 No such file or directory}}
Topic: App & System Services SubTopic: Core OS Tags:
Nov ’25