eskimo

[quote='812624021, joel2001k, /thread/812624, /profile/joel2001k'] My certificates expired and I created new ones. [/quote] How? Using the Developer website? Or using Xcode? Because… [quote='812624021, joel2001k, /thread/812624, /profile/joel2001k'] How to fix the missing private key? [/quote] The way that you create a signing certificate determines where your private key ends up. For most certificates it’s just to just revoke stuff and start again, and that’s often the easiest way to resolve issues like this. WARNING That’s not the case for Developer ID certificates. For those, see The Care and Feeding of Developer ID. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='812598021, yccheok, /thread/812598, /profile/yccheok'] Is nonisolated still an appropriate way to ensure code runs on a background thread? [/quote] Yes and no. There are a couple of Swift Evolution proposals that describe this change in detail: SE-0461 Run nonisolated async functions on the caller's actor by default SE-0466 Control default actor isolation inference And, as you’ve noticed, there are Xcode build settings that affect this stuff. So, you have a couple of options: You can tweak your build settings and leave your code as is. Or you can move forward to the new build settings and tweak your code. I generally favour the second option, but I can understand folks preferring the first option, especially when wrangling a large project. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The Apple Developer Forums are primary focused on helping developers build apps and other products for Apple’s various platforms. Given that, I have two suggestions for you: File a bug using Feedback Assistant. Seek help in the Apple Support Community, run by Apple Support. Or both (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

So, when running outside of the debug, MIE can run in one of two modes: In soft mode, it generates simulated crash reports for violations. In hard mode, it crashes the process. My understanding is that hard mode is not yet support for third-party apps. The weird part is that I can’t find that documented anywhere. I’m gonna research why that’s not the case and get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m not sure what you’re asking for here. Are you trying to report a bug against Xcode? Or trying to work out how to use expectation-based tests in Swift Testing? If it’s the former, I recommend that you do that officially, as explained in Bug Reporting: How and Why? And please post your bug number, just for the record. If it’s the latter, see Expectations and confirmations. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

See my response on the other thread that you created about this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I don’t have a technical answer for you here but… [quote='812661021, pcasimiro10, /thread/812661, /profile/pcasimiro10'] Apple Forums (3 days ago): [/quote] Indeed. I recommend that you focus your efforts on that thread rather than continuing with this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

DevForums is primarily focused on APIs, so we can’t help you with general Wi-Fi issues. Given that, I have two suggestions for you: I encourage you to report this as a bug. I have specific advice on how to report Wi-Fi bugs in this post. If you’re seeking a workaround, I recommend that you ask about that on Apple Support Community, run by Apple Support. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Yeah, this is tricky. We do hope to ship an update to the Swift Playground app [1] but I don’t have any timeline info to share. I can’t even say whether it’ll happen before or after the Swift Student Challenge submission period [2]. Given that, my only advice is to plan to develop using the tools that are currently available. If things change before the submission period ends, you can then adjust accordingly. I’m sorry I don’t have better news here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] See here. [2] Per the main page, that’s 2026-02-06…28.

Thanks for the extra info. First up, an SFAuthorizationPluginView can’t support smart card authentication in the same way as the built-in login UI can (FB11978008). That’s because the built-in UI populates various authorization context values but SFAuthorizationPluginView does not. The name and format of these values is not documented, so the authorization plug-in can’t work around this issue itself. However, that’s not what you’re trying to do. Rather, you’re trying to simply use smart-card-back credentials, and that’s more feasible. There’s one thing to check here, and then a roadblock to get around. The thing to check is that your smart card is available in pre-login context. To do that, disable your authorisation plug-in, reverting to the built-in login UI. Then check that you can use the built-in PIV smart card support to pair your user with your smart card, and thus log in with your YubiKey. I don’t have docs for how to do that handy — that’s more of an Apple Support thing than a DTS thing — but I do it

[quote='869942022, compiler_flags, /thread/792453?answerId=869942022#869942022, /profile/compiler_flags'] including on products that have menu bars. [/quote] OK. That’s something I should look at because: This isn’t expected behaviour. And it’s not the behaviour that most developers see. But you’re obviously seeing it consistently. And I’ve seen reports similar to this from other developers, so there’s clearly something missing somewhere. [quote='869942022, compiler_flags, /thread/792453?answerId=869942022#869942022, /profile/compiler_flags'] I use netcat to create an opening listening port on one and then copied the compiled version of NetworkIssueTest.app … [/quote] OK. I’d like to try this here in my office. I specifically want to try it with the exact binary that you compiled, but it’d be great if I had the source code to build that as well. Probably the best way to get that to me is to file a bug. That way you can attach all the necessary bits. And, honestly, your latest test should work, so it’s reasona

I’m gonna shelve the SIGTERM issue for the moment… Bah, no, I can’t let that go. My original question still stands here: Why are you getting involved in SIGTERM at all? This matters because there’s evidence to suggest that your packet tunnel provider is not stopping when asked, and SIGTERM can be a factor in that. Also, I don’t see any crash reports in the sysdiagnose log, and it’s not uncommon for signals handlers to interfere with crash report generation. So I’d like to get a handle on why SIGTERM comes into play here, and if any other signal handlers are installed. That is … is the real deal. Cool. For reference, I’m working from sysdiagnose_2024.10.17_10-27-27+0200_iPhone-OS_iPhone_22A3370_44011817.tar.gz. I opened system_logs.logarchive and started poking around. In the last 30 minutes of the system log I see three failures to start the VPN: type: default time: 2024-10-17 10:18:56.832535 +0200 process: APP_NAME subsystem: com.apple.networkextension message: Last disconnect error for CONFIG_NAME changed f

[quote='872032022, shabnamk, /thread/812271?answerId=872032022#872032022, /profile/shabnamk'] We have opened a Code Support ticket (Case ID: 17936650) to address this. [/quote] That hasn’t yet come through our system. When it does, I’ll look at it and the update this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

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. Thanks for those answers. My advice here is that you change tack. Rather than try to set this at runtime based on an environment variable, have your installer install an app with the right icon. That doesn’t mean that you need N installers for your N icons. There are a couple of ways that you can customise the icon on the fly. The first is to have a post-install script that applies a custom icon to your app. This has one key advantage: It’s easy to implement (-: Specifically, setting a custom icon doesn’t affect the app’s code signature. However, I’m not sure it’s actually the right option for you, because of the issues you raised in your other thread, Changing the menu bar display name. There’s no way to set a custom app name like this. Honestly, I can’t think of a good way to set the app name at all. macOS expects apps to be static artefacts. While you can change some of this stuff at

[quote='872001022, shenbj, /thread/812455?answerId=872001022#872001022, /profile/shenbj'] Here is the Crash Report [/quote] Unfortunately that crash report is not doing what I need it to do. It’s possible that was munged by the forums platform [1]. It’s also possible that your redaction efforts caused something to break. [quote='871930022, , /thread/812455?answerId=871930022#871930022'] Also, please post the Feedback Report number. [/quote] Yeah, I think that’s the best way to make progress here. shenbj, Please file a bug about this, attaching some example crash reports, and then reply here with the bug number. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] This is, alas, a known bug (r. 136655649).