Apple Maps Guides

Hi @SuyashBel, To run Foundation Models in Simulator, ensure that macOS is up to date. Utilizing Foundation Models framework in the Simulator requires macOS Tahoe, with Apple Intelligence enabled on the Mac. (System Settings -> Apple Intelligence) This will trigger a download of the model, which can also take a little time. Additionally, make sure the simulator is running 26 or later. It can also be helpful to ensure you're using the latest version of Xcode. If everything is updated and you're still having trouble, try restarting your Mac. If all that still fails, let us know and also please file Feedback so we can track this issue. Best, -J

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.

Thanks for the post, I have only questions for you to narrow down and make sure I understand the platform not working. Can you provide me the version of Xcode and what simulator are you using to ensure that the simulator you're using is compatible with the Foundation Model framework. Since your M1 Air and iPad Pro M5 are both Apple silicon devices, the simulator should generally support the latest frameworks. Make sure you have the latest version of Xcode installed. Update the simulator images to the latest version available. If possible, try running your app on a different simulator that you know works well with your app. You can choose from a list of simulators available in Xcode. Can you provide me that? Can you provide me exactly the error you are getting in the simulator. Look at the error logs in Xcode for more specific information about what might be causing the issue. This can help in diagnosing the problem more accurately. If possible, test your app on a real device using the same model as y

The updated profile is now live and can be downloaded from this link (found inside the Apple Matter OTA - User Guide). __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Thank you for your post. We recommend you sign up for a session with App Review during the weekly Meet with Apple event. Sign in with your Developer ID and select Request a one-on-one App Review consultation. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines.

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to this thread. Bug Reporting: How and Why? has tips on creating your bug report.

With the same firmware, OTA testing on the DCL test network was successful in September 2025, and the Home app was able to deliver software update notifications. Since the beginning of 2026, however, the Home app no longer delivers software update notifications. Are you sure about exactly when this started failing? It looks like the TestNet DCL mobile config file (see section 3.2.3. Profile enablement of Apple Matter OTA - User Guide r4) expired on February 7th, at which point this would have stopped working. . I'm working on getting an updated profile released, however, the existing profile should have worked until then unless something else was going wrong. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

However, we have struggled to find comprehensive technical documentation or specifications regarding the WAC service. Could anyone point us to the official source for these materials? WAC is documented and licensed through the MFi program. For technical questions, the MFi program has its own support process, described in the Developer Technical Support of the MFi Licensing Handbook. You can find all of the necessary specifications in the Content Center of the MFi Portal. I have a few comments below, but more detailed support needs to go through the support process I mentioned above. We are testing WAC provisioning and found that the Home app can discover our device and successfully get it online. However, it always ends with a Failed to add accessory message. Does WAC support imply that a device should be addable via the Home app? Sort of. I'm not sure Home.app is expected to pair all WAC accessories, but AirPlay 2 accessories can be paired through Home.app and placed into that home. Note that the accessory s

Thank you for your post. We recommend that you sign up for a session with App Review during the weekly Meet with Apple event. Sign in with your Developer ID and select Request a one-on-one App Review consultation. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines.

No, still no response from Apple other than the one above. The last review that was completed for me was on Jan 25.

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. In my experience problems like this, where an app talking to a Wi-Fi accessory works generally but fails on a small fraction of iOS devices, are most commonly caused by the app assuming that the Wi-Fi interface is en0. We talk about this in TN3179 Understanding local network privacy, but I have a bunch of additional information related to this in the various posts linked to by Extra-ordinary Networking, including: Don’t Try to Get the Device’s IP Address Broadcasts and Multicasts, Hints and Tips Working with a Wi-Fi Accessory So, I recommend that you start out by searching your codebase for en0. If you have that hard-coded somewhere in your network code, you need to fix that. If that’s not the problem, reply back here and we can dig deeper. In that case, I’d appreciate you sharing details about the UDP protocol used by your app. Does it involve broadcasts? Or multicasts? And what does t