“file uri scheme”

Thanks for reply, Albert. Interestingly, installation of MacOS 24.6 beta 4 was successful in safe mode on both my Intel iMac and my M1 Max MBP the second time I tried (a day later). Every time I attempted an upgrade, the Mac appeared to re-download the full OS file so not sure a corrupted cached file would explain it; also the bug presented itself on two systens with different processors. I wonder if Apple fixed a bug in the installer overnight. I did post the issue in the Developer Feedback app, and got a request for more information, asking if I was able to install in safe mode (when I had already said that I was not). In any case, all good now. :)

Thanks, Quinn! The first problem is that the entitlements validated flag is not set -- here's the relevant text: code signing info = valid refuse invalid pages kill on invalid pages require enforcement allowed mach-o platform dyld And the codesign result shows that the new app group is not present, just the old one: Executable=/Applications/MyApp.app/Contents/PlugIns/EMPFileProvider.appex/Contents/MacOS/EMPFileProvider [Dict] [Key] com.apple.security.app-sandbox [Value] [Bool] true [Key] com.apple.security.network.client [Value] [Bool] true [Key] keychain-access-groups [Value] [Array] [String] XXXXXXXXXX.com.mydomain.MyApp.Shared [Key] com.apple.security.application-groups [Value] [Array] [String] group.com.mydomain.MyApp [Key] com.apple.application-identifier [Value] [String] $(AppIdentifierPrefix)$(PRODUCT_BUNDLE_IDENTIFIER) ...which is odd because the embedded.provisionprofile inside the .appex lists all three: com.apple.security.application-groups group.XXXXXXXXXX.com.mydomain.MyApp group.com.mydomain.My

removing the script didn't fix for me. the script had been holding it together till now, but something changed recently. Ok — since this sounds like a recent change, it would be helpful for us to get a bug report from you so we can look into this further. It would be helpful if you could detail the exact configuration you've set for this build environment (macOS version and Xcode versions), and a link to a specific build. Once that's filed, please post the FB number here so I can locate your report. — Ed Ford,  DTS Engineer

I presume you looked at implementing code like this, from the documentation: @AppIntent(schema: .system.search) struct ExampleSearchIntent: ShowInAppSearchResultsIntent { static var searchScopes: [StringSearchScope] = [.general] var criteria: StringSearchCriteria func perform() async throws -> some IntentResult { let searchString = criteria.term print(Searching for (searchString)) // ... // Code that navigates to your app's search and enters the search string into a search field. // ... return .result() } } The key type here, ShowInAppSearchResultsIntent, is a clear indication of the intended behavior of showing search results inside of the app. Also, testing your intent in the Shortcuts app is an excellent way to test. Do I need to do AppIntents without the schema and wait until there is a search schema that does not open the app, or should I be using a different schema? What am I missing? It's worth considering the larger picture of what someone does with your intent after the search — in many cases, the

To see what happened here, I used Xcode 26.4 beta 3 to create a new multi-platform app. I added a new file, added an import statement for App Intents, and then copied in the snippet of getting started code from the documentation. Indeed, this fails to compile. That new project's default build setting configuration is: Swift Langage Version: Swift 5 Approachable Concurrency: Yes Default Actor Isolation: MainActor To allow this to compile, I change the Default Actor Isolation build setting to nonisolated instead. This is worth a bug report — please use Feedback Assistant to report it, and post the FB number here so I can follow up on it. — Ed Ford,  DTS Engineer

Thanks for the post. I'm not an expert on that API, not even close to that, so I'm inviting other engineers to jump into this thread and provide their options on the 3 questions. This is a PhotoKit upload asset for background process. As noted the extension processes uploads only while enabled. Disable the extension when a person signs out or disables cloud sync in your app. https://developer.apple.com/documentation/PhotoKit/uploading-asset-resources-in-the-background The PHAssetResourceUploadJobChangeRequest.createJob(destination:resource:) API is designed to hand off the entire upload process to a system daemon. Because the system daemon manages the network connection out-of-process (to preserve battery and allow the extension to be suspended or terminated), it imposes specific architectural constraints on how your backend must receive the data. Here is the limitations are documented https://developer.apple.com/documentation/photos/phphotoserror-swift.struct/limitexceeded Are you hitting any? I believe the

The ‘strongly discouraged’ guidance only applies to directly using the clonefile function on directories, because it ties up the filesystem in ways that can be detrimental to the overall system health. On the other hand cloning directories recursively with copyfile is perfectly fine, because copyfile internally only calls clonefile on each file separately. Hope that helps clarify things.

Thanks for the post. This is extremely interesting, but I'm sure is frustrating as well. Are you able to complete the installation if you boot to safe mode? It seems it is almost certainly a corrupted OTA (Over-The-Air) delta update file cached on your system? The process terminates with Failed to prepare the software update or An error occurred while downloading the selected updates.”? When a beta update fails halfway or downloads a corrupted delta package, macOS will continuously try to use that broken file every time you hit Update, resulting in the same error. Can I ask you both to please create a bug for this issue? 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? Thanks!! Albert Pascual
  Worldwide Developer Relations.

Thanks for the post and sorry that I have missed it, somehow went over all my filters, no excuses for me, thanks for your patience. Doing a simple request returns correct JSON with curl -v https://app.myloft-stage.com/.well-known/apple-app-site-association But with a simple user-agent we get a security issue: curl -I -A AASA-Bot/1.0 https://app.myloft-stage.com/.well-known/apple-app-site-association So the servers can’t not access the file. When you test the URL in your browser or via cURL, you are using a standard User-Agent. When Apple's CDN fetches the file, it uses a specific bot User-Agent and originates from Apple's IP subnets. Check your server/WAF access logs for requests to the /.well-known/apple-app-site-association path. Look for blocked requests or requests returning a 403/Challenge status for the AASA-Bot User-Agent. Whitelist all User-Agent and IPs in your firewall rules for that specific path. When all that is done, everything will start working in a few hours. Albert Pascual


Hello @Highmore and @John24, Could you please attach a JSON version of any crash reports (.ips) to your thread? Please see Acquiring crash reports and diagnostic logs for details. Alternatively, you could also open a Bug Report via Feedback Assistant and attach a sysdiagnose log there. Bug Reports allow you to upload artifacts with private information if necessary, and provide you with feedback status updates as progress is made on issues. 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? Let me know if you'd like to know more, Richard Yeh  Developer Technical Support

It seems like this is an enhancement request. If you'd like us to consider adding the necessary functionality, please file an enhancement request using Feedback Assistant. Once you file the request, please post the FB number here. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.

Quinn- A user was reporting the crash which I could not reproduce locally. We are both running macOS 26.3 right after it came out (I upgraded to macOS 26 mostly because of this- rounded corners are annoying/wasteful, just saying). Code is on GitHub (https://github.com/com-entonos/Desktop-Icon-Manager) in particular ViewController.swift, line 114. This works for the user. The previous version of that file crashes at start for the user. The way the code crashed I could not explain (it was in a routine it should not be possible to reach at startup) unless there was UserDefaults value that changed. I had the user use 'defaults delete ...' to delete the relevant plist file, so I really don't know what the state of his machine was. If he had 'Automatically restore at start' checked, it would explain it. Default is not checked. He was at an university so who knows what IT does... Good luck.