“eskimo”

What you have there is a JSON crash report. The simplest way to get a human readable crash report from that is to save it to disk with the .ips extension and then Quick Look it in the Finder. Having said that, just that small snippet is enough to see that this isn’t a jetsam event: termination : {…,code:11,namespace:SIGNAL,indicator:Segmentation fault: 11,…}, Your app crashed due a memory exception. Now, that could be caused by a memory allocation failure, but you need some evidence before coming to that conclusion. I recommend that you start at the top with Diagnosing issues using crash reports and device logs. Or if you want to post the crash report here, I’d be happy to take a look. Posting it is a bit tricky, and see Posting a Crash Report for specific advice on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Just to set expectations, I’m unlikely to spontaneously update this thread if and when we start seeding a fix. vince-zheng should be notified if and when that happens, and it’d be nice if they posted an update here. But if you don’t want to rely on them, you can file your own bug about this, asking that it be marked as a duplicate of of our internal bug (r. 175178722). That way our bugs system will notify you if and when there’s a fix. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='889992022, p.hackett7, /thread/828859?answerId=889992022#889992022, /profile/p.hackett7'] Yes i have various pre-existing feedback [/quote] OK. What are the bug numbers? [quote='889992022, p.hackett7, /thread/828859?answerId=889992022#889992022, /profile/p.hackett7'] the long standing case we have raised about this is 100926273318 [/quote] FYI, that’s not a bug number. It looks like a case number with Apple Support. Which brings me back to my earlier point, which this issue isn’t really something we can help you with on the developer forums. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='889961022, unni0786, /thread/822908?answerId=889961022#889961022, /profile/unni0786'] Here is the Apple reference link [/quote] Those describe the standard keychain access group entitlements. The specific entitlements are documented in Sharing access to keychain items among a collection of apps, namely: keychain-access-groups application-identifier (or com.apple.application-identifier on macOS) com.apple.security.application-groups [1] All of these entitlements are tied to your team: Values in keychain-access-groups must be prefixed by your Team ID. The value in application-identifier is your App ID, and the App ID prefix is either your Team ID or a unique value assigned to your team. You can only iOS-style app group IDs, starting with group., that are assigned to your team. None of them grant access to Apple-only keychain access groups. And, notably, none of the documents you referenced mention com.apple.managed-keychain, which makes sense because, again, AFAICT, it isn’t actually a thing. [quote='88

The short answer here is “No.” I pinged the Virtualization team about this, and learnt some fascinating facts about how it works under the covers, but that doesn’t help with this problem. The Virtualization API is very high-level, and thus there’s not a lot wiggle room for you to explore improvements. The speed is likely to be determined by the size of the guest’s RAM, and a few seconds is certainly expected. Is that inline with your “taking a lot of time” comment? Or is a way more than that? Also, it’d definitely be worthwhile filing a bug about this. It seems likely that there’s stuff we could do to speed things up. If you do file a bug, there’s a few things I recommend that you do to improve its chances of gaining traction: If you have the time, try to reproduce the issue with Virtualization sample code. That’ll confirm that the bottleneck is in Apple stuff, and unrelated to your code. Then attach the tweaked sample to your bug. That’ll give us a clear understanding of your configuration. If you can’t do t

[quote='828775021, Tianqiw, /thread/828775, /profile/Tianqiw'] Is preferNoProxies guaranteed to bypass PAC‑selected explicit proxies … [/quote] No. The clue is in the name. It says prefer, not something like disable. You can learn more about this from the doc comments. Annoyingly, you have do a bit of digging. The official docs (Swift, C) don’t capture this subtlety, but the doc comments for nw_parameters_set_prefer_no_proxy in are better. They say: * Set to true to attempt connections without using proxies, only using any configured proxies if the connections * cannot otherwise be completed. Defaults to false. Note that “if the connections cannot otherwise be completed”. So, regardless of your specific situation, preferNoProxies is not guaranteed to disable proxies. As to what’s going on in your case, I’m not 100% sure. First things first, let’s determine if your Network Extension context is relevant. If you disable your NE and create a small test app and have it run a connection with preferNoProxies, does

[quote='889830022, thesayynn, /thread/828533?answerId=889830022#889830022, /profile/thesayynn'] I sent the feedback request a while back; its FB22596726 [/quote] OK. I took a look and there’s nothing for me to report on that front, other than that it’s landed with the right folks. Note If you’ve already filed a bug it saves some time if you include it in your post. See Quinn’s Top Ten DevForums Tips for this and other titbits. [quote='889830022, thesayynn, /thread/828533?answerId=889830022#889830022, /profile/thesayynn'] I was just hoping i could talk to the FSKit … engineers directly … [/quote] FSKit engineers do swing by the forums on occasion, but I can’t offer any timeline. Oh, except that next week there’s a File Systems Q&A, and they’ll certainly be here for that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Is this an actual crash? Or are you being jetsammed? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Your questions aren’t really things I can answer. Forums is primarily focused on code-level questions, and given that this issue is affecting Apple apps like Preview, it’s clear that none of your code is involved. My advice is that you file a bug about it, making sure to include a sysdiagnose log that you triggered during the delay. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

DevForums is primarily a place to help third-party developers with their API level questions, so… [quote='828859021, p.hackett7, /thread/828859, /profile/p.hackett7'] Is there any chance to get this handling updated … [/quote] None of your code is involved here, right? If so, then the best way to request a change to the Apple side of things is to file a bug in Feedback Assistant. Please post your bug number, just for the record. ps Thanks for applying the GSS tag. Its tag landing page has been very empty in recent years [1], so it’s glad to have something there again. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Due to a misfeature in the forums, the tag landing pages only show threads that are newer than a certain time limit. I hope to get that fixed at some point (r. 175332842).

Just for the record, here’s a link to the thread you referenced. [quote='828858021, enjora-sh, /thread/828858, /profile/enjora-sh'] Quinn's 827096 reply describes in-depth analysis for new teams clearing in a day or two. [/quote] What I actually wrote was: [quote='888752022, DTS Engineer, /thread/827096?answerId=888752022#888752022'] This state usually clears in a day or two. [/quote] which is significantly less absolute (-: [quote='828858021, enjora-sh, /thread/828858, /profile/enjora-sh'] Is there a known long-tail beyond that window [/quote] Yes, which is why I wrote this: [quote='888752022, DTS Engineer, /thread/827096?answerId=888752022#888752022'] If a week passes without any progress … [/quote] [quote='828858021, enjora-sh, /thread/828858, /profile/enjora-sh'] is there anything a team can do … rather than waiting passively? [/quote] No. Which is why I wrote: [quote='888752022, DTS Engineer, /thread/827096?answerId=888752022#888752022'] My advice here is that you [simply] wait. [/quote] [quote='82885802

Ah, cool, that’s exactly what I was looking for. I had a look at the origin of that message and it’s interesting. Obviously NSMetadataQuery was designed for a run loop world, with the queue support added later on. So this check has to handle both cases. The logic looks something like this: if not started then ok = true else if we have a queue then ok = NSOperationQueue.currentQueue is equal to that queue else … the run loop case … end if So, if you’ve assigned a queue then you get that message based on the result of the currentQueue class property. Which means that your overall conclusion is correct: If you want to change properties on the fly, bounce to the queue and do the work there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Yep. FB22823075 has found it’s way to the right people but there’s no fix yet. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='889746022, Fushj, /thread/783701?answerId=889746022#889746022, /profile/Fushj'] The bug number is FB22904017. [/quote] Thanks! [quote='889746022, Fushj, /thread/783701?answerId=889746022#889746022, /profile/Fushj'] Does has any way to get all your articles like above? [/quote] No, but more because an accident of history than any good reason. We’ve recently been talking about this over in Cannot access profile page of individual DTS engineers. Having said that, most of these posts are linked to from the various Resources posts that are pinned to the top of various topics, subtopic, and tags. For example, Notarisation Resources has links to a bunch of my posts, and it’s pinned to the Code Signing > Notarization subtopic and the Notarization tag. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Are you running out of virtual or physical memory? Because the symptoms you’ve described suggest that you’re hitting the virtual limit. Kevin has been talking to a different developer about that subtlety in this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com