“Apple Maps Guides”

[quote='822456021, ParinK124, /thread/822456, /profile/ParinK124'] I am loving it! [/quote] Cool. [quote='822456021, ParinK124, /thread/822456, /profile/ParinK124'] Is there any other apps that help me to learn coding? [/quote] It kinda depends on your direction: Are you looking to learn Swift programming in general? Or looking to learn Swift programming so that you create iOS apps? Or something else? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='884173022, rbmanian75, /thread/822025?answerId=884173022#884173022, /profile/rbmanian75'] it seem to be that VZVmnetNetworkDeviceAttachment is only avaialble for mac os 26 [/quote] Right. I don’t see a good option for earlier systems. Internally we bounced around the idea of looking for a record of the VM’s MAC address in the ARP cache but, honestly, I’m not a fan of that idea. It’s easy to imagine various ways it might go wrong. [quote='884173022, rbmanian75, /thread/822025?answerId=884173022#884173022, /profile/rbmanian75'] i would like to do the port forwarding. [/quote] It looks like you’re making progress on that. If you get completely stuck, I recommend that you start a new thread so that we can keep this thread focused on the IP address issue. Use the same subtopic and tags as this thread; that way I’ll be sure to see it go by. Coming back to your IP address issue, it seems like you’re trying to share a vmnet interface between all your VMs. I think that’ll work in general, but it presents a pro

spctl is not a great way to check whether a program will run. Rather, I recommend that you do an end-to-end test, as explained in Testing a Notarised Product. Oh, and two minor things. First, when you run an assessment with spctl you have to pass in the correct assessment type via the -t option. install is not correct for command-line tools. You want to use exec. Second, I noticed you’re signing code with sudo. That’s something we specifically recommend against. See Creating distribution-signed code for macOS. In many cases it’ll work, but it also send you off into the errSecInternalComponent weeds. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

HomeKit is an outlier in that it’s supported on the Mac but only for Mac Catalyst apps. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I wouldn’t characterise this as a bug. If you set the atomic flag then the file wrapper will either work or, if something goes wrong, leave the destination unchanged. The system has to jump through extra hoops to provide this guarantee. OTOH, if you don’t set that flag then you’re telling the system that you don’t care about the state destination in the error case. The system is free to choose whatever writing techniques that it finds convenient. This is a valid choice if, for example, you’re writing to a temporary file, but it doesn’t look like that’s the case for you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='883989022, DTS Engineer, /thread/822361?answerId=883989022#883989022'] If the issue originates from your own codebase rather than a compiled third-party SDK, you can identify and resolve it at the source code level. [/quote] Out of curiosity, what if it doesn't? Part of our issue was that we were using a third-party library to access HealthKit and that library being a general purpose one, contained some references to the API the Apple Store Connect wanted us to remove. Our solution was to fork the library and remove the references from it ourselves, but I am curious if there's a better approach. [quote='883989022, DTS Engineer, /thread/822361?answerId=883989022#883989022'] Apple’s review process examines the binary for linked frameworks and symbol references. You can perform the same checks locally or within your pipeline before the build is submitted to QA. [/quote] Once we are made aware of it, sure. But you are talking about checks that we would implement ourselves, right? I was r

This is a terrible bug. I’m not surprised at all, though, since Xcode itself has always been a terrible application. Doesn’t Apple have any competent Xcode developers?

Thanks for filing FB22476701. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m gonna start you out with SecItem: Fundamentals. It explains how you should think about the keychain. Once you internalise that, a lot of its behaviour makes sense. As to what’s going on here, it’s hard to say without more context. My first question is: What platform are you on? This matters because, if you’re on the Mac, the keychain has a lot of additional complexity. TN3137 On Mac keychain APIs and implementations explains the details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Sadly, I can’t read Chinese, so I’m answering based on a machine translation. My understanding is that: The 511 limit is a default. The hard limit is 999. You can control this via sysctl with the kern.tty.ptmx_max selector, for example: % sudo sysctl kern.tty.ptmx_max=800 kern.tty.ptmx_max: 511 -> 800 Please try that out and let me know how you get along. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s focus this discussion in your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com