“Apple Maps Guides”

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.

IMPORTANT There’s updated advice in this reply (i. 101537572, r. 174902737). Wow, that escalated quickly. When I replied earlier I thought that this was something specific to sergej_swiftlane’s situation. However, this is clearly affecting a wide range of folks. A colleague of mine uncovered a third-party developer bug about this (FB22439399) [1] and we’re escalating that internally. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] It may even be from one of you (-:

Thanks for bringing this to the forums. Lemme start out by linking to iOS Background Execution Limits. You’ve probably already seen it, but it sets the stage (hey hey) for other folks following this thread. There are two parts to this: What’s technically possible? What will be accepted by App Review? I can’t addresse the second part. I don’t work for App Review and thus can’t speak on their behalf. My general advice is that you consult their published guidelines and, if you still have questions, contact them directly. With that out of the way, let’s return to the technical stuff. I want to start by recapping some of the points from TN2277 Networking and Multitasking: Networking works fine in the background as long as your app doesn’t get suspended. If your app does get suspended, normal networking will just stop. For things to continue, you need some sort of special affordance, the canonical example of that being a URLSession background session. There’s no special affordance for UDP. So, your question is equi