Apple Maps Guides

See Resolving Error 65 When Stapling. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It looks like you’re trying to file a bug report, which isn’t really what DevForums is about. Rather, you should file this in Feedback Assistant. See Bug Reporting: How and Why? for lots of hints and tips on this process. 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

I have a two part answer for you: Entitlements Networking On the entitlements front, I recommend that you review the table in Developer Account Help > Reference > Supported capabilities (iOS). The Apple Developer column shows all the capabilities available to folks using free provisioning, aka a Personal Team. There’s no supported way to use capabilities that aren’t listed there. On the networking front, you wrote: [quote='803362021, ImmuneFOMO, /thread/803362, /profile/ImmuneFOMO'] Bonjour networking between Mac and iPhone for session coordination [/quote] You don’t need the multicast entitlement if you’re using Bonjour [1]. You only need that entitlement if you’re sending and receive multicasts yourself. If you’re having problems getting Bonjour to work, I recommend that you work through the steps in Getting Started with Bonjour. That doesn’t help you with Family Controls, alas )-: Oh, I should mentioned one other thing: Many educational institutions have their own developer team. If that’s t

Have you jumped through all the hoops so that your app can actually send Apple Events? Here is some old documentation that might be a good starting point: https://developer.apple.com/library/archive/qa/qa1888/_index.html The application isn't sandboxed, so I didn't add any additional entitlements and it should not matter. Moreover, if it was sandboxed I'd expect some kind of error in the console regarding sandboxing limitations, as it usually happens in such cases. But in this case, everything is silent (but doesn't work). NSAppleEventsUsageDescription should not matter either, but even with that added, nothing changes. Any new code that relies on AppleScript is risky. Apple is already transitioning to Shortcuts. And Apple has begun to be much more aggressive about deprecating and discontinuing technologies, pretty much all of which are much recent than Apple Events. I realise all that. However, I don't see why I wouldn't use it while it's still there and hasn't been deprec

Generally, a sandbox violation doesn’t cause the process to crash. Rather, it blocks a specific operation. Of course, it’s possible for the process to crash because it got an error it wasn’t expecting (-: Anyway, does this crash generate a crash report? If so, please post it here. 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 started a couple of other ExtensionKit threads (here and here) and it’s not clear why our answers there are sufficient to address the issue being discussed on this thread. If not, please reply here with a status update and I’ll take another look. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='786976021, rbmanian75, /thread/786976, /profile/rbmanian75'] I’ve … used the modern CSImportExtension approach with a Spotlight Importer extension target. [/quote] Have you see this thread? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='803426021, suzsfot, /thread/803426, /profile/suzsfot'] Many developers in Chinese forums have provided feedback on this issue [/quote] Generally? Or to Apple? If anyone has filed a bug about this, I’d appreciate it if you posted the bug number here. Frankly, this looks like something that needs to be investigated by Apple’s network engineering teams. For that to happen, someone needs to file a bug about it. Ideally, that bug would include: A small test project that demonstrates the issue. It’d be best if you wrote this using Xcode and Apple’s APIs, rather third-party tooling, because that rules out the third-party tooling as a source of this issue. A sysdiagnose log taken shortly after reproducing the problem. On a device with Network Diagnostics debug profile installed. Get that from our Bug Reporting > Profiles and Logs page. An RVI packet traces showing the working case on iPhone 16 and the failing case on iPhone 17. However, this is the ideal situation. If you’re not

Any help is highly appreciated, thanks! Have you jumped through all the hoops so that your app can actually send Apple Events? Here is some old documentation that might be a good starting point: https://developer.apple.com/library/archive/qa/qa1888/_index.html And here is a previous question from someone managed to get it working, after a fashion: https://developer.apple.com/forums/thread/771769 Any attempt to script the Finder is going to limit your app. It won't be acceptable for the Mac App Store. Any new code that relies on AppleScript is risky. Apple is already transitioning to Shortcuts. And Apple has begun to be much more aggressive about deprecating and discontinuing technologies, pretty much all of which are much recent than Apple Events. In older apps where I still did such things, I had good success with running the osascript command-line tool with carefully constructed parameters.

[quote='804647021, Fat_Panda, /thread/804647, /profile/Fat_Panda'] can I edit the current certificates so that they don't expire soon? [/quote] You can’t edit certificates. They must be issued by Apple, and that requirement is enforced by Cryptographic Goo™. For Apple Development and Apple Distribution code-signing identities, I generally enable automatic code signing in Xcode and let it take care of all the details. That works really well. Finally, be aware that if you’re targeting the App Store your distribution certificate only needs to be valid at the time you submit the app. The app then gets re-signed by the App Store, using an Apple signing identity, and so the expiration date of your code-signing identity’s certificate is irrelevant. For lots more background to this, see TN3161 Inside Code Signing: Certificates. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='804450021, nikhil2701, /thread/804450, /profile/nikhil2701'] does it automatically decide which interface to pick? [/quote] Yes. There’s no way to avoid that if you’re using TCP. That protocol necessarily runs over a specific interface, and if there are paths via multiple interfaces the system has to pick one. [quote='804450021, nikhil2701, /thread/804450, /profile/nikhil2701'] Happy Eyeball algorithm but that seem to point more towards ipv4 vs ipv6 [/quote] While Happy Eyeballs was introduced to improve the IPv6 experience, it’s not exclusively about the IP version. Rather, it starts candidate connections across multiple network paths and then races them, discarding the ones that don’t win that race. See Understanding Also-Ran Connections. IPv4 and IPv6 are different paths, but so are infrastructure and peer-to-peer Wi-Fi. Happy Eyeballs is a general description of the approach and Apple platforms implement a lot of smarts on top of that. I suspect you’ll find a strong preference for infrast

This isn’t something I can help you with. There’s no API that specifically identifies a domain associated with Software Update, so you’re relying on implementation details published by Apple Support. That’s not something I can speak too. Rather, my advice is that you file an enhancement request for a specific API for identifying Software Update flows [1]. Please post your bug number, just for the record. I’ve updated the subtopic of your thread to see if I can attract other folks to it. If not, you might have better luck asking this question over in the Apple Support Community, run by Apple Support, and specifically in the Business and Education topic area. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] There’s precedent for this, namely the various excludeXYZ properties in NEVPNProtocol.

I’d like to clarify your issue. My understanding is that: You have an iPhone with cellular networking enabled. You enable Personal Hotspot on it. On some other device, you join that Wi-Fi network. In some cases things go wrong, meaning that the device from step 3 can’t access the Internet. Is that right? If so, what sort of device are you use in step 3? Another Apple device? Or something else? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

There seems to be some missing info here, namely the behaviour of your NE filter. Are you testing this with a ‘pass through’ filter, that is, one whose handleNewFlow(_:) method returns allow() in all cases? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com