Search results for

“file uri scheme”

81,750 results found

Post

Replies

Boosts

Views

Activity

Instruments Malfunction
I’m reporting a severe reproducible issue in Instruments, specifically when using the SwiftUI instrument and opening Show Cause & Effect Graph. What happens: • Instruments becomes extremely laggy/unresponsive • The graph/detail area can turn solid magenta/pink • Memory usage rapidly increases (I observed around 18 GB, 25 GB, and up to 34 GB) • My Mac has crashed/restarted during this, or in other terms, had a kernel panic, where my Mac froze, and everything unresponsive. The Trackpad wouldn't even click. Important detail: • I could not find a generated kernel panic log after the crash/restart. Repro context: • SwiftUI iOS app profiled from Xcode • Trigger is specifically entering Show Cause & Effect Graph • Recordings can be short and still trigger it • Issue is much less severe or absent if I avoid that view What I already tried: • Rebooting • Short captures / fewer instruments • Clearing Xcode/Instruments caches/preferences • Retesting after cleanup • Reinstalling Xcode Is this a known Instruments r
2
0
127
2w
Reply to Unusually Long "Waiting for Review" Times This Week - Anyone Else?
@App Review The issue is NOT resolved for all developers. I have two apps stuck in Waiting for Review with zero communication: OKIRIZO (Apple ID: 6757417197) - First submitted Jan 10, 2026. Current submission Feb 25. Over 2 months waiting. TidaKitchen (Apple ID: 6759185372) - Submitted ~Mar 11. Still waiting. I have filed THREE support cases with no response: Case 102824913561 (Feb 19) - no reply Follow-up (Mar 4) - no reply Case 102846444484 (Mar 17) - no reply Expedited review request also submitted with no response. Three support cases over one month, all ignored. This is unacceptable for paying Apple Developer Program members. Please investigate immediately.
2w
Reply to App review process takes long time
I am experiencing the same issue with two of my apps. OKIRIZO (Apple ID: 6757417197) - First submitted January 10, 2026. Current submission from February 25, now waiting 23+ days. I have contacted Apple Developer Support on February 19 (case 102824913561), followed up on March 4, and again on March 17 (case 102846444484). No response to any of these inquiries. I have also submitted an expedited review request with no response. TidaKitchen (Apple ID: 6759185372) - Submitted approximately March 11, also stuck in Waiting for Review. Both are v1.0 initial submissions. No messages, no rejections, no feedback in App Store Connect. Three support cases filed over the past month with zero replies. This is severely impacting our business operations in Okinawa, Japan. Could the App Review team please investigate?
2w
Reply to CallKit lock screen UI on iOS 26: “slide to answer” text is too faint / hard to read
I've noticed the same contrast issue on iOS 26 with dark wallpapers. This appears to be a Liquid Glass regression — the frosted material doesn't adapt well to certain background luminance levels. Since the slide to answer text is entirely system-managed through CallKit, there's no app-side workaround. I'd recommend filing a Feedback (if you haven't already) under UIKit > System UI with a screenshot showing the low contrast scenario. Referencing the WCAG 2.1 AA contrast ratio requirement (4.5:1 for normal text) in your report might help prioritize it, since this is a core accessibility concern for incoming calls.
Topic: Design SubTopic: General Tags:
2w
Reply to File Export from iOS - eventually import too
When I rename a file I can't seem to change the extension. For example: when I select the file and change to MyFile.csv - it writes MyFile.csv.txt is there any way to get rid of that .txt extension other than make the user delete it? I mean they could edit from .txt to .csv and macOS asks if they are sure - but I'd like to remove that step. That might be worthy of a feedback...
Topic: UI Frameworks SubTopic: SwiftUI
2w
File Export from iOS - eventually import too
iOS 15 - iOS 26.x, SwiftUI, Xcode 26.1.1 (rewritten without links) I’m attempting to add the capability to export a file from CoreData. Since ShareLink requires iOS16+, I found an article showing how to create a UIKit wrapper for 'UIActivityViewController' This does work, but I end up with multiple files instead of one. How do I merge this into one file? Note: I don’t think I want to write to the app’s document directory – rather I’d like to allow the user to export to iCloud. Eventually, I’d like to share a list of dates with descriptions and if someone puts a sensitive date in there – I don’t want it to be left in a directory. I would include a warning that the file that they export needs to be handled with care if there are any sensitive dates. Some might consider birthdays as private information, right? I'd also like to be able to name the file - so far when the share sheet comes up, I select Save to Files and it uses a default name of text.txt My next
Topic: UI Frameworks SubTopic: SwiftUI
6
0
320
2w
Reply to copyfile Sometimes Fails to copy .DS_Store when Copying a Folder But Does Not Report Usable Error
Mystery (partially) solved. I just took a sneak peak at the extended attributes of the .DS_Store file and some have a resource fork (probably the ones that were failing to copy I BET!). So appears to be the same failure we are talking about here: https://developer.apple.com/forums/thread/814076 Can you upload a copy of the .DS_Store file to the bug you filed on this? Also, what's the bug number? Also, are you sure the Finder actually copied the file (it may very well be skipping these files). .DS_Stores on the NAS's with resource forks.. maybe that will help you figure out leaky compression Does the file have a data fork? My I suspect these files are actually just old/weird, but the presence of a data fork means it's unlikely the file was ever compressed. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic: App & System Services SubTopic: Core OS Tags:
2w
Reply to File Export from iOS - eventually import too
In some online tutorials there was a way to set the full filename (like Export.csv) In the case of sharing a file, you can give the file a name you choose. Here you are sharing a piece of data, and so the use casen is different. Could you clarify how DTS works now relative to these questions answered here on the forum? Since I did ask for a DTS - does this count as one? Apple's DTS has been providing our usual code level support in the forums as well as via email. We've also lifted the cap of 2 incidents per account per year so developers can ask questions as needed. As a result, other than the medium of communication, there’s really no difference in the support response we’ll provide. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: SwiftUI
2w
Doesn't match the entitlements file's value for the com.apple.developer.driverkit.userclient-access entitlement.
My application will create a virtual touchpad. The problem I encountered is: click on the Product menu, select Archives, then select the Distribute App, then click on Drill Distribution, then click on Distribute, and then a prompt appears: Provisioning profile Mac Team direct Provisioning Profile:com.xxx.xxxdoesn't match the entitlements file's valuefor the com.apple.developer.driverkit.userclient-access entitlement. But My Identifiers Selected the:DriverKit Allow Any UserClient (development) Do I need toRequest a System Extension or DriverKit Entitlement Select Virtual HID in here? https://developer.apple.com/contact/request/system-extension/
1
0
177
2w
Reply to filecopy fails with errno 34 "Result too large" when copying from NAS
All it takes, as you demonstrated, to get copyfile to fail is to feed it a file with a resource fork. Not exactly. Creating that failure required intentionally breaking a compressed file, which isn’t something that should be happening in the wild. That is, I replicated the problem that leads to this error, but I still don't know what/how the scenario is being created in the first place. In regards to the potential compression situation, I'm assuming Finder copying doesn't involve the user or set UF_COMPRESSED? Or does it? Correct, it's just copying the file. It'd be great if Finder shared the same copy engine with the rest of us, at least whatever issues would be consistent system-wide. But I get it…it probably won't ever happen. To be clear here, the isn't here isn't really about the Finder being special- to some extent we DID make the Finder's copy engine available, as that's what FSCopyObject[1] actually does. However, the problem here is twofold: The Finder's copy full copy engi
Topic: App & System Services SubTopic: Core OS Tags:
2w
Reply to DriverKit Entitlement Model Has No Viable Path for Open Source and Community-Maintained Drivers
A free or reduced-cost entitlement path for non-commercial volunteer-maintained drivers If you haven't already, please file a bug asking for the dev-only entitlements to be enabled on free developer accounts, and post the bug number back here. I can't promise it will happen, but it's an interesting idea that I don't think we've really considered. Published approval criteria and timelines so projects can plan accordingly Unfortunately, publishing truly formal criteria is much more difficult than it sounds since, in practice, it's very difficult to come up with a criteria set that EXACTLY covers every reasonable use case while also excluding every possible unreasonable use case... and that assumes we could even come up with every use case. However, on this point: Even if the developer is a professional company, some legacy hardware will go unsupported because of a lack of support from the vendor. Providing a way for users who need access to older hardware would be needed. We understand that the nature
Topic: App & System Services SubTopic: Drivers Tags:
2w
Following up on Feedback Assistant reports
I have filed 27 bug reports against macOS using Feedback Assistant and none have had any sort of follow-up. I'm wondering if anyone at Apple looks at these reports? A few of these involve accessibility features that are not working (for example: speak announcements doesn't work -- and yes, my feedback is much more detailed than doesn't work). I would have thought issues with accessibility would be a high priority for Apple to fix quickly. Another report is that Grapher uses black text on dark gray making it very difficult to see the formula you enter. This should be a one-line code fix. These two, and 25 other bug reports have seemingly been ignored. Several of these reports indicate more than 10 similar reports, yet go unfixed. Leading me back to my opening question -- does anyone at Apple read these reports? I'd like to think I'm helping Apple to deliver a more perfect product but I feel like I'm wasting my time writing detailed bug reports. Is there another way to bring these to Apple's attention?
3
0
612
2w
Invalid Entitlement: Unknown ID
I am attempting to configure appclips, but I am getting this error in App Store Connect. I created an app clips target in my project, I have checked the XCAsset files and it is included when archived and pushed to App Store Connect. In both my parent and my app clips target I've added the associated domains capabilities, with the following associated same domains for both targets: appclips:akin-server-side-staging.onrender.com appclips:akin-server-side.onrender.com applinks:akin-server-side-staging.onrender.com applinks:akin-server-side.onrender.com My server is configured to serve the following json at all permutations of the staging endpoints and prod endpoints for both well known and aasa without well known. Here is one of them: https://akin-server-side.onrender.com/.well-known/apple-app-site-association Here is the JSON it is returning: {applinks:{details:[{appIDs:[8PJ28P9ZZ8.com.ElevatedUnderdogs.akin1],components:[{/:/appClips/referral/venueToUser/*}]}]},appclips:{apps:[8PJ28P9ZZ8.com.ElevatedU
4
0
192
2w
FileManager.replaceItemAt(_:withItemAt:) fails sporadically on ubiquitous items
I’m encountering a strange, sporadic error in FileManager.replaceItemAt(_:withItemAt:) when trying to update files that happen to be stored in cloud containers such as iCloud Drive or Dropbox. Here’s my setup: I have an NSDocument-based app which uses a zip file format (although the error can be reproduced using any kind of file). In my NSDocument.writeToURL: implementation, I do the following: Create a temp folder using FileManager.url(for: .itemReplacementDirectory, in: .userDomainMask, appropriateFor: fileURL, create: true). Copy the original zip file into the temp directory. Update the zip file in the temp directory. Move the updated zip file into place by moving it from the temp directory to the original location using FileManager.replaceItemAt(_:withItemAt:). This all works perfectly - most of the time. However, very occasionally I receive a save error caused by replaceItemAt(_withItemAt:) failing. Saving can work fine for hundreds of times, but then
15
0
337
2w
Reply to FileManager.replaceItemAt(_:withItemAt:) fails sporadically on ubiquitous items
What makes copies slow isn't the writes; it's the reads, since the data still has to be pulled off the disk so it can be sent back to write. That makes sense and does indeed seem to be the reason for the speed after first import (the developer of LibZip said much the same recently when I was asking for more details about how it takes advantage of file cloning). The initial read of the large file takes a while, but after that saving is fast, even on reopening the file (because it is read on open). Anyway, thanks again - this discussion has lead to some nice optimisations in the way I'm working with LibZip as well as working around the save error.
Topic: App & System Services SubTopic: Core OS Tags:
2w
Instruments Malfunction
I’m reporting a severe reproducible issue in Instruments, specifically when using the SwiftUI instrument and opening Show Cause & Effect Graph. What happens: • Instruments becomes extremely laggy/unresponsive • The graph/detail area can turn solid magenta/pink • Memory usage rapidly increases (I observed around 18 GB, 25 GB, and up to 34 GB) • My Mac has crashed/restarted during this, or in other terms, had a kernel panic, where my Mac froze, and everything unresponsive. The Trackpad wouldn't even click. Important detail: • I could not find a generated kernel panic log after the crash/restart. Repro context: • SwiftUI iOS app profiled from Xcode • Trigger is specifically entering Show Cause & Effect Graph • Recordings can be short and still trigger it • Issue is much less severe or absent if I avoid that view What I already tried: • Rebooting • Short captures / fewer instruments • Clearing Xcode/Instruments caches/preferences • Retesting after cleanup • Reinstalling Xcode Is this a known Instruments r
Replies
2
Boosts
0
Views
127
Activity
2w
Reply to Unusually Long "Waiting for Review" Times This Week - Anyone Else?
@App Review The issue is NOT resolved for all developers. I have two apps stuck in Waiting for Review with zero communication: OKIRIZO (Apple ID: 6757417197) - First submitted Jan 10, 2026. Current submission Feb 25. Over 2 months waiting. TidaKitchen (Apple ID: 6759185372) - Submitted ~Mar 11. Still waiting. I have filed THREE support cases with no response: Case 102824913561 (Feb 19) - no reply Follow-up (Mar 4) - no reply Case 102846444484 (Mar 17) - no reply Expedited review request also submitted with no response. Three support cases over one month, all ignored. This is unacceptable for paying Apple Developer Program members. Please investigate immediately.
Replies
Boosts
Views
Activity
2w
Reply to App review process takes long time
I am experiencing the same issue with two of my apps. OKIRIZO (Apple ID: 6757417197) - First submitted January 10, 2026. Current submission from February 25, now waiting 23+ days. I have contacted Apple Developer Support on February 19 (case 102824913561), followed up on March 4, and again on March 17 (case 102846444484). No response to any of these inquiries. I have also submitted an expedited review request with no response. TidaKitchen (Apple ID: 6759185372) - Submitted approximately March 11, also stuck in Waiting for Review. Both are v1.0 initial submissions. No messages, no rejections, no feedback in App Store Connect. Three support cases filed over the past month with zero replies. This is severely impacting our business operations in Okinawa, Japan. Could the App Review team please investigate?
Replies
Boosts
Views
Activity
2w
Reply to CallKit lock screen UI on iOS 26: “slide to answer” text is too faint / hard to read
I've noticed the same contrast issue on iOS 26 with dark wallpapers. This appears to be a Liquid Glass regression — the frosted material doesn't adapt well to certain background luminance levels. Since the slide to answer text is entirely system-managed through CallKit, there's no app-side workaround. I'd recommend filing a Feedback (if you haven't already) under UIKit > System UI with a screenshot showing the low contrast scenario. Referencing the WCAG 2.1 AA contrast ratio requirement (4.5:1 for normal text) in your report might help prioritize it, since this is a core accessibility concern for incoming calls.
Topic: Design SubTopic: General Tags:
Replies
Boosts
Views
Activity
2w
Reply to File Export from iOS - eventually import too
When I rename a file I can't seem to change the extension. For example: when I select the file and change to MyFile.csv - it writes MyFile.csv.txt is there any way to get rid of that .txt extension other than make the user delete it? I mean they could edit from .txt to .csv and macOS asks if they are sure - but I'd like to remove that step. That might be worthy of a feedback...
Topic: UI Frameworks SubTopic: SwiftUI
Replies
Boosts
Views
Activity
2w
File Export from iOS - eventually import too
iOS 15 - iOS 26.x, SwiftUI, Xcode 26.1.1 (rewritten without links) I’m attempting to add the capability to export a file from CoreData. Since ShareLink requires iOS16+, I found an article showing how to create a UIKit wrapper for 'UIActivityViewController' This does work, but I end up with multiple files instead of one. How do I merge this into one file? Note: I don’t think I want to write to the app’s document directory – rather I’d like to allow the user to export to iCloud. Eventually, I’d like to share a list of dates with descriptions and if someone puts a sensitive date in there – I don’t want it to be left in a directory. I would include a warning that the file that they export needs to be handled with care if there are any sensitive dates. Some might consider birthdays as private information, right? I'd also like to be able to name the file - so far when the share sheet comes up, I select Save to Files and it uses a default name of text.txt My next
Topic: UI Frameworks SubTopic: SwiftUI
Replies
6
Boosts
0
Views
320
Activity
2w
Reply to copyfile Sometimes Fails to copy .DS_Store when Copying a Folder But Does Not Report Usable Error
Mystery (partially) solved. I just took a sneak peak at the extended attributes of the .DS_Store file and some have a resource fork (probably the ones that were failing to copy I BET!). So appears to be the same failure we are talking about here: https://developer.apple.com/forums/thread/814076 Can you upload a copy of the .DS_Store file to the bug you filed on this? Also, what's the bug number? Also, are you sure the Finder actually copied the file (it may very well be skipping these files). .DS_Stores on the NAS's with resource forks.. maybe that will help you figure out leaky compression Does the file have a data fork? My I suspect these files are actually just old/weird, but the presence of a data fork means it's unlikely the file was ever compressed. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
2w
Reply to File Export from iOS - eventually import too
In some online tutorials there was a way to set the full filename (like Export.csv) In the case of sharing a file, you can give the file a name you choose. Here you are sharing a piece of data, and so the use casen is different. Could you clarify how DTS works now relative to these questions answered here on the forum? Since I did ask for a DTS - does this count as one? Apple's DTS has been providing our usual code level support in the forums as well as via email. We've also lifted the cap of 2 incidents per account per year so developers can ask questions as needed. As a result, other than the medium of communication, there’s really no difference in the support response we’ll provide. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: SwiftUI
Replies
Boosts
Views
Activity
2w
Doesn't match the entitlements file's value for the com.apple.developer.driverkit.userclient-access entitlement.
My application will create a virtual touchpad. The problem I encountered is: click on the Product menu, select Archives, then select the Distribute App, then click on Drill Distribution, then click on Distribute, and then a prompt appears: Provisioning profile Mac Team direct Provisioning Profile:com.xxx.xxxdoesn't match the entitlements file's valuefor the com.apple.developer.driverkit.userclient-access entitlement. But My Identifiers Selected the:DriverKit Allow Any UserClient (development) Do I need toRequest a System Extension or DriverKit Entitlement Select Virtual HID in here? https://developer.apple.com/contact/request/system-extension/
Replies
1
Boosts
0
Views
177
Activity
2w
Reply to filecopy fails with errno 34 "Result too large" when copying from NAS
All it takes, as you demonstrated, to get copyfile to fail is to feed it a file with a resource fork. Not exactly. Creating that failure required intentionally breaking a compressed file, which isn’t something that should be happening in the wild. That is, I replicated the problem that leads to this error, but I still don't know what/how the scenario is being created in the first place. In regards to the potential compression situation, I'm assuming Finder copying doesn't involve the user or set UF_COMPRESSED? Or does it? Correct, it's just copying the file. It'd be great if Finder shared the same copy engine with the rest of us, at least whatever issues would be consistent system-wide. But I get it…it probably won't ever happen. To be clear here, the isn't here isn't really about the Finder being special- to some extent we DID make the Finder's copy engine available, as that's what FSCopyObject[1] actually does. However, the problem here is twofold: The Finder's copy full copy engi
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
2w
Reply to DriverKit Entitlement Model Has No Viable Path for Open Source and Community-Maintained Drivers
A free or reduced-cost entitlement path for non-commercial volunteer-maintained drivers If you haven't already, please file a bug asking for the dev-only entitlements to be enabled on free developer accounts, and post the bug number back here. I can't promise it will happen, but it's an interesting idea that I don't think we've really considered. Published approval criteria and timelines so projects can plan accordingly Unfortunately, publishing truly formal criteria is much more difficult than it sounds since, in practice, it's very difficult to come up with a criteria set that EXACTLY covers every reasonable use case while also excluding every possible unreasonable use case... and that assumes we could even come up with every use case. However, on this point: Even if the developer is a professional company, some legacy hardware will go unsupported because of a lack of support from the vendor. Providing a way for users who need access to older hardware would be needed. We understand that the nature
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
2w
Following up on Feedback Assistant reports
I have filed 27 bug reports against macOS using Feedback Assistant and none have had any sort of follow-up. I'm wondering if anyone at Apple looks at these reports? A few of these involve accessibility features that are not working (for example: speak announcements doesn't work -- and yes, my feedback is much more detailed than doesn't work). I would have thought issues with accessibility would be a high priority for Apple to fix quickly. Another report is that Grapher uses black text on dark gray making it very difficult to see the formula you enter. This should be a one-line code fix. These two, and 25 other bug reports have seemingly been ignored. Several of these reports indicate more than 10 similar reports, yet go unfixed. Leading me back to my opening question -- does anyone at Apple read these reports? I'd like to think I'm helping Apple to deliver a more perfect product but I feel like I'm wasting my time writing detailed bug reports. Is there another way to bring these to Apple's attention?
Replies
3
Boosts
0
Views
612
Activity
2w
Invalid Entitlement: Unknown ID
I am attempting to configure appclips, but I am getting this error in App Store Connect. I created an app clips target in my project, I have checked the XCAsset files and it is included when archived and pushed to App Store Connect. In both my parent and my app clips target I've added the associated domains capabilities, with the following associated same domains for both targets: appclips:akin-server-side-staging.onrender.com appclips:akin-server-side.onrender.com applinks:akin-server-side-staging.onrender.com applinks:akin-server-side.onrender.com My server is configured to serve the following json at all permutations of the staging endpoints and prod endpoints for both well known and aasa without well known. Here is one of them: https://akin-server-side.onrender.com/.well-known/apple-app-site-association Here is the JSON it is returning: {applinks:{details:[{appIDs:[8PJ28P9ZZ8.com.ElevatedUnderdogs.akin1],components:[{/:/appClips/referral/venueToUser/*}]}]},appclips:{apps:[8PJ28P9ZZ8.com.ElevatedU
Replies
4
Boosts
0
Views
192
Activity
2w
FileManager.replaceItemAt(_:withItemAt:) fails sporadically on ubiquitous items
I’m encountering a strange, sporadic error in FileManager.replaceItemAt(_:withItemAt:) when trying to update files that happen to be stored in cloud containers such as iCloud Drive or Dropbox. Here’s my setup: I have an NSDocument-based app which uses a zip file format (although the error can be reproduced using any kind of file). In my NSDocument.writeToURL: implementation, I do the following: Create a temp folder using FileManager.url(for: .itemReplacementDirectory, in: .userDomainMask, appropriateFor: fileURL, create: true). Copy the original zip file into the temp directory. Update the zip file in the temp directory. Move the updated zip file into place by moving it from the temp directory to the original location using FileManager.replaceItemAt(_:withItemAt:). This all works perfectly - most of the time. However, very occasionally I receive a save error caused by replaceItemAt(_withItemAt:) failing. Saving can work fine for hundreds of times, but then
Replies
15
Boosts
0
Views
337
Activity
2w
Reply to FileManager.replaceItemAt(_:withItemAt:) fails sporadically on ubiquitous items
What makes copies slow isn't the writes; it's the reads, since the data still has to be pulled off the disk so it can be sent back to write. That makes sense and does indeed seem to be the reason for the speed after first import (the developer of LibZip said much the same recently when I was asking for more details about how it takes advantage of file cloning). The initial read of the large file takes a while, but after that saving is fast, even on reopening the file (because it is read on open). Anyway, thanks again - this discussion has lead to some nice optimisations in the way I'm working with LibZip as well as working around the save error.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
2w