“eskimo”

[quote='838853021, ges1983, /thread/838853, /profile/ges1983'] is there something off on Apple side? [/quote] Probably not, in that when there’s a widespread failure of the notary service this section of the forums tends to light up like a Christmas tree. Can you elaborate on the failure mode here? Are things failing to upload? Or uploading just fine and then getting stuck in In Progress? Or completing with an error? 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 additional 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

[quote='898458022, Nickkk, /thread/799898?answerId=898458022#898458022, /profile/Nickkk'] Already the mention of an unspecified magic user default tells me that I shouldn't bother messing with this. [/quote] To be clear, that’s not an Apple user default, but a VirtualBuddy one. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='898440022, Bojie_Lv, /thread/838513?answerId=898440022#898440022, /profile/Bojie_Lv'] Could you provide us with a sample code for Wi-Fi Aware using Socket? [/quote] Well, I dodged that question earlier, and for good reason. My understanding is that there’s no good way to combine Wi-Fi Aware and BSD Sockets. However, before I send you off to file an ER for that, I’m gonna double check… Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m gonna recommend that you start a new thread with this question. This thread was about OSLog, and I think that’s adequately resolved. Your latest question is about a bunch of other stuff — SwiftData, CloudKit, widgets, process management, and so on — and needs to be looked at by different folks. A variety of different subtopics would make sense for this, but let’s start out with App & System Services > SwiftData and then add other relevant tags (make sure to at least add Service Management, which makes sure I’ll see it). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m presuming that this problem reproduces with built-in system components, like Safari or curl, doing the download. If so then: [quote='838761021, WilFinnell, /thread/838761, /profile/WilFinnell'] Filed as FB23904785 [/quote] is the best path for this report. Our primary focus here on the forums is helping developers with code-level questions, and if you can reproduce it without any of your code involved then that’s clearly Apple’s issue to investigate. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='838682021, Catalin_e10, /thread/838682, /profile/Catalin_e10'] Any official Apple guidance [/quote] You’re unlikely to get official guidance here on the forums, where our primary focus is helping developers with code-level questions, not with their security audits. [quote='838682021, Catalin_e10, /thread/838682, /profile/Catalin_e10'] I have also filed this through Feedback Assistant: FB23893693 [/quote] That’s a good path for this. Finally, I want to stress that scripting language runtimes built in to macOS have been deprecated since macOS 10.15. The runtime you’re referring too is used internally by our developers tools and appropriate for other use cases. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='898414022, Klipto, /thread/838754?answerId=898414022#898414022, /profile/Klipto'] resolved, a parallel resubmission went through [/quote] Interesting. Did your original submission then complete promptly? Or is it still stuck? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='898402022, Leo Natan, /thread/836206?answerId=898402022#898402022, /profile/Leo+Natan'] Unfortunately, I have updated my Mac to Golden Gate beta. [/quote] Your main work Mac? Well, that’s… courageous (-: Anyway, if you have some free disk space there’s a really easy way to test this fix: Install macOS 26 in a virtual machine. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='898309022, Nickkk, /thread/799898?answerId=898309022#898309022, /profile/Nickkk'] How you created that VM is what I'd like to have confirmed._ [/quote] I’d post steps but I’ve actually forgotten )-: It was early in the macOS 27 beta cycle, and I’d definitely installed Xcode 27 beta before attempting this, so I had to jump through some hoops. I think they involved a prerelease of VB and a setting some magic user default, but I didn’t note down the details at the time, and I don’t have time to try it again today. And hence my original reply here, recommending that you research this via the support resources for the specific virtualisation solution you’re using. I will eventually find time to get back to this, but it’s possible that macOS 26.6 will be released before that (it’s currently an RC) which should smooth this path considerably. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

FYI, this is a known regression in Xcode 27 beta (r. 181024563). I don’t have any info to share as to when the fix will land. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='898181022, mateogon, /thread/822120?answerId=898181022#898181022, /profile/mateogon'] file a separate Feedback Assistant report if that would be useful. [/quote] I recommend that you do that. DevForums is primarily about APIs, and that was the focus of AntonPastrevich’s bug report (FB22448572). Your issue is about the behaviour of the system as a whole, and hence it makes sense to file your own bug report about it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Yes, that's also accurate. Cool. That bug (FB23788740) has definitely been seen by the right people. I don’t have any concrete info to share as to when it’ll be fixed. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hmmm, I would expect that to work. There are expected consequences of moving the VM between machines — it changes the provisioning UDID — but that shouldn’t stop it from logging in to an Apple Account. I just tried this here in my office and I’m also having problems, although it has different symptoms that what you’ve described. I’m gonna dig into this some more and get back to you. In the meantime, however, I wanted to share one specific piece of advice: Make sure the Apple Account you’re using has two-factor authentication enabled. Based on my previous testing, that’s a requirement. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Differences like this are usually the result of optimisation changes. For example, your app relies an undefined behaviour, the exact behaviour you get depends on the optimisation level, and thus things work in Debug builds but fail in Release builds. However, as a first step I recommend that you make sure that this isn’t a code signing issue. I explain how to do that in Isolating Code Signing Problems from Build Problems. Assuming that the problem follows the build configuration (Debug vs Release) rather than the code signing setup (Development vs Distribution) then you need to look at how you’re using the API. The most common problem I see in situations like this is that folks create a connection and fail to maintain a strong reference to that connection. The Release build then optimises the reference away, which causes the connection to close. The best way to avoid such problems is to use structured concurrency. I have some examples of that in TN3213 Moving from Multipeer Connectivity to Network framework.