“eskimo”

There are a bunch more factors in play here, including: For Macs with a battery, whether it’s connected to mains power or not. Various preferences in System Settings > Battery, and specifically those under Options. Lots of wacky options under pmset (see the pmset man page for more). But these are all implementation details. From an API perspective, launchd doesn’t guarantee anything about the power state of the system when it starts your job based on StartCalendarInterval. Usually daemons aren’t expected to interact with the user, and thus it doesn’t really matter what the UI state of the system is when the system starts your job. To offer more specific guidance here, I’d need to know more about what your job does. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

What Albert said plus… Some managed capabilities are granted to a specific App ID, while others are granted to your team as a whole. My experience is that the Multicast Networking capability is always granted to your team, so you can use it in any app from that team. And, presuming that you’re working in Team ID H________3, our records show no sign of it deviating from this standard practice. [quote='814969021, idrachman, /thread/814969, /profile/idrachman'] now multicast entitlement is no longer provisioned. [/quote] What do you mean by that? Is Xcode failing to build your app? Or are is your app failing to send or receive multicasts? If it’s the later, be aware that the vast majority of such problems are not tied to the Multicast Networking capability, but rather are caused by code-level problems. I have a bunch of advice about that in Extra-ordinary Networking > Broadcasts and Multicasts, Hints and Tips. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo

[quote='814949021, ghutchis, /thread/814949, /profile/ghutchis'] How can notarization work for macOS 14 and 26, but not for macOS 15? [/quote] That’s not what’s happening here. Notarisation has worked, but your app is failing to pass Gatekeeper. This is actually pretty common. Notarisation and Gatekeeper are separate subsystems, and notarisation is necessary but not suffiient to pass Gatekeeper. It’s less common for this to vary by macOS version, but I’ve certainly see that before. You can find my general advice on this topic in Testing a Notarised Product. Specifically, by setting up a macOS 15 VM you can test this for yourself, which has a couple of benefits: It shortens your debugging cycle for this specific issue. It’ll help you avoid problems like this in the future. Finally, when it comes to debugging this issue I have a bunch of advice in Resolving Trusted Execution Problems. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + app

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. 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='814937021, JimWu01, /thread/814937, /profile/JimWu01'] 1- … but 16+ hours with zero feedback seems excessive. [/quote] My experience, based on reports I’ve seen here in the forums, is that when you hit the in-depth analysis path it can take a day or two to clear. I generally don’t bother investigating issues like this until a week has passed. [quote='814937021, JimWu01, /thread/814937, /profile/JimWu01'] 2- Is there any manual configuration Apple needs to do on their end to unblock my team for notarization? [/quote] No, that’s a different issue. [quote='814937021, JimWu01, /thread/81493

[quote='815061021, alyme, /thread/815061, /profile/alyme'] iOS 19/iPadOS 19 [/quote] There is no iOS 19 O-: You can assume that your playground will be run on a released version of iPadOS 26 / macOS 26 [1]. AFAICT the fine print doesn’t specify what type of device will be used for testing, other than to confirm that on-device intelligence will be available [2]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] See my response here to the equivalent question from last year. [2] See this thread.

Do this: Launch Xcode 26.3rc. File > New > Project. At the top, select iOS. In the main list, select App Playground. Complete the workflow from there. Good luck with your submission! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Regarding your first question, I see that you found an older thread about this and my advice is that folks focus the discussion there. Regarding your second, this is a common question and I don’t have any answers for you )-: If that changes, I’ll post on update in this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='815002021, lijiaxu, /thread/815002, /profile/lijiaxu'] could that violate the rules or lead to rejection? [/quote] I’m not aware of any specific prohibition against this, but my advice for questions like this is always the same: Read the fine print! Specifically, these two pages: Developer > Swift Student Challenge > Eligibility and requirements Developer > Swift Student Challenge > Terms and Conditions Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s focus this discussion on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

@Joeljiangjiang, what @eskimo said. Here is my feedback as a reference. Please make one and if you're willing share your ask here so I can update mine too. In short, I want both a diagnostic, and some new properties associated with that memory pressure diagnostic. FB9972410 (MetricKit: Capture memory usage at time of jetsam and report as diagnostic) April 2022 While the memory metric is insightful combined with the exit metrics, it would be even more powerful to know the memory footprint at the time of jetsam pressure exit. This would allow one to look at the memory footprint and really evaluate if it is worth investigating, or if the footprint is so low and just the system was memory hungry because of some foreground app. For example, if the average suspend memory was 38 mb, but there was one instance of 150 mb, it would be good to see that one getting jetsam'd but the others not. Then we know we have an outlier and something wasn't released upon transition to background and it is time well spent to

[quote='875131022, IHadToChooseAUserNameAndIdidntWantTo, /thread/809959?answerId=875131022#875131022, /profile/IHadToChooseAUserNameAndIdidntWantTo'] Are there public APIs to assess notarization? [/quote] That’s tricky, because it depends on your definition of API. The codesign tool has a --check-notarization operation that does that. See Testing a Notarised Product and the codesign man page. While that’s documented, I’m not a fan of using command-line tools as APIs. The code signing requirement language has the notarized constraint. That’s not documented where it should be but it’s debatable whether that’s just because the parent document is stuck in the Documentation Archive. Annoyingly, an equivalent constraint has not been added to the LightweightCodeRequirements framework. If you think that’d be useful, I encourage you to file an enhancement request for it. And if you do, please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple

Hmmm, that’s really hard to read )-: Please repost it using code blocks for the preformatted text. See tip 5 in Quinn’s Top Ten DevForums Tips for info on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I wanted to shared a quick update on FB21858319. I figured you’d appreciate that given all the work you put in to help isolate it (-: My experience is that Apple is pretty good about fixing local network privacy problems like this one. The critical factor is reproducing the problem, which is why I’ve been so happy to get your cooperation here on this thread. Based on our preliminary analysis of your bug, we think we know what’s going on here. I’m going to offer a little insight into that below, but first I want to set some expectations. Understanding the problem isn’t the same as fixing it. I can’t offer any concrete timeline as to when a fix for this problem will be released. However, when we start seeding a beta release that contains the fix, you should be notified via Feedback Assistant [1]. As to what’s actually happening here, lemme explain a bit about how local network privacy works. As described in TN3179, the local network privacy state on macOS is per user. However, macOS’s networking stack is global