“file uri scheme”

@HolgerGrauslund Thank you for your post. Unfortunately, I am unable to discuss other individuals’ bugs or timelines regarding an issue publicly. Additionally, I am uncertain if you are experiencing the same issue. I recommend creating a new thread and providing as much information as possible, including crash files, sysdiagnose results, and a focused project that reproduces the issue. This information will assist engineers in identifying the issue you are encountering. Thank you for your understanding. Albert Pascual
  Worldwide Developer Relations.

Hi there! That is certainly not expected – could you please file a feedback with us, including model, OS version and sysdiagnose from your iOS device? Thanks, Kacper

I have same problem with Xcode 26.3 Bun on Xcode 16.4 - Download Container worked User Info: { DVTErrorCreationDateKey = 2026-03-11 14:49:00 +0000; NSURL = file:///Users/alexander/Developer/..../AppData/Library/SplashBoard/Snapshots/; } -- The specified file could not be transferred. Domain: com.apple.dt.CoreDeviceError Code: 7000 User Info: { NSURL = file:///Users/alexander/Developer/..../AppData/Library/SplashBoard/Snapshots/; } -- The request from the client is missing one or more required fields: A valid filename cannot end in a path separator character Domain: com.apple.dt.remoteservices.error Code: 11015 -- System Information macOS Version 15.7.4 (Build 24G517) Xcode 26.3 (24587) (Build 17C529) Timestamp: 2026-03-11T17:49:00+03:00

Thanks for the help. I put the zipped application and the zipped log file on GitHub as a pre-release for my app. They are here: https://github.com/hasii2011/umldiagrammer/releases/tag/0.3.0 Code sign command: codesign --sign ${IDENTITY} '--force --timestamp --options=runtime <.so or .dylib to sign> Verification Command /usr/sbin/spctl -vvvv --assess --type exec /Users/humberto.a.sanchez.ii/PycharmProjects/umldiagrammer/dist/umldigrammer.app

I’m not sure what’s going wrong here but I have a couple of diagnostics tests for you to run. Both require you to get your file provider started. Once you have that: Use launchctl procinfo to check whether the process has the entitlements validated flag set. App Groups: macOS vs iOS: Working Towards Harmony has an explanation of how to do this. Use codesign to check the entitlements of the running process: % codesign -d --entitlements - PID where PID is the process ID. What do you see? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I've done a lot more work on this, and I have the impression that this is a bug in macOS, at least on 12 and 13 Intel. #include #include #include #include #include #include // used for debugging apple pointer issues, see // https://bugs.kde.org/show_bug.cgi?id=517304 #define DEBUG_ENV // On Darwin there's this secret fourth argument, 'apple'. // That's kind of like a cut down obfuscated version of auxv. // For the moment we only support the first entry, executable_path= int main(int argc, char *argv[], char *envp[], char *apple[]) { char *pargv = calloc((PATH_MAX+1), sizeof(char)), *pappl = calloc((PATH_MAX+1), sizeof(char)); int i; for (i = 0; envp[i]; i++) { #if defined(DEBUG_ENV) fprintf(stderr, apple-main-arg: i %d &envp[i] %p envp[i] %sn, i, &envp[i], envp[i]); #endif } #if defined(DEBUG_ENV) fprintf(stderr, 2 slots after envpn); fprintf(stderr, apple-main-arg: i %d &envp[i] %p envp[i] %sn, i, &envp[i], envp[i]); fprintf(stderr, apple-main-arg: i %d &envp[i] %p envp[i] %sn, i+1,

Thanks for filing FB22189729. [quote='879085022, DTS Engineer, /thread/817488?answerId=879085022#879085022'] I’m going to talk to some colleagues [/quote] Based on that discussion, I think I’m gonna let my original recommendation stand, that is, add a dummy use of Subprocess within your app. It’s a bit kludgy, but it’ll get the job done. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

That message corresponds to errSecCSInvalidObjectRef (-67071). That’s an obscure one. I’ve been supporting Mac coded signing for almost a decade and I’ve never seen it before. Well done! [quote='818406021, hasii2021, /thread/818406, /profile/hasii2021'] Can't figure out how to post the log file. [/quote] You can post log files as text attachments. I have info on how to do that in Posting a Crash Report. Its focus is on crash reports, but the process for posting a text attachment is the same in both cases. However, the notary log is unlikely to help here because, as you say, the app notarises successfully. Rather, this is a code signing error on your local Mac. [quote='818406021, hasii2021, /thread/818406, /profile/hasii2021'] when I try to verify the signature I get the above error. [/quote] How are you doing that? Normally I’d verify a signature like so: % codesign -v --deep --strict /path/to/my.app Is that what you’re doing? As to the potential causes of errSecCSInvalidObjectRef, there are

My general approach for problems like this is to set up a VM that’s never seen my product before and then use that VM to test various user-level sequences. For example, I might install version N of the app, check that screen capture works, then install version N+1, and then check that it continues to work. The advantage of doing this on a VM is that you’re starting from a fresh machine and you can save and restore snapshots for your various tests. If your product passes those tests, and thus works in general, this becomes a question of what’s happening on specific user machines to cause the reported issue? That’s a much harder question to answer. macOS has lots of flexibility — with the user able to install and remove apps at will, install multiple copies of your app, and so on — and that flexibility causes serious challenges for TCC. There’s no easy way to map from specific symptoms back to the root cause. However, it’s unlikely to be your app’s issue. I mean, there’s nothing you can do at the code level to

Hello SuneethaR, Apologies, the tintColor of a view controller's tab bar item refers to the color of its title and image, not the grey background that appears when an item is highlighted through selection. There's no supported way for you to customize it with the APIs currently available. 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? We also recommend you move away from the Appearance APIs and reduce your use of custom backgrounds when customizing navigation elements. Let me know if you'd like to know more, Richard Yeh  Developer Technical Support