“eskimo”

I don’t think we’ll be able to help you here on the Apple Developer Forums. Our focus is on helping developers use Apple APIs and tools to create products for Apple platforms. We’re not really set up to help folks use Apple products, and that includes advanced use cases like yours. You might have better luck asking this question over in the Apple Support Community, run by Apple Support, and specifically in the Business and Education topic area. If that doesn’t pan out, I recommend that you contact Apple Support directly. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Well, it’s never actually calm here in DTS, but it’s certainly less busy than it is in the lead up to WWDC (-: I re-read your initial post and, honestly, much of this would be better served by one or more bugs against the documentation. Lemme explain why. DTS’s goal is to help developers use Apple APIs and tools to create products for Apple’s platform that work today and in the future. As part of that we regularly have to offer opinions as to what’s an API and what’s an implementation detail. In many cases that’s obvious, but it’s not always so. Your original post is full of such questions. Those are hard to answer in general, and especially hard to answer in the abstract. For example, let’s consider your question about the correlation between evaluatedDomainState and stateHash. If you wrote a question like: I have an app that fetches evaluatedDomainState and has stored the result in my preferences. I want to upgrade it to use stateHash, so I need to know if those values are comparable? then that’s something

AFAIK there’s no documentation at the level of detail you’re asking about, so about the only thing that you can be certain of is that: When you launch a sandboxed app, its app container will be set up before any of the app’s code runs. When you relaunch a correctly signed [1] sandboxed app, it will be able to access the contents of its app container. The same logic also applies to app group containers. Modern versions of macOS work to ensure that containers are only accessible to the corresponding app. Again, the exact mechanism used for this isn’t documented, but the developer impact is covered by a couple of WWDC videos. See the app container protection and app group container protection links in Trusted Execution Resources. [quote='851946021, 0m3s1k6, /thread/851946, /profile/0m3s1k6'] while separately preventing subsequent application-managed writes inside that container [/quote] There’s no support for anything like that. You might be able to construct something using an es_new_descendants_client ES clien

[quote='910456022, MineaVoiceDev, /thread/851802?answerId=910456022#910456022, /profile/MineaVoiceDev'] If your time and the rules of your role allow it, would you be willing to help us further? [/quote] DTS’s role here at Apple is to help developers with technical issues related to Apple’s APIs and tools. And some Apple developer focused services. Oh, and we also support accessory developers. We are, as you might imagine, quite busy (-: And given all of that, we can’t help with this sort of one-on-one consulting work. [quote='910456022, MineaVoiceDev, /thread/851802?answerId=910456022#910456022, /profile/MineaVoiceDev'] a recommendation for a suitable specialist [/quote] Sorry, I can’t help you with that one either. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

would you recommend investigating the URL Filter Provider or Screen Time content-filter approach described in TN3134? This is a decision you’ll have to make for yourself. Each mechanism has limitations, and you have to trade off between them. Notably: The content filter Screen Time support is limited to child Apple Accounts. The URL filter mechanism only supports filtering URLs, so it doesn’t affect non-HTTP traffic. Also, if the app doesn’t use Apple’s preferred networking APIs, it has to opt in to URL filtering. ps 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

[quote='910471022, vm_install_notes, /thread/852113?answerId=910471022#910471022, /profile/vm_install_notes'] If a controller runs as a launchd job with AbandonProcessGroup=false, does job-death cleanup cover a worker … [/quote] The documented behaviour for that is pretty clear. The launchd.plist man page says: AbandonProcessGroup When a job dies, launchd kills any remaining processes with the same process group ID as the job. Setting this key to true disables that behavior. You specifically asked about a potential race condition, and my take on that is that it should work as documented and, if it’s not, then that’s a bug and you should file it as such. Keep in mind that, if your launchd job spawns a child process, there’s nothing stopping that from changing its process group, meaning that it won’t be killed via this mechanism. If your goal is to guard against that, you’ll need something much more heavy-handed, like an es_new_descendants_client ES client. [quote='910471022, vm_install_notes, /thread/852113?an

So, just to be clear, you ‘own’ these hotspots, right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I recommend that you file your own bug about this. Once you do, please post your bug number, just for the record. IMPORTANT Make sure to attach a sysdiagnose log to your bug report. This should be triggered on the device having the problem immediately after seeing the problem. See our Bug Reporting > Profiles and Logs for more about sysdiagnose logs. Note that yyy07’s bug FB24755993 landed in the right place but it’s not making the progress I would like, which is why I’ve recommended that you file your own bug. @yyy07, Please check Feedback Assistant for a recent update about FB24755993. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’d like to start by getting a better understanding of the context here. Please post an example crash report. See Posting a Crash Report for advice on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Most of your questions are about App Review policy. I don’t work for App Review and can’t give you definitive answers about their policy. If you need that, I suggest you contact them directly. I do have some technology-focused answers though: [quote='852292021, ymbg, /thread/852292, /profile/ymbg'] Are Finder Sync extensions … recommended for these use cases? [/quote] No. Finder Sync extensions are intended to be use to manage syncing the file system with a cloud-based file store. If you try to use them for other tasks, you inevitably run into problem. If you review the various threads with the Finder Sync tag, you’ll see a bunch of cases where developers who’ve not followed this advice have come a cropper. [quote='852292021, ymbg, /thread/852292, /profile/ymbg'] Are … Accessibility APIs … recommended for these use cases? [/quote] The docs specifically call out that accessibility APIs aren’t supported by App Sandbox. [quote='852292021, ymbg, /thread/852292, /profile/ymbg'] Are … macOS Services … recommended f

This is tied to the second of the two issues (FB24791716) being discussed here. [quote='852247021, pajp_fsc, /thread/852247, /profile/pajp_fsc'] I reported it to Apple as FB25121799 [/quote] Thanks. Internally that’s been dup’d to the same ‘lead’ bug as FB24791716. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='852213021, vishalsehgal, /thread/852213, /profile/vishalsehgal'] Our understanding is that this is because the method is declared mutating [/quote] Yes, but that’s not really the main point. Rather, the withUnsafeMutableBytes(_:) call has to pass a mutable pointer to its closure and it can’t tell whether that closure is or isn’t going to mutate the bytes. Thus it must necessarily ensure that the bytes are mutable, and hence it triggers the CoW. [quote='852213021, vishalsehgal, /thread/852213, /profile/vishalsehgal'] we would also like to confirm that withUnsafeMutableBytes(_:) … is the intended long-term API and isn't expected to be deprecated in the same way. [/quote] I don’t think it’s going away any time soon, but it’s fundamentally unsafe and thus not something that we encourage folks to use. Swift is moving towards a world where this sort of low-level access is both efficient and safe [1]. It’s doing this via the Span type (and its variants, like MutableSpan, RawSpan, and so on). Notably, these b

If you have an NSArray, you have to use NSArray methods to access the elements. For example: use framework Foundation set s to current application's NSString's stringWithString:Hello Cruel World! set a to s's componentsSeparatedByString: (a's objectAtIndex:1) as string -- -> Cruel Here I’m using the -objectAtIndex: method. [quote='852189021, danieldlds, /thread/852189, /profile/danieldlds'] I have looked for AppleScript documentation on Apple Developer but can only find documents related to the scripting bridge. [/quote] Most of the AppleScript documentation is in the Documentation Archive )-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

vshuraeff, This thread is about notarytool crashing, resulting in notary requests that show up as In Progress for about 12 hours and then disappear. If your requests are still around after a day, it’s likely that you’ve hit the additional analysis path. For my take on that, see my initial reply on this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

There seems to be a significant compatibilility issue between Swift Playground and iPadOS 27 )-: See this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com