“eskimo”

I don’t have any info to share beyond what you can see in Feedback Assistant: Your bug, FB13845934, remains unresolved. 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 very few. Most of

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

[quote='879421022, Arihant_Marwaha, /thread/818407?answerId=879421022#879421022, /profile/Arihant_Marwaha'] its resolved now [/quote] Cool. Thanks for closing the loop. And just FYI, I suspect you were being hit by an infrastructure outage yesterday. Based on the posts at the end of this thread it seems to be resolved. It’s just unfortunate that you happened to see it after updating to the latest beta. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

How reproducible is this crash? Can you reproduce it reliably in your office? Or are you chasing bug reports coming in from the field? Also, if you put that code into a small test project and run it with the standard memory debugging tools, does it crash there? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Jweeces, I don’t think you’re hitting exactly the same problem as Tonnew. Rather, I think you were being hit by an infrastructure outage yesterday. Based on the posts at the end of this thread (10 pages, wow!) it seems to be resolved. Reply back here if you continue to have problems. @Tonnew , Sorry I missed your thread the first time around (I suspect I was out of the office). I you continue to have problems with this, please post an update here and I’ll take a look. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It seems like there was a major infrastructure outage yesterday. Based on the posts at the end of this thread (10 pages, wow!) it seems to be resolved. Reply back here if you continue to have problems. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. [quote='818322021, Chandrashakar, /thread/818322, /profile/Chandrashakar'] Is this the in-depth analysis path … ? [/quote] It certainly looks that way. [quote='818322021, Chandrashakar, /thread/818322, /profile/Chandrashakar'] for new accounts [/quote] It can be triggered by a variety of criteria. [quote='818322021, Chandrashakar, /thread/818322, /profile/Chandrashakar'] Any ETA … ? [/quote] Usually this clears in a few days. If you remain stuck after a week, lemme know by replying here. [quote='818322021, Chandrashakar, /thread/818322, /profile/Chandrashakar'] workaround? [/quote] No. In my ex

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. [quote='818398021, grad13, /thread/818398, /profile/grad13'] Notarization submissions stuck “In Progress” for 5+ days [/quote] In my experience five days is longer than normal for submissions that hit the “in-depth analysis” path. However, it’s not completely unheard of. If you remains stuck after a week, please reply here with: The UUID and creation date of your earliest request. The UUID and creation date of your latest request. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Two bits of administrivia: It looks like nilsn26 started a similar thread on Swift Forums. nilsn26, It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This is for Team ID J________H, right? If you click that Manage button, what do you see? For example, here’s what I see when I do that for my individual test team: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

benihayashi, Let’s discuss this over in your specific thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Based on the above I tried reproducing this with a test project. And lo! it’s trivial to reproduce: I started with Xcode 26.3 without the Metal Toolchain 26.3 component installed. I created a new project from the iOS > App template. In the General tab of the target editor, I removed the Mac (Designed for iPad) destination. And added the Mac (Mac Catalyst) destination. I selected My Mac (Mac Catalyst) as the run destination. I chose Product > Build; the project built without any warning. In Xcode > Settings > Components, I installed the Metal Toolchain 26.3 component. I chose Product > Clean. And then Product > Build. I now see a build warning: ld: warning: search path '/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.3.7003.10.hJke6J/Metal.xctoolchain/usr/lib/swift/maccatalyst' not found Given the above, I can only conclude that this is a bug. I did some digging and was unable to find any more backstory (for example, I thought that someone might’ve filed this