“eskimo”

[quote='883512022, SCFarrell, /thread/821471?answerId=883512022#883512022, /profile/SCFarrell'] I submitted a bug for this exact same behavior … FB22436593 [/quote] Thanks! [quote='883541022, GMacD53, /thread/821471?answerId=883541022#883541022, /profile/GMacD53'] I now see I have not filed a Bug Report. [/quote] Indeed. You don’t need to file your own bug about this. SCFarrell’s one is fine. But if you want to be notified when this is fixed, you can file a bug and ask that it be marked as a duplicate of FB22436593. See Bug Reporting: How and Why? for more on that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='883420022, PavanGulla, /thread/821002?answerId=883420022#883420022, /profile/PavanGulla'] We have filed FB22433770 [/quote] Thanks! [quote='883420022, PavanGulla, /thread/821002?answerId=883420022#883420022, /profile/PavanGulla'] Does MetricKit also use these same APIs under the hood … ? [/quote] I think it’s fair to say that: Various low-level subsystems have mechanisms to vend metrics. MetricKit collects these values and turns them into something coherent for you to consume. However, there are a lot of implementation details in the mix: Some of these low-level mechanisms have no API. Or there might be an old API with significant caveats. You can find a good example of the latter in Extra-ordinary Networking > Network Interface Statistics. Even when they do have an API, it’s not always obvious how the low-level values it returns correlate to the values reported by MetricKit. So, in general, there isn’t a good way for you to call these low-level APIs and produce metrics that match the MetricKit one

[quote='883484022, antho2305, /thread/821749?answerId=883484022#883484022, /profile/antho2305'] I have already opened a support case [/quote] Cool. [quote='883484022, antho2305, /thread/821749?answerId=883484022#883484022, /profile/antho2305'] many developers are still reporting notarization issues right now [/quote] Honestly, this is about normal, with the vast majority being the “in-depth analysis” issue. [quote='883484022, antho2305, /thread/821749?answerId=883484022#883484022, /profile/antho2305'] including 403 errors reported this morning on the forums [/quote] Yeah, I’ve seen a few of those. They are definitely unrelated to your issue. Rather, they’re tied to the Apple Developer Program License Agreement. I usually see a cluster of those every time we update the agreement, which is something we did recently (2026-03-31). These usually have an obvious cause — the developer simply failed to agree to the new agreement — but every now and again I see something unexpected. However, the symptoms are very spec

Is your client able to receive other events types? I’m asking because: If it can, then that indicates an issue specific to the linkQualityDidChange event. But if it also fails for, say, ssidDidChange, that suggests a general issue with your event monitor. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I have a theory about what’s going on here. I’m gonna check on some details and get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='821926021, matthewruzzi, /thread/821926, /profile/matthewruzzi'] FB22441056 [/quote] Thanks for that. 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

This is definitely unusual. You’ve already eliminated a bunch of the more common causes of issues like this. AFAICT your team received the Contactless Pass Provisioning (SharableCredential) capability for all App IDs. I’d like to exploit that fact to run a diagnostic test: Using the same Xcode, create a new project from the iOS > App template. When creating the project, enter a new test bundle ID and select your standard team (Team ID S7AUTD2C2B). In Signing & Capabilities, make sure automatic code signing is enabled for all configurations. And that the correct team is selected. At the top, make sure that you have a test device selected as the run destination. Then add the Contactless Pass Provisioning (SharableCredential) capability. Automatic code signing should kick in and create a new development provisioning profile. Wait for that to finish. Assuming that works, try running the app on a test device. What do you see? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ App

Are you working on an iOS app that talks to your server? Or are you expecting users to access it via Safari? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='821896021, RobJones, /thread/821896, /profile/RobJones'] I've also created a CTK extension [/quote] So, yeah, you don’t want to go down that path. Because the YubiKey presents a PIV interface over USB, it will be picked up by the built-in PIV support, so you don’t need to mess around with a CTK app extension. And this also means that you’re correct that you don’t need to install Yubico Authenticator. As to what you should be doing, I recommend that you break this up into two steps: Find and then use the key, just to make sure it’s working. Then try to pass the corresponding digital identity to URLSession for mTLS. For step 1, see my advice in this post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m still working on this. It’s proving to be challenging, not helped by the fact that WWDC is looming large on everyone’s calendar. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='883372022, GMacD53, /thread/821471?answerId=883372022#883372022, /profile/GMacD53'] My issue is it not being able to be added for review [/quote] Ah, thanks for clarifying that. Unfortunately that limits my ability to help you here. I’m not able to submit apps for review. [quote='883372022, GMacD53, /thread/821471?answerId=883372022#883372022, /profile/GMacD53'] I wouldn’t want to submit it for approval? [/quote] Yeah, agreed. The obvious next step is to file a bug about this. Please include the Apple ID of your app [1], a summary of the steps you took, and the details of the specific error you’re hitting. Once you’re done, please post your bug number here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] That’s the Apple ID of the app, not your Apple ID (now known as an Apple Account). To see this in App Store Connect, go to the app record, select App Information on the left, and look for the Apple ID field. It’

[quote='883354022, -dp, /thread/806471?answerId=883354022#883354022, /profile/-dp'] for the app's main module, I have to enter a Library name of this form: myApp.debug.dylib. [/quote] That’s not my experience. When I put this code into an app, the library for each log point is Test806471.debug.dylib but pasting Library:Test806471 into the field still works. If you click on the arrow for that token you can see why. It presents a popup menu with various options, and one of those options lets you select between Equals and Contains, with Contains being the default. [quote='883354022, -dp, /thread/806471?answerId=883354022#883354022, /profile/-dp'] it appears that this section is cleared on each Xcode launch [/quote] Indeed. I’ve seen complaints about that before, and some spelunking turned by the relevant bug (r. 130497236). If you want to be notified if and when that gets fixed, file your own bug and ask that it be marked as a dup of that one. See Bug Reporting: How and Why? for lots more hints and tips about fi

I use third-party application. OK. DevForums is primarily focused on helping developers use the APIs in Apple’s various platform SDKs. If you’re having problems with a third-party product, you have a couple of options: I generally recommend that you contact the product’s vendor. It’s likely that they’ll have the most specific advice for you. Alternatively, if you want to discuss this with other Apple users, start a thread over in Apple Support Community, run by Apple Support. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Lots of what Albert talked about is covered in more depth in TN3179 Understanding local network privacy. Specifically, the symptoms you’ve described are most commonly seen by folks who aren’t signing their code properly. See the Build-time considerations section of that technote for more. Also, I want to clarify this point: [quote='821759021, Evan, /thread/821759, /profile/Evan'] I’m building an app [/quote] Are you using app in the Apple sense? That is, something that presents a GUI and the user launches from the Finder (or Home screen on iOS)? Or in a more general sense? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com