Apple Maps Guides

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

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

[quote='860843022, herman602, /thread/802846?answerId=860843022#860843022, /profile/herman602'] Or can an app built with Xcode 26 also run this feature on earlier iOS versions? [/quote] No. This is a new facility in iOS 26. With that out of the way, let’s talk terminology. In app extension parlance: The container app is the one in which the appex is embedded. The host app is the one using the appex. In general, ExtensionKit lets you create a host app that invokes app extensions provided by other developers. Indeed, that’s how it works on macOS. On iOS, however, there are limitations. I’m still researching the exact details of those limitations, but it’s certainly true that iOS apps cannot host extensions created by other third-party developers (FB18784426). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='860903022, nam-common, /thread/802640?answerId=860903022#860903022, /profile/nam-common'] For example are there limits to how we can interact with the device? [/quote] An MFi accessory can support the External Accessory framework, which has a very specific communication model. Notably, it doesn’t expose a USB-like API. Rather, your accessory has to implement an MFi-specific on-the-wire protocol that ‘connects’ it to the input and output streams exposed to EA. After that, it’s up to you what commands to run over those streams. I can’t go into the details about the MFi side of this because that info isn’t public. Creating an EA-compatible accessory is a bit of a faff, so I’d definitely explore options outside of that space. For example, an off-the-shelf USB Ethernet dongle will Just Work™ with iOS, at which point you can communicate using standard networking APIs. That definitely has its limitations [1], but EA also has a bunch of limitations. And the advantage with a USB Ethernet dongle is that you can

It looks like you’re using Xcode to build an Endpoint Security system extension. If so, the following should work: In Xcode, create a new app project by choosing File > New > Project and selecting the macOS > App template. Once that’s set up, create a new Endpoint Security system extension target by choosing File > New > Target and selecting the macOS > Endpoint Security Extension template. Then do this: In the Project navigator on the left, select your project. In the Project editor — the middle pane of the Xcode window — select your Endpoint Security system extension target on the left. At the top, select the General tab. In the Frameworks and Libraries list, you’ll see libEndpointSecurity.tbd. That’s the stub library necessary to resolve the linker error you’re reporting. If you’re not familiar with the concept of a stub library, I explain that in An Apple Library Primer. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1

You can find the official answer to this in Developer > Support > Certificates. Note the emphasis on “compromised certificates”. My advice is that you not attempt to revoke a Developer ID certificate just because you’re not using it. Rather, back it up safely and keep it around just in case you need it in the future. I talk a lot more about this in The Care and Feeding of Developer ID. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I haven’t encountered this myself, but the behaviour you’re describing certainly seems strange enough to be bugworthy. Make sure to attach a sysdiagnose log taken shortly after reproducing the problem. And if you can turn your minimal repro into a small test project and attach that, we’d appreciate it. 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

Normally I avoid wading into threads like this but there have been two notable changes since this thread was created back in 2018: At WWDC 2022 Apple outlined its future directions. If you haven’t already done so, I recommend that you watch WWDC 2022 Session 102 Platforms State of the Union, and specifically Josh’s section starting at 3:43. Many new Apple frameworks are Swift only. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’d like to clarify some details of your post. Reading between the lines I believe that: You have an app for tvOS. It implements some some of media streaming. You’re seeing higher CPU usage in your app on tvOS, which affects your stream quality. Is that right? If so, I can only presume that you’re streaming video. It’s hard to imagine audio streaming using this much CPU. What Apple API are you using for this streaming? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='860845022, rozmansi, /thread/801050?answerId=860845022#860845022, /profile/rozmansi'] I have submitted two feedbacks on this issue: FB20340722 and FB20446752. [/quote] Thanks. I don’t have any insight into what’s going on here, and it seems that neither does anyone else, so sending this to Feedback Assistant is your best option. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

A negative value here is expected. Although come to think of it, the behaviour of that counter is a bit weird: If starts out at 0 / 7000, indicating that you’ve typed 0 characters and you have a budget of 7000. As you type, the first number increments. So, if you type Hello Cruel World!, it goes to 18 / 7000. At 7000 character, the value becomes 7000 / 7000. If you type one more it goes to -1 / 7000, indicating that you are 1 character over the budget. And so on. You entered a huge amount of text, 15550 characters, resulting in a display of -8550 / 7000. If you want to post a large log file, do that as a text attachment rather than inline. In the editor, click the paperclip icon. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com