“eskimo”

[quote='843058021, sbatson01, /thread/843058, /profile/sbatson01'] I get a popup indicating that that it's trying to sign in to Keychain using my first Name (Steve). [/quote] Well, that’s weird because the keychain unlock alert normally only requests the keychain password. There is no user name. So… Please post a screenshot of the alert you’re seeing. Also, launch Keychain Access, select login on the left and My Certificates at the top, grab a screenshot of that, and post it as well. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='843925021, Loren-86, /thread/843925, /profile/Loren-86'] Is there any self-service way to release an App ID from a personal team … ? [/quote] No. A Personal Team has strict limits [1] and so you’ll find that the App ID expires pretty promptly. But the quickest way to resolve this issue is to change your app’s bundle ID. That makes it a new app from the perspective of Apple’s tooling. Normally changing the app’s bundle ID is a Big Deal™ but that’s not the case here because of the afore-mentioned limits on your Personal Team. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] For the details, see Developer > Support > Choosing a Membership.

I don’t think you’ll find the answers you seek here on the Apple Developer Forums. Our focus is on Apple APIs and tools, and the issue you’re hitting is very much tied to your use of third-party tooling. In cases like that you need to either: Seek help from support resource for that tooling. Or if the tooling is open source, investigate the issues yourself. On the Apple side of things, I recommend that you start by using the Xcode to create a test project and upload that using the Xcode organiser. You can then use the organiser to export that app, package it using command-line tools, and then upload it using altool. See Packaging Mac software for distribution for packaging instructions. I suspect that’ll work successfully and, if it does, you can use it as a baseline to drive your investigation of the issue you’re hitting with your third-party tooling. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Why does this matter to you? I’d like to know because words like this… [quote='843527021, hjvoryn, /thread/843527, /profile/hjvoryn'] contractually guarantee [/quote] suggest that you’re going to ship a product that relies on the exact behaviour here. And AFAICT the exact behaviour isn’t documented, making it an implementation detail, and thus there is no guaranteed behaviour. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This is expected. Your packet tunnel provide effectively operates in one of two modes depending on the includeAllNetworks setting. Routing your VPN network traffic has the details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m glad to hear you got this sorted. [quote='902927022, DrMiller, /thread/843449?answerId=902927022#902927022, /profile/DrMiller'] Although I am curious where K533... came from [/quote] You are mixing up your 10-character identifiers. This is a common source of confusion, so I collected together all the detail in Code Signing Identifiers Explained. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This is ringing some bells, but I wasn’t able to track down the place where I’ve seen it before. But the answer here is pretty much always the system. If the system is leaking objects of a type that you’ve never touched, it’s most likely a bug in the system rather than a bug in your code. Normally I’d send you straight off to file a bug, but in this case I think it’d be worthwhile for you to test on the latest system (including the latest macOS 27 beta) to make sure we’ve not fixed it already. If you do file a bug, 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

There are two ways to think about this: What are the official rules? Within the bounds of those rules, what should you do? We can’t meaningfully discuss the first point because: The 2026 Swift Student Challenge has closed, so last year’s fine print is irrelevant. There’s been no announcement about a subsequent Swift Student Challenge, so we’ve no idea what its fine print will look like (or if it’ll even exist). As to the second point, I don’t have any official advice on that front. Speaking personally, I feel that the best challenge entries are the ones that tell a story, and so you need to think about how your plan fits in with the story you want to tell. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='843700021, fhcolak, /thread/843700, /profile/fhcolak'] However, verification reports: [/quote] What do you mean by “verification”? Clicking the Validate App button in the Xcode organiser? [quote='843700021, fhcolak, /thread/843700, /profile/fhcolak'] I suspect a Unicode-normalization mismatch [/quote] You are right to suspect that, but I want to run you through some debugging steps before I send you down that path. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Are you seeing this in standard user scenarios? Or on your work Mac? The reason I ask is that it seems that this crash is related to Launch Services finding the ‘wrong’ version of your app (well, the appex within your app). Such problems are common on development Macs, and my general advice is rule them out by retest as most users use your app, that is, with a single copy of the app in the Application folder. Having said that, this trap isn’t any fun and we’ll use your bug, FB24525451, to decide what to do about that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Lemme start you out with iOS Background Execution Limits. While that specifically refers to iOS, a lot of the context is relevant on the watch as well. I want to focus on this part of your question: [quote='843751021, BioLinkAlex, /thread/843751, /profile/BioLinkAlex'] that periodically uploads small HTTPS payloads [/quote] How is your app getting execution time to kick off this upload? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='843544021, Colin30, /thread/843544, /profile/Colin30'] Is there any supported public API … to reliably determine … [/quote] Not really. There are APIs that let you introspect the networking stack, but they all come with caveats. For example: There’s a difference between cellular being disabled and WWAN not working. There’s a difference between WWAN not working and your app have access to WWAN. Similar for Wi-Fi. Remember that ‘disabling’ Wi-Fi in Control Centre is different from disabling it in Settings. And that on an iPhone bought in China the user has the option to disable Wi-Fi access in addition to disabling WWAN access. Options like Ethernet significantly muddy the waters. So, questions like this inevitably boil down to what exactly you’re trying to achieve. A lot of the time there are options that work for specific scenarios that don’t work generally. Anyway, lemme point you in the direction of Extra-ordinary Networking, which links to a bunch of other posts that explain a lot of the background

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

I was gonna suggest that you file a bug about this but I see that you’ve already done so (FB24481377). That’s the best path forward here. And I took a quick look (hey hey) at it and can confirm that it’s with the right folks. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='843250021, Jobson, /thread/843250, /profile/Jobson'] We opened a high-priority ticket with Developer Support [/quote] Cool. You’re on the right path here. We can’t help you with that specific error here on the forums. See this post for more background. [quote='843250021, Jobson, /thread/843250, /profile/Jobson'] the initial front-line response was a generic boilerplate macro telling us to complete iOS App Notarization metadata fields [/quote] Ah, the perils of reusing terminology )-: I recommend that you clarify that point with Developer Program Support. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com