eskimo

maybe this should be a new thread. Yes, this should definitely be a new thread (-: If you do start a thread, use the subtopic and tags as this thread; that way I’ll be sure to see it go by. Before you do that, however, make sure to review TN3179 Understanding local network privacy. I suspect this is as simple as you not signing your app with the com.apple.developer.networking.multicast entitlement, a requirement that’s documented in that technote. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I see two straightforward options here: Use Xcode for your development. Xcode has a Personal Team feature that allows you to develop apps for your own device without being a member of a paid team [1]. Re-join the paid developer program. I’m not sure if your third-party tooling has the equivalent of Xcode’s Personal Team feature. I very much doubt it, but you’d have to ask the vendor to be sure. But the current path your on, which is clearly focused on paid team membership, because it need an App Store Connection API key, isn’t going to work when you can’t create such a key. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Albeit with significant restrictions. For the details, see Developer > Support > Choosing a Membership.

[quote='867195022, Sandya, /thread/808036?answerId=867195022#867195022, /profile/Sandya'] This does prevent the crash. [/quote] Cool. [quote='867195022, Sandya, /thread/808036?answerId=867195022#867195022, /profile/Sandya'] the fonts still do not install system-wide [/quote] Bummer. [quote='867195022, Sandya, /thread/808036?answerId=867195022#867195022, /profile/Sandya'] Is .persistent font registration intended to work with fonts delivered through Apple-Hosted Background Assets? [/quote] I don’t know, but I’m not sure that matters. You want this to work, and that’s a pretty reasonable request. So either this as a bug or an enhancement request, and the path forward is the same in both cases: File a report in Feedback Assistant. However, looking at FB21109320 it seems like we’ve decided to use it to drive that investigation, rather than use it to track the CT annotation issue. So I don’t think there’s anything else for you to do here, other than to keep on eye on FB21109320 in Feedback Assistant. Share and Enj

[quote='867158022, Calumh11, /thread/806195?answerId=867158022#867158022, /profile/Calumh11'] TestFlight … fails to install as well. [/quote] Thanks for confirming that. [quote='867158022, Calumh11, /thread/806195?answerId=867158022#867158022, /profile/Calumh11'] programatically add the capability for iOS 26 only but I have not found a way to do that! [/quote] That’s not possible. Xcode reflects this capability into your app’s entitlements. Entitlements are baked into your code signature. You can’t add them at runtime. If you’re curious how this actually works, have a read of TN3125 Inside Code Signing: Provisioning Profiles. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='867289022, Mutiny78, /thread/807490?answerId=867289022#867289022, /profile/Mutiny78'] I have complete wild guess [/quote] That’s a pretty wild guess, and AFAICT it’s not even close. I actually spent some time looking at this before my previous reply. Based on my own research, here’s what I know: Swift Playground has the App Sandbox enabled. When you preview an app, it builds a copy of the app and runs that [1]. That app is stored in the Swift Playground app container. That app is ad hoc signed. Modern versions of macOS implement something called app container protection. This prevents app A from accessing the app container of app B without user approval [2]. In this case app A is the app being previewed and app B is Swift Playground. In fact, the app being previewed is triggering the app container protection immediately at startup, simply by trying to access its own main executable. What I don’t know is why this is only happening on macOS 26.1. App container protection has been around since macOS 14.

[quote='867269022, nikhil2701, /thread/807854?answerId=867269022#867269022, /profile/nikhil2701'] The [new] classes doesnt seem to support any custom TLS configuration using NWParameters. [/quote] With the new API you generally configure stuff using modifiers. For example, here’s how to do custom server trust evaluation on a connection: let endpoint: NWEndpoint = endpoint let connection = NetworkConnection(to: endpoint) { TLS() .certificateValidator { _, trust in let shouldConnectToServer = … check trust … return shouldConnectToServer } } [quote='867269022, nikhil2701, /thread/807854?answerId=867269022#867269022, /profile/nikhil2701'] The multipeer connectivity framework used to switch from Infrastructure Wifi to Peer to Peer Wifi automatically when the Wifi went down. [/quote] It did? I find that quite surprising? How did you actually test that? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

For better or worse, this is the nature of Feedback Assistant. Our bugs folks generally don’t reach out to you until there’s something to verify. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='867165022, pabugeater2, /thread/806641?answerId=867165022#867165022, /profile/pabugeater2'] because I was not changing the icon, and it had been previously cached. [/quote] OK. But you can test this by setting up a new macOS 15 machine and trying it there. I usually use a VM for this sort of thing, because it lets me quickly get back to a ‘fresh’ state by restoring a snapshot. [quote='867165022, pabugeater2, /thread/806641?answerId=867165022#867165022, /profile/pabugeater2'] it seems I learned to include two thumbnail files [/quote] Ah, that explains my confusion. Given that this isn’t documented as part of the screen saver API, it’s basically an implementation detail that you can’t rely on. Oh, and I’d be remiss if I didn’t repeat my standard spiel: The current screen saver API is based on legacy in-process plug-in technology. This results in a wide range of performance and compatibility problems. If you’re interested in having a better screen saver API, one based on app extensions, I encourage you t

There’s no explicit cancel method in the new API. Rather, our expectation is that you’d use structure concurrency, meaning that: All the use of a given connection would be within one scope. When you exit that scope, that drops the last reference to the connection. Which then cancels it. There’s a similar setup for listeners and browser, except those enforce the rules by means of their run(…) methods. [quote='808198021, captadoh, /thread/808198, /profile/captadoh'] my app crashes when I go to toggle of all the networking stuff. [/quote] Can you share an example crash report? See Posting a Crash Report for advice on how to do 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. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

What context is the agent running in? That is, what do you have set for LimitLoadToSessionType? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Someone else just posted a very similar question that my colleague is addressing over on this thread. I suggest you join the conversation over there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

There are two factors in play here, the Apple Developer website and your third-party tooling. Let’s separate them. Try this: In Certificates, Identifiers, and Profiles section of the Developer website, create a new App ID. I’d like you to share info about this App ID, so choose bundle ID that you’re comfortable posting here. During the creation process, enable the Push Notifications capability. Back in Certificates, Identifiers, and Profiles, create a new provisioning profile for that App ID. At the first screen, select iOS App Development. Check the entitlement authorised by that profile. I just did that here and this is what I see: % security cms -D -i Test808162_Dev.mobileprovision | plutil -p - { … Entitlements => { application-identifier => SKMME9E2Y8.com.example.apple-samplecode.Test808162 aps-environment => development com.apple.developer.team-identifier => SKMME9E2Y8 get-task-allow => 1 keychain-access-groups => [ 0 => SKMME9E2Y8.* 1 => com.apple.token ] } … } As you can see, t

[quote='808098021, udtt_ds, /thread/808098, /profile/udtt_ds'] [is] the main thread … the very first thread created when the process starts? [/quote] Yes. When the system starts a process, it creates within that process a single thread that is, by definition, the main thread. For an iOS app the system sets things up so that this main thread calls the main executable’s main function. The main function must call in to one of the standard UI frameworks which is then responsible for running the run loop. For example, for UIKit the main function is expected to call UIApplicationMain. Note If you’re using Swift, you can use the @main attribute to decorate a main type which then takes over the task of providing the main function and calling in to the relevant UI framework. All of the above applies to apps running on iOS and its child platforms. There are a number of important nuances on macOS. However, it’s still true that every process starts with one thread that acts as the main thread. Share and Enjoy — Quinn “Th

[quote='808201021, Wutian, /thread/808201, /profile/Wutian'] both [projects] have their deployment targets set to iOS 13.0. [/quote] Neither Xcode 26 nor Xcode 16 support iOS 13 development. According to Developer > Support > Xcode, they both have a minimum deployment target of iOS 15. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com