“eskimo”

Network framework has significant limitations when it comes to handling UDP broadcasts. We talk about these in TN3151 Choosing the right networking API. If you actually need to use broadcasts, check out my advice in Extra-ordinary Networking > Broadcasts and Multicasts, Hints and Tips. The emphasis there being need. I see a lot of folks using broadcasts for stuff that would be better served by Bonjour service discovery. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Based on your pattern of behaviour on this thread and your other thread, I won’t be responding. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Based on your pattern of behaviour on this thread and your other thread, I won’t be responding. 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. If you post your notary request UUID, we can check to be sure everything seems to be working as expected. 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='821679021, Elacity, /thread/821679, /profile/Elacity'] not APFS - aware of DTS r. 134264492 [/quote] I believe that’s a red herring. See my explanation here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m glad you got this sorted, but I don’t think that this is the right explanation: [quote='883178022, duals, /thread/821552?answerId=883178022#883178022, /profile/duals'] Apple's notary service has a known issue with APFS DMGs (Apple DTS: r. 134264492). [/quote] The notary service should be able to handle both APFS and HFS Plus just fine. That bug, which I mentioned on this thread, doesn’t affect APFS. Rather, it was caused by the developer submitting a UDF disk image. The fix was… well… to not do that. I suspect you were actually being routed to the “in-depth analysis” path — I’ve included my standard explanation of that below — and your resubmission as HFS Plus just happen to coincide with that state being cleared. If you want to confirm this, you could revert back to APFS and see if you continue to have problems. Or not, because there’s nothing wrong with shipping an HFS Plus disk image. But if you do run this test, please let me know how you get along because I’m super curious. Share and Enjoy — Quinn “T

Just a quick update… I’m confidant that we now have a handle on this issue (FB22384135). I can’t offer any concrete details about timelines but, as always, I encourage you to test with the latest betas as we seed them. And in this case that means Xcode betas, because this is an Xcode issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='882769022, h-noto, /thread/819445?answerId=882769022#882769022, /profile/h-noto'] How do we create a persistent CTK token that's not tied to physical smart card hardware? [/quote] Start with the macOS > Persistent Token Extension template, which creates the necessary app extension target along with three subclasses (of TKTokenDriver, TKToken, and TKTokenSession) that you need to fill in. Beyond that, I have some other hints that will help you get started. I can’t include them all here, so please open a DTS code-level support request and I’ll pass them along via that channel. IMPORTANT When you fill in the form for the support request, where is asks if someone told you to contact DTS, enter a reference to this forums thread. That way your request will come straight to me. [quote='882769022, h-noto, /thread/819445?answerId=882769022#882769022, /profile/h-noto'] How should the token session retrieve the private key imported from the PKCS#12 bundle? [/quote] That’s kinda up to you. Most persistent toke

[quote='882763022, VictorPetitjean, /thread/809211?answerId=882763022#882763022, /profile/VictorPetitjean'] I shared a screen recording in the feedback assistant showing this behavior [/quote] Ah, I see that. My advice here is that you create a new bug for this case. That’ll let us treat FB21858319 as the solution for the original problem, and give us a separate ‘handle’ to track this edge [1] case Please post your new bug number. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Well, _more-edge-like- perhaps (-:

Glad to hear you’re making progress. [quote='882788022, markkolan, /thread/821305?answerId=882788022#882788022, /profile/markkolan'] The posts you linked should be official documentation [/quote] If you’d like to request that officially, please file a bug against the docs. It’d be helpful if you called out the specific bits that you found helpful. And if you do file this bug, please post your bug number, just for the record. [quote='882788022, markkolan, /thread/821305?answerId=882788022#882788022, /profile/markkolan'] The entitlement group in the documentation has a unicode zero width space [/quote] Oi vey! I filed my own bug about that [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Actually, three bugs: One against the docs (r. 174003674) Another against the entitlements complier (r. 174003869) And a third one against the Swift complier (r. 174003886) I feel very accomplished (-:

What version of Swift Playground are you using? And is this on Mac or iPad? [quote='821471021, GMacD53, /thread/821471, /profile/GMacD53'] because Playground does not use Xcode as far as I am aware? [/quote] Yes and no. It’s an independent product but, when you submit to App Store Connect, it reuses a bunch of the same infrastructure. Thus it’s not a huge surprise that you’re seeing Xcode in this error message. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

(vfllc has already seen a reply like this via another channel, but I wanted to reply here in case others stumble across this thread.) The forums are primarily focused on code-level issue and, as I explain in this post, this error isn’t something we can help you with here. You’ll have to continue to seek help via official channels. 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. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

A good way to approach this is to run the store-credentials subcommand with no arguments: % xcrun notarytool store-credentials It will then interactively walk you through the login process. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Folks, I’m going to lock this thread because: It’s super old. And it’s obviously become a magnet for spammers. If you want to continue the discussion, feel free to start a new thread in Community > Apple Developers. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com