Apple Maps Guides

Same issue here. I keep getting logged out and the information on most pages is unavailable. Server status looks green on the Apple Status page but this seems incorrect.

Mountain peaks don't correspond to a point of interest category you can filter for. You can see the category for a selected map item and look at the value of the pointOfInterestCategory property, which can be nil, such as for mountain peaks like Mount Whitney or Mauna Loa in the United States. Please file an enhancement request for mountain peaks to become a point of interest API, and post the FB number here for the record. — Ed Ford,  DTS Engineer

Hi @zaalup There are two parts to this: the broadcast extension code and the passthrough-in-screen-capture entitlement. First, verify your broadcast extension is working: Can you get the extension to capture video when you haven't configured the passthrough-in-screen-capture entitlement? You should be able to record the screen without this entitlement, the difference is that the captured video will show your Vision Pro's content over a black background instead of passthrough. This will help isolate whether the issue is with your extension setup or specifically with the enterprise license. Next, troubleshoot the entitlement/license setup: Do you have multiple apps from your developer account installed on your Apple Vision Pro? If so, check that none of them have expired licenses. I've seen instances where an app with an expired license can cause other apps from the same developer to behave as if their licenses are also expired. Additionally, use VisionEntitlementServices to verify your license is set

I FOUND The FIX: I saw someone else mention this here but I will reiterate because it is the only thing that worked for me. You need to contact apple developer support here: https://developer.apple.com/contact/ I had the enroll button greyed out in the app and was getting payment failed on the website. I went to the developer support site and requested a phone call. Was connecting to somebody within 2 minutes. The lady I spoke to said the website sign up is very buggy, and to use the app. I told her the button was greyed out for me, and she changed something on the back end to enable it for me. Once she did that, I was able to enroll and pay within seconds inside the app. This took me hours to solve. I hope this helps somebody else save some time.

Hello, I need some help regarding my Apple Developer Program enrollment. I purchased the Developer Program on December 3rd, 2025 at 16:03 (Turkey time). The payment was successfully processed by my bank, and I also received the official Apple Store receipt email confirming the purchase. However, my Developer account still shows: • “Purchase your membership” • “Your purchase may take up to 48 hours to process.” • Enrollment status: Pending • App Store Connect still not accessible It has now been more than X days, and the enrollment has not been activated. Here are the details: • Region: Turkey • Payment amount: 1029 TRY (local pricing for the Developer Program) • Payment status: Completed / Posted (not pending) • Case ID with Apple Support: 102769533427 • I have already opened a support case, but there has been no resolution yet. I would appreciate any guidance from others who experienced similar issues. Is this a known delay for Turkey-based accounts, or does it usually require manu

I agree that we need to handle scenarios such as force quit or unexpected termination, and we are improving those cases. However, I would still like to clarify the behavior specifically during app updates. On macOS 15, the app terminates cleanly, but on macOS 26, it is immediately killed without entering any shutdown flow. We would like to understand whether this change aligns with the AppleEvent-based quit model you mentioned. Specifically: What is AppleEvent? AppleEvents are one of the mechanisms the system uses to deliver actions into your app. As a concrete example, take this sequence: Right-click on an app’s dock icon. A menu appears. Select Quit. App quits. The menu presented in #2 is part of the Dock, NOT your app, which means your app didn't have any direct involvement with presenting that menu. The way it found out it was supposed to Quit was that it received the quit AppleEvent. The event system itself isn't all that well documented because most apps don't actually interact with it all that much. Fo