“eskimo”

[quote='820860021, pabugeater2, /thread/820860, /profile/pabugeater2'] I've filed FB FB22353950 [/quote] Thanks. That’s the best path forward here. Oh, except that you should file an ER for a better screen saver API, one based on app extension technology. Normally I’d include my standard spiel on that topic, but I believe that you’ve seen already. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='881933022, rkasud0, /thread/820741?answerId=881933022#881933022, /profile/rkasud0'] using an OHTTP Gateway requires an OHTTP Relay to function correctly [/quote] The story here depends on where you’re at in your development. During bring up, you don’t need to mess around with OHTTP. When you go to deploy [1], you’ll need to onboard with Apple’s OHTTP relay. See How to onboard with an Oblivious HTTP relay hosted by Apple. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] To be clear, that includes Ad Hoc distribution and TestFlight. The critical factor here is the get-task-allow entitlement, which is set to true for development-signed code and false (or missing) for distribution-signed code.

DevForums is primarily focused on APIs, so if you’re building an app that’s affected by this, or a Bluetooth accessory, please let me know. If not, my advice is that you seek help from Apple Support, either directly or on Apple Support Community. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Do you have a software product that’s affected by this? Or are you trying to report a user-level change in behaviour? Because if it’s the latter, you should do that in Feedback Assistant [1], but if it’s the former then we really need to talk about what your product is doing with the keychain |-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] See Bug Reporting: How and Why? for lots of advice here.

These two statements are at odds: [quote='882101022, Arebus, /thread/820871?answerId=882101022#882101022, /profile/Arebus'] there is nothing special here [/quote] [quote='882101022, Arebus, /thread/820871?answerId=882101022#882101022, /profile/Arebus'] just a command line tool with a Localization.xcstrings file [/quote] Doing this is special because, in general, we don’t localise command-line tools on the Mac. Specifically, the traditional Unix-y way of localising command-line tools [1] is not standard practice on Apple platforms. Rather, Apple platforms use their own mechanism, based on the bundle structure. This mechanism is intended for GUI apps, and you have to jump through hoops to get it to work from the command line [2]. If you’re doing this just for testing, I recommend that you use Xcode’s testing infrastructure. It has options for overriding the language and region. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Is any of your code involved here? Reading your description it doesn’t look like that’s the case, in which case the best place for this report is Feedback Assistant. See Bug Reporting: How and Why? for lots of hints and tips on how to file a bug. 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

[quote='820864021, matthewruzzi, /thread/820864, /profile/matthewruzzi'] FB22353186 [/quote] Thanks! I filed my own bug about this a while back (r. 92946014), but it’s always good to get external reports of issues like this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

-URLByAppendingPathComponent: is, as the name makes clear, intended to add a single path component. However, it doesn’t do anything to block you from adding a string with a path component separator, which effectively adds multiple path components. This is something I try to avoid relying because it assumes that the path component separator is always /. Way back in the day Foundation used to run on non-Unix-y platforms, where that wasn’t the case. And the Swift equivalent of this method runs on non-Unix-y platforms today. Notably, the modern Swift equivalent of this method, namely appending(component:directoryHint:), will percent encode path separators. ps File system paths are a source on ongoing grief. For a clear example of that, read this Swift Forums thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

So, DevForums is primarily focused on APIs, and thus we’re not really set up to help folks with Wi-Fi debugging issues. You might have more luck over in the Apple Support Community, run by Apple Support, and specifically in the Business and Education topic area. However, I have a couple of tips to share: Filing a Wi-Fi Bug Report is my advice on how to file an actionable Wi-Fi bug. Specifically, it talks about how to enable additional Wi-Fi logging. Your Friend the System Log offer general advice on how to use the system log effectively. [quote='820970021, Whitebengal, /thread/820970, /profile/Whitebengal'] I've submitted a couple of pieces of feedback [/quote] What were those bug numbers? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I recommend that you file a bug about this. Once you’re done, please post your bug number, just for the record. In general, frameworks that use XPC to talk to a daemon should recover if the daemon terminates for some reason. Now, you manually killing the daemon is an extra-ordinary thing, but I understand that you’re doing that just to illustrate your point. ctkd could be terminated by the system for other reasons [1], or it could crash, and the framework should handle that. Are you actually seeing this in practice? I mean, without you manually killing the daemon? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Notably, both the daemon and agent variants specifically opt in to memory pressure termination: % plutil -p /System/Library/LaunchDaemons/com.apple.ctkd.plist { EnablePressuredExit => true … } % plutil -p /System/Library/LaunchAgents/com.apple.ctkd.plist { EnablePressuredExit => true … }

[quote='820929021, g_i_i_k, /thread/820929, /profile/g_i_i_k'] Filed an issue with Apple [/quote] What was that bug number? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='820849021, AndriiSulimenko, /thread/820849, /profile/AndriiSulimenko'] Is it possible to distribute a DNS proxy provider for use on non-MDM / non-supervised devices? [/quote] No. The table in the DNS proxy section of TN3134 lists two options for iOS: app extension | 11.0 | supervised devices only | 16.0 | per-app on managed devices If you exclude those two options then you have… well… zero options. [quote='820849021, AndriiSulimenko, /thread/820849, /profile/AndriiSulimenko'] Is [this] strictly enforced at distribution/runtime? [/quote] Yes. It’s a privacy policy that’s strictly enforced at runtime [quote='820849021, AndriiSulimenko, /thread/820849, /profile/AndriiSulimenko'] Is a packet tunnel provider the only viable alternative for App Store distribution? [/quote] There are two parts to this question: Do packet tunnel providers work on general user devices? Are there a viable alternative to a DNS proxy. The answer to the first is “Yes.” TN3134 makes that clear. The answer to the second is “No.” TN3

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

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

[quote='882074022, mdtoledo, /thread/820867?answerId=882074022#882074022, /profile/mdtoledo'] It was finally approved several hours later. [/quote] Cool. This is not, in and of itself, unusual. I have a standard blurb that explains the most likely cause, which I’ve included below. 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.