Apple Maps Guides

We've developed a PCIDriverKit driver for the capture card on macOS and have identified an issue: CreateMemoryDescriptorFromClient can only read data from the user space to the driver, but cannot write data back to the user. Two answers here: I believe the immediate issue is that you also need to set kIOMemoryDisableCopyOnWrite, so your code would be: ret = CreateMemoryDescriptorFromClient(kIOMemoryDirectionOutIn | kIOMemoryDisableCopyOnWrite, ... The other option, particularly if you're dealing with larger amounts of memory that you'll be using for things like ring buffers, is using IOConnectMapMemory(...) and CopyClientMemoryForType(...) to more directly manage the mapping process. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

@RickMaddy I think that might be a little out of scope for this thread. But in any case, I was able to update my macOS 26.1b2 VM to 26.1b3 via my logged-in Apple Account, so I don't think it's universally broken. Although my host is still on Sequoia 15.7.1. The closest thing I've experienced to what you're describing is an issue that I've seen for a while where logging in with an Apple Account hasn't been working for me if I have physical security keys enabled on my account for 2FA (FB19614234). Unfortunately if you're in this situation I don't know of any workaround other than removing all the security keys (and even if you re-enable them after logging in with the VM, eventually the VM will start complaining with pop-ups asking you to login again, although beta updates will still work despite this). This isn't new to 26.1, though. If this isn't the issue you're experiencing you might find better luck creating a new thread since I don't think many people with similar issues are going to find

Kevin and ssmith_c for your assistance. I fortunately managed to file in the bug: FB20677188 Thank you! Looking over the bug, there was one point I wanted to comment on: For the Matter Media Device Basic Video Player Type Apple Home does support the commissioning (adding the device to the list of accessories displayed in Home App), but no controls are displayed. Not even the mandatory required controls: ... This type of Matter Device, which is part of the standard, should at least expose the mandatory controls and commands. The idea that Apple (and general ecosystem vendors more broadly) should try and support the full range of the Matter specification is, IMHO, one of those ideas which sounds reasonable on the surface but is, in fact, a very bad idea. First off, quoting myself: The Matter specification itself is sufficiently broad and complex that, in practice, I'm not sure it will ever really be possible to create a high-quality controller app* that actually supports EVERY possible accesso

We appreciate your interest in participating in the forums! These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to a consumer feature and is better suited for the Apple Support Communities https://discussions.apple.com/welcome Albert Pascual
  Worldwide Developer Relations.

The value shown there is the LLVM/clang/swiftc target triple that Swift Testing used when Apple compiled it. Swift Testing's minimum deployment target (the lowest version of the OS you can run it on) is iOS 13, so the target triple shows iOS 13.

I am working on a Gaussian Splatting App using the UnityGaussianSplatting package and building for Apple Vision Pro. I want to be able to load splat (.ply / .splat) files from the Vision Pro's storage into the application. OK. So the main issue to be aware of here is the difference between works fine for a developer and works well for a user. For development purposes, you can basically just set the two keys (UIFileSharingEnabled/LSSupportsOpeningDocumentsInPlace) and then use your Documents directory as your working storage. There could be issues if you edited or deleted those files while your app was actively running, but you will just avoid those issues... by not doing that. On the other hand, if you're planning to ship this to end users then you'll need to use things like file coordination to avoid those issues. Similarly, apps that are more viewer oriented (meaning, they don't edit the files they're working with) often use an import model where they copy (actually clone, so they don't use additio

I can't give legal advice on whether potential actions violate the terms of developer agreements. I suggest that having your customers manage their own MDM push certificates makes sense from the point of view of segmentation of risk. MDM is a very powerful technology, and rarely people abuse it. When Apple becomes aware of abuse of MDM it may take various actions in response. These actions may include revoking the MDM push certificate involved in the abuse, revoking the MDM vendor certificate associated with the MDM push certificate, removing the MDM CSR permission, and/or terminating any Apple Accounts, Apple Developer Program accounts, or Apple Developer Enterprise accounts associated with those certificates. As a device management service vendor, consider if one of your customers abuses device management capabilities and Apple revokes the MDM push certificate and the associated Apple Account. If your device management service used the same MDM push cert

Well the new Liquid Glass design language is also terrible. They have taken an elegant and refined UI and added quite superficial flourishes to it that just eats screen real estate and undermines legibility. And it's not even consistent! Even if the next MacBook has touch, as some rumors claim, this was NOT the way to accommodate it. But removing Launchpad actually removes useful functionality. I can't imagine how this was justified. In addition, search for apps is broken! This is a known bug and after weeks there is no Mac OS update in sight to fix it. This is negligent and incompetent conduct on Apple's part. I dont know what is going on inside the company but it's not good.

Same issue here on MacOS Tahoe. This issue makes the official Apple guide from https://developer.apple.com/library/archive/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html#//apple_ref/doc/uid/TP40010220-CH213-SW16 outdated.

Hi @AndreiAvram99 Thanks for the post. Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. I'd greatly appreciate it if you could open a bug report and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating your bug report. In the meantime, I confirmed (and suspect you already have too) the dialog displays correctly when requestReview is invoked from within a view displayed in a window or volume.

Is tap to pay still needed? i don't want to read passes from wallet nor accept payments. I want to use nfc card reader on the credit card from the bank i work for in the bank of the app i work for to validate the card and activate it. I don't see how it would be related to tap to pay or wallet. we already have apple pay setup but we still get an error about the entitlements missing. So i'm wondering which one i need and if i need to do a specific request to have them knowing we are a bank and already have com.apple.developer.payment-pass-provisioning

Fitness app only shows data from Apple watch while Health app shows data from all sources. This is why you see a discrepancy.