eskimo

Sorry, I meant the My Certificates tab. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for filing FB21229146. FWIW, I tried reproducing this here in my office — using a private browsing window and a new non-Apple test account — and I didn’t see it. Clicking “Remind me later” took me to the root of the forums with the ‘welcomes to the forums’ tour sheet, which is what I’d expect. So I’m not sure why it’s affecting you. How did you manage to escape the “Remind me later” loop? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The canonically correct way to manage Mach service names [1] in a sandboxed app is to make the name a ‘child’ of an app group ID. That’s what I recommend that you do here. Temporary exception entitlements are a reasonable option when: You’re not targeting the Mac App Store No other option is available to you I talk more about that in The Case for Sandboxing a Directly Distributed App. But in this case you are targeting the Mac App Store and there is a better option available, and hence my recommendation. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] This includes XPC named endpoints. I recommend that folks not use Mach directly, although I realise that’s not something under your control here.

I’m glad to hear you got this sorted out. Lemme tackle this last bit: [quote='867924022, fbartolom, /thread/808952?answerId=867924022#867924022, /profile/fbartolom'] I'm still in the blue about what embedding or not embedding does mean. [/quote] In the context of an iOS app [1]: Select Do Not Embed if you want to simply record a reference to the framework. This is primarily for system frameworks, like StoreKit, where the framework exists on the OS you’re targeting, and thus your app doesn’t need to carry along its own copy [2]. Select Embed & Sign if you want to embed the framework in your app and re-sign it as your code. This is most commonly used for frameworks that are part of a third-party SDK, where the code doesn’t exist on the target OS and thus your app needs to have its own copy. Select Embed if you want to embed the framework in your app. Folks typically use this with their own frameworks. For example, you might create a framework to hold some some code that’s common to your app and its app exte

Are you seeing this on macOS 26.0? Or is it new in macOS 26.1? If it’s new in 26.1, be aware that it has a serious bug in this space. See this thread for details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

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

If you have multiple issues, it’s generally best to put them in different threads. That’s because different folks have different expertise, and it’s unlikely that any one person will be able to help you with all of your issues at once. In this case, I can address your second question: [quote='808920021, chps67, /thread/808920, /profile/chps67'] In Xcode 16 why is it no longer possible to arrange my files as I did before [/quote] I’m not 100% sure I understand this, but I suspect it’s because Xcode now has two ways to organise items in the Project navigator: Groups, as used by older versions of Xcode Folders, which are new [1] With groups you can explicitly manage the position and order of items in the Project navigator. With folders, Xcode does that implicitly, replicating the file system hierarchy and showing all the items alphabetically. Folders have some really important advantages — most notably, they radically reduce the number of project file merge conflicts — but if you don’t like them you can always s

Did you opt in to peer-to-peer on both the listener and the browser? We never enable that by default because it has a non-trivial network impact. IIRC, this is how you’d do that on the listener: let lp = BonjourListenerProvider(type: _test._tcp) let l = try NetworkListener( for: lp, using: .parameters({ TCP() }) .peerToPeerIncluded(true) ) And a similar technique is available for the browser. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This is only with the new NetworkConnection API, right? So things work if you use the older NWConnection? If so, my advice is that you file a bug against the new API. 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

What Albert said plus… Keep in mind that, regardless of what your third-party tooling does, iOS imposes strict limits on what apps can do in the background. See iOS Background Execution Limits for more about that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

There are two parts to this: How to cleanly close an NWListener in general. And what to do when “exiting the application”. [quote='808957021, veer_dutta07, /thread/808957, /profile/veer_dutta07'] After calling listener.cancel(), do we need to wait for the .cancelled state … ? [/quote] No. From the perspective of Network framework, the cancellation will proceed asynchronously and that’s just fine. However, it’s easy to think of cases where you might need to do that due to considerations in your code. Imagine, for example, that you have a listener controlled by a Start / Stop button. If the user clicks Stop and then immediately clicks Start, bad things might happen if the cancellation is still in progress. In that case, you’d want to show a status of stopping and not enable the Start button until the cancellation is complete. [quote='808957021, veer_dutta07, /thread/808957, /profile/veer_dutta07'] Is it recommended (or required) to set newConnectionHandler = nil when shutting down a UDP listener? [/quote] It sh

I’m not exactly sure what caused the change you’re reporting here. If you’re having problems with a third-party tool like this, I recommend that you start by escalating them with the tool’s vendor. Having said that, my general advice is that you not use a third-party crash reporter. For a detailed explanation as to why that’s a bad idea, see Implementing Your Own Crash Reporter. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

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

[quote='867580022, whiteb, /thread/804841?answerId=867580022#867580022, /profile/whiteb'] Is there just a propagation time … ? [/quote] No. Is this for Team ID 8________6? What are the last four characters in the Mac’s provisioning UDID? And is that Mac a VM? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='867728022, shara7, /thread/806187?answerId=867728022#867728022, /profile/shara7'] I assume this is simply a bug [/quote] That’s correct. If you’re building a macOS product and this is causing you significant amounts of grief, it might make sense to ship an update to your product that embeds your program in an app-like wrapper (per Kevin’s suggestion above). Otherwise, my advice is that you wait for a fix. And, no, I don’t have any info to share as to when that fix will actually land. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com