eskimo

Thanks for the confirmation. Media streaming isn’t really my forte, so I’m going to move your thread over to Media Technologies > Streaming to see if someone else can help you over there. But before I go, one general comment. If exactly the same binary sees a significant performance regression between tvOS 18 and tvOS 26 when running on the same hardware, I think that’s worth filing a bug about. So, do something like this: In Xcode, choose Product > Archive. This will give you an optimised binary. Export a Development-signed app. Install that on an A1625 running tvOS 18. And on a different A1625 running tvOS 26. Run your test. Presuming that you still see the performance problem on tvOS 26, grab a sysdiagnose log on each device [1]. Put all that info into your bug. If you do 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 [1] Per the advice in our Bug Repor

[quote='861049022, GlacierSec, /thread/802691?answerId=861049022#861049022, /profile/GlacierSec'] The isEnabled property on NEDNSSettingsManager appears to be read only. [/quote] D’oh! I missed that. In my defence, it’s read/write for all the other provider types. I’m not sure why it’s read-only just in this case. The obvious workaround is to remove the configuration but, as you noted, that’ll trigger another round of user approval when you reinstall the configuration. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Wow, this is just getting weirder and weirder. [quote='861091022, istvangg, /thread/802845?answerId=861091022#861091022, /profile/istvangg'] I’ve opened the following bug report: FB20502408. [/quote] Much appreciated. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='861037022, DTS Engineer, /thread/802640?answerId=861037022#861037022'] your accessory has to implement an MFi-specific on-the-wire protocol [/quote] FYI, that protocol is called iAP. That stands for i Accessory Protocol, where the i expands as it does with MFi. I didn’t mention that earlier because much of MFi is not disclosed publicly and, as I don’t support it day-to-day, it’s hard for me to keep track of what is or isn’t public info. However, I found the protocol name on the public MFi Program > FAQs page. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

What platform are you targeting? This matters because, when it comes to recording private data, different platfroms have different facilities. I talk about this in general in Your Friend the System Log. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='803047021, sigma2025, /thread/803047, /profile/sigma2025'] 1- What is the purpose of OID 1.2.840.113635.100.6.1.13? [/quote] In general, you can find answers to questions like this in the various docs on the Apple PKI page. In this case, you can find that OID documented in Developer ID CPS, which currently leads to Certification Practice Statement Developer ID, Version 4.0, October 16, 2024. That doc lists the OID as being critical and non-optional. An to what it means, TN3127 Inside Code Signing: Requirements has this to say on that topic: the OID 1.2.840.113635.100.6.1.13 … is present in the Developer ID Application signing certificates issued by Apple [quote='803047021, sigma2025, /thread/803047, /profile/sigma2025'] 2- Why is it marked as critical only for Turkish certificates? [/quote] That’s not my experience. Here’s a dump of my individual test Developer ID Application signing identity: % openssl x509 -inform der -in Developer ID Application: Quinn Quinn (SKMME9E2Y8).cer -text Certificate: … Si

[quote='803076021, monksoffunk, /thread/803076, /profile/monksoffunk'] This issue has already been reported via Feedback Assistant as FB20512074 [/quote] Yeah, Feedback Assistant is the right place for this… well… feedback. I took a look and at your bug and it seems to have got a little lost. I’m gonna see if I can get it back on the right path. I’ll let you know when I learn more. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi Eskimo, Thank you for your response! I’ve opened the following bug report: FB20502408. After restarting the Mail app I found that my original minimal repro no longer showed the issue, so I built a new, smaller Xcode test project and attached it to the bug report. With this test project I can reproduce the problem every time on my iPad. The additional conditions are: The email has an HTML body that contains a hyperlink. If the link is removed, the issue no longer occurs. The email has a PDF attachment generated by rendering views into a PDF context in our app. The problem appears only when the PDF is above a certain size. A sample PDF is included in the test project. Thanks for your guidance, Istvan

[quote='861033022, DTS Engineer, /thread/802846?answerId=861033022#861033022'] I’m still researching the exact details of those limitations [/quote] Hey hey, that went quicker than I expected. As things currently stand on iOS 26, an app can only host extensions that it contains. Needless to say, this significantly undermines the utility of the ExtensionKit. While it’s possible that you might find a creative use for it, there’s one specific situation where it’s super useful, namely, using an extension to host code that is either unreliable or deals with untrusted data. For more on that last point, see Creating enhanced security helper extensions. There’s obviously a lot of demand from third-party developers to broaden the scope of ExtensionKit on iOS. If you have a specific use case in mind, feel free to file an enhancement request with the details. That’s particularly important if your use case is limited in some way. As I mentioned above, we already have an ER for the sort of general support we have on macOS

I’m not sure what you’re asking for here. Based on your contribution to other threads (like here), I get the feeling that you’re looking for a sample that shows how to communicate between iOS and Android apps. We don’t have such a sample, and it’s not something I’m create for you here on the forums. If you’d like to see that, please do file an enhancement request for it. And post your bug number, just for the record. If I’ve misunderstood your message, I’d appreciate more details on what you’re looking for. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m not sure what you’re trying to convey with your latest reply. I’ve already: Explained that this is a bug. Recommend that you file a bug about it. Suggested a workaround that will at least allow your code to build. What else are you looking for? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='860886022, interferon, /thread/802423?answerId=860886022#860886022, /profile/interferon'] I filed FB20484368. [/quote] Thanks. [quote='860886022, interferon, /thread/802423?answerId=860886022#860886022, /profile/interferon'] I was worried it was related to something in my code. [/quote] You are right to be worried here. While the problem isn’t with your code, the issue could affect your code. Lemme explain… Actually, that explanation got way too long so I’ve moved the first part of it here: Waiting for an Async Result in a Synchronous Function You can think of the unsafeForcedSync code as being like the mySynchronous(…) function from that post, except that it checks whether it’s being called from a Swift async function and logs if that’s the case. That log is not just noise: It tells you that you’re potentially exposing yourself to Swift concurrency thread pool exhaustion, and hence to a deadlock. But what you do about it is one of those classic engineering trade-offs. Do you leave it for Apple to res

Ah, I thought might be the case. The simulator works a bit like macOS, where Xcode sets things up so that your app can load a framework from the build products directory. That won’t work on a real device, where the framework must be embedded in the app’s bundle. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com