“eskimo”

[quote='825043021, nathan-pierce-veertu, /thread/825043, /profile/nathan-pierce-veertu'] is there any ETA [/quote] We can’t talk about The Future™ here on DevForums. See tip 3 in Quinn’s Top Ten DevForums Tips. [quote='825043021, nathan-pierce-veertu, /thread/825043, /profile/nathan-pierce-veertu'] Running Docker specifically would be nice. [/quote] As always, if there’s something specific you want, I encourage you to file an enhancement request that outlines your requirements. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hmmm, interesting. Browsing for all services requires the multicast entitlement on iOS, but according to TN3179 that entitlement isn’t needed on macOS. And it seems that you tried it anyway, and it’s still not working. I’ve no idea what’s going on here but you’ve done enough isolation that I think the next step is a bug report. Make sure to attach a sysdiagnose taken shortly after reproducing the problem. And if you can attach your small test project that shows this failing with DNSServiceBrowse, that’d be great. Please post your bug number, just for the record. 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='825006021, Rustem98, /thread/825006, /profile/Rustem98'] Has anyone else experienced extended In Progress hold on a freshly enrolled Developer ID? [/quote] That seems to be pretty common, based on what I see here on the forums. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

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

[quote='886284022, Murat_Ozturk, /thread/824781?answerId=886284022#886284022, /profile/Murat_Ozturk'] The responsibility for this lies with you. [/quote] Me personally? Or are you using “you” to refer to Apple as a whole? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This has come up a bunch of times and I think this thread is probably the best one to treat as a ‘lead’ thread. I plan to post an update to that thread soon [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Ideally in the next few hours but I’m travelling right now, meaning my schedule is much harder to predict, so it might be a few days |-:

[quote='824781021, Murat_Ozturk, /thread/824781, /profile/Murat_Ozturk'] Forum mod DTS Engineer gives copy-paste answers to every user who has this problem. [/quote] Indeed. For those folks reading along at home, I’ve included a copy of that response at the end of this reply. Presumably you want me to give you more information about this delay. I’m not able to do that, sorry. You didn’t mention how long your requests have been stuck. Most folks who hit this issue see the issue resolved in a day or two. If your requests are stuck for more than a week, reply back here and I’ll look at this again. Oh, and just FYI, I’m not a “forums mod”. I work for DTS, whose role here on the forums is to answer technique questions about Apple’s APIs, developers tools, and some developer services. There are in fact moderators that doing moderator-like things — dealing with spam and so on — but they generally don’t post replies. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo

I asked about this internally and the answers were pretty much along the lines explained by mlgiPhone7plus: We plan to get the awards to folks before WWDC26. The situation with tracking depends on your region. So, it’s possible that some winners will receive a FedEx tracking link but others might get notified in some other way. Bah!, running a worldwide company is hard |-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='886187022, DeviceManagementPM, /thread/824282?answerId=886187022#886187022, /profile/DeviceManagementPM'] FB22494634 [/quote] Thanks! It looks like this has already found its way to the right folks and they’re treating it as… yep… a bug. I’ve no info to share as to the schedule for a fix, but you can monitor the state of the bug in Feedback Assistant. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for that. You’re right that the lacks device name entitlement log entry is worrying, especially given the later Service does not have a bonjour name error. The entitlement in question is com.apple.developer.device-information.user-assigned-device-name, as explained here. Enabling private data recording would be super interesting here, but I can understand that it’s a bit of a chore to set up. At this point I think it makes sense for you to file a bug about this. See the Handoff for xyzOS instructions on our Bug Reporting > Profiles and Logs for specific instructions. Please epost your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I send mail by smtp protocol and javamail api. Ah, OK. So your issue is that the Mail app’s MIME support doesn’t match your expectations. Given that this doesn’t involve any Apple APIs — it’s about the behaviour of the Mail app itself — this isn’t really something we can help you with here on the forums. Our focus is on Apple APIs, Apple developer tools, and so on. So, my advice is that you file a bug about this, explaining what you’re doing and why you think the Mail app is handling this incorrectly. Make sure to include screenshots of the problem. And, if you can reproduce this on the Mac, it’d be helpful to include a copy of the message as a .eml file. In Mail, get this by choosing Message > Forward as Attachment. Also, if your messages render correctly on other common platforms, I recommend that you include those details, and screenshots from them as well. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='886193022, PavanGulla, /thread/823741?answerId=886193022#886193022, /profile/PavanGulla'] Is this the correct approach for collecting NE debug logs for a standard user repro? [/quote] It’ll work, but you can do better. More on that below. [quote='886193022, PavanGulla, /thread/823741?answerId=886193022#886193022, /profile/PavanGulla'] does the debug log need to be collected from within the same user session … ? [/quote] No. The download with your approach is that there’s a relatively long delay between the event and you capturing the log. A better option would be: Using the GUI, log in as a standard user. Using SSH, log in as an admin user. And enable the debug options. In the GUI, reproduce the problem. In the SSH session, trigger the log. However, if it’s hard to set this up — for example, if this managed Mac won’t let you enable SSH — it’s just fine to user the original approach you outlined. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo

Modern versions of Apple’s linker are able to merge identical functions. That’s pretty darned cool, but it presents a problem for symbolication. Which symbol should it show? By default it doesn’t show any of the symbols, but instead this placeholder, which is exactly what you’re seeing here. There are two ways around this: Disable the optimisation Manually symbolicate By default, Xcode enables this optimisation only for Release builds. You can change that policy by the -no_deduplicate linker setting. See the ld man page for more about that. IMPORTANT Put this linker flag in the Other Linker Flags build setting. Make sure to escape the value with -Xlinker. The downside to this approach is that you miss out on a useful optimisation. To quantify that, pass the -verbose_deduplicate option to the linker and it’ll output a report of what it did. An alternative is to manually symbolicate the frame’s address and then pass the -dedup option to atos. See the atos man page for more about that. For more information abou

Yeah, that’s weird. I’d appreciate you filing a bug about this, and then posting the bug number here, just for the record. This did actually create a playground from the template, it just doesn’t switch to it. So, you can get around the problem by clicking the back button until you get to the top level and then clicking on your newly created playground. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m not 100% sure what’s causing all the behaviour you’re seeing [1] but if I were in your shoes I’d get around this by declaring an codable version of your struct solely for the benefit of the coding system: struct Activities { var name: String var age: Int fileprivate struct Inner: Codable { var name: String var age: Int } } extension Activities: RawRepresentable { init?(rawValue: String) { guard let i = try? JSONDecoder().decode(Inner.self, from: Data(rawValue.utf8)) else { return nil } self.init(name: i.name, age: i.age) } var rawValue: String { let i = Inner(name: self.name, age: self.age) let e = try! JSONEncoder().encode(i) return String(decoding: e, as: UTF8.self) } } The downside is that you need to keep Activities and Activities.Inner in sync, but the benefit is that the extra code is super simple. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] I think it’s because the encoding system has special cases for ty