“Apple Maps Guides”

Yeah, I dusted off one of my CoreWLAN test projects and tried to get this working. Sadly, I had the same issue as you. I’m able to see other events but not linkQualityDidChange events. I tried a couple of things: Disabling the App Sandbox Requesting the location privilege Neither helped. Looking at the system log I see this: type: default time: 2026-04-09 13:49:29.717180 +0100 process: airportd message: ERROR: CoreWLANTestbed (62660) is not entitled for com.apple.wifi.events, but allowing anyways for event type 6 where 6 is the raw value of the linkQualityDidChange event, which confirms that the registration worked. There are plenty of signs in the system log that the system is noticing the RSSI change. There seems to be something blocking event delivered, and it’s not at all clear what. I’m going to have you file a bug about this. Once you’re done, reply here with the bug number and I’ll take another look. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eski

Hi Quinn, Thanks for your reply. I understand the possibility of “in-depth analysis”, but based on the behavior I’m observing, this doesn’t seem to fully explain the situation. Here is the full sequence of events: For over a month, notarization has been working consistently (20+ submissions), typically completing within a minute. On April 4th (morning), submissions were still accepted without any issue. Later that same day, submissions started getting stuck in “In Progress” for extended periods. At that point, I waited for those “In Progress” submissions to complete. After some time, those submissions were eventually returned as Rejected with the error: Team is not yet configured for notarization. I then retried new submissions, and on April 8th, they were suddenly Accepted again, without any change on my side. However, later that same day, new submissions were again Rejected with the same error. And today (April 9th), new submissions are once again stuck in In Progress (since around 9 AM). So the pattern is:

This concerns only my apple developer account and not my consumer Apple ID.

My current Apple Developer account status as displayed at developer.apple.com/account

OK, you’re definitely on the right path here. [quote='883659022, RobJones, /thread/821896?answerId=883659022#883659022, /profile/RobJones'] it works ONLY WITH my enterprise provisioning profile. [/quote] Interesting. I didn’t expect to see a difference between team types here, because Developer Account Help > Reference > Supported capabilities (iOS) says that Keychain Sharing is available for all three team. However, I tested this and discovered a discrepancy. Specifically, I created a test project with two app targets: Individual, signed by the Individual team I use for testing (SKMME9E2Y8) PersonalTeam, signed by the Personal Team I use for testing (SKMME9E2Y8) Note Personal Team is the term that Xcode uses for Apple’s free provisioning feature. It corresponds to the Apple Developer column in the table I referenced earlier. In contrast, an Individual team is covered by the ADP column. I then added the Keychain Sharing capability to both, built them for the device, and then dumped the

Thanks, Apple. A thing to note: I tried to test my links through Notes, that works on iOS but not on watchOS. On watch only Mail and Messages do work!

[quote='883691022, akadeepsh, /thread/806641?answerId=883691022#883691022, /profile/akadeepsh'] isn't there any way to add a thumbnail to replace the blue swirl galaxy? [/quote] (Negative question. Tricky!) AFAIK there’s no supported way to replace the default thumbnail. [quote='883691022, akadeepsh, /thread/806641?answerId=883691022#883691022, /profile/akadeepsh'] I haven't signed any screensaver before so i have no idea. [/quote] I presume you’re distributing it directly? If so, you’ll need to use Developer ID signing. I have a couple of key points about that: Developer ID signing identities are precious, so you need to manage them carefully. See The Care and Feeding of Developer ID. If you’re using Xcode, be aware that the organiser can only export apps. If your distribute a standalone screen saver — rather than, say, nesting it within an app — then you’ll need to manually export and re-sign the screen saver from your Xcode archive. For more on how to do that, see Creating distribution-signed code for macO

So, yeah, this is pretty much what I suspected yesterday. The behaviour you’re seeing is fallout from a wider change (r. 154872815). It’s part of a security hardened effort, and thus there’s no easy ‘undo’ option. [quote='821894021, oleksandr91, /thread/821894, /profile/oleksandr91'] what I really need is the ability to keep the keychain password in sync with the user password when the latter is changed by our program. [/quote] I’d like to get a better handle on this: Is this part of some sort of identity provider product? From what context are you changing the user’s password? From a GUI app? Or in the background? And what API are you using to do that? And how does confirming the login keychain password help with that process? Presumably that means you also need to change the login keychain password. How are you doing that? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

If your goal is inference, Apple Silicon with unified memory sidesteps these driver issues entirely. I've been loading 30B+ models via MLX on an M2 Pro — no PCIe bottleneck, no VRAM split, no driver compatibility fights. Might be worth comparing the cost of a Mac Studio vs the time spent debugging ROCm on the 2019 Pro.