Apple Maps Guides

Earlier I wrote: [quote='867857022, DTS Engineer, /thread/806187?answerId=867857022#867857022'] And, no, I don’t have any info to share as to when that fix will actually land. [/quote] As others have noted, this is still present in the macOS 26.2 Release Candidate. Given that, it’s very likely to remain unfixed in the final release of macOS 26.2 )-: and I recommend that you plan accordingly. Beyond that, I still have no specific info to share. But, as always, it’s a good idea to test with new betas of macOS as and when we seed them. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Multipeer Connectivity hasn’t worked over Bluetooth for 10-ish years. On modern systems its peer-to-peer support is based entirely on peer-to-peer Wi-Fi. Historically, Multipeer Connectivity wasn’t the only option for accessing peer-to-peer Bluetooth. Even after peer-to-peer Bluetooth was no longer enabled by default, you could still access it via lower-level APIs or an explicit opt in [1]. However, that’s not been the case for a long while also. At some point we disabled the opt in [2] and eventually we removed the implementation entirely. My general advice is that you: Not use Multipeer Connectivity at all. See Moving from Multipeer Connectivity to Network Framework Forget about peer-to-peer Bluetooth, and rely on either peer-to-peer Wi-Fi or Wi-Fi Aware. However, I wanted to address your case specifically: [quote='809565021, AppDevVa , /thread/809565, /profile/AppDevVa+'] We have a requirement for device-to-device communication … without requiring Wi-Fi connectivity. [/quote] What’s the rationale for the p

[quote='809562021, hpux735, /thread/809562, /profile/hpux735'] Has the functionality been walked back such that extensions can only be loaded in iOS from within the single app bundle? [/quote] I wouldn’t say “walked back” because full ExtensionKit support was never a feature of iOS. Well, I guess you could considered it to be walked back relative to macOS… Anyway, see my replies on this thread for the current state of affairs. [quote='809562021, hpux735, /thread/809562, /profile/hpux735'] What's the best way to achieve this? [/quote] There’s no way to achieve that goal for native code. If you’re willing to entertain the idea of non-native code then you have various options, the most obvious being: Support JavaScript via JavaScriptCore. Support Wasm with your own runtime [1]. Keep in mind, however, that this is only the technical side of this coin. On the business side, I want to be clear that I don’t work for App Review and thus can’t give definitive answers about this policy. I recommend that you review thei

See my replies on this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

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

No one here can help you. If you can't uninstall the profiles yourself (have you even tried? you don't actually say), then go to an Apple Store and ask for help there. These are the Developer Forums, where developers of third-party apps for Apple's platforms ask each other for hints and tips on coding. You're in the wrong place.

Cool. And, yeah, based on reports here on the forums, that seems to be a common pattern. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

One thing I have noticed about the sandbox testing account is that it will still return the value of false for AgeRangeService.shared.isEligibleForAgeFeatures even if you have a valid scenario selected from the developer menu, if you happen to be signed into your sandbox account via the standard iCloud sign in flow (like how one would for Apple Pay sandbox accounts) You must make sure you are not signed into your sandbox account anywhere else on the test device other than in the developer settings.