Apple Maps Guides

Hello, I am writing this post because the Apple Developer Program enrollment process is clearly malfunctioning, and I have reached a point where this situation is unacceptable. First payment I initially purchased the Apple Developer Program on December 3rd, 2025 at 16:03 (Turkey time). The payment was fully completed, confirmed by my bank, and I received the official Apple Store receipt. • Order ID: W1557478965 • Amount: 1029 TRY • Status: Completed / Posted Despite this, my account continued to show: • “Purchase your membership” • Enrollment status: Pending • No access to App Store Connect After several days with no response from Apple Support and no activation, I assumed something had gone wrong on Apple’s side. Second payment Because I was completely blocked and received no reply from support or the forums, I made a second payment to rule out any payment failure. • Order ID: W1694587309 • Amount: 1029 TRY • Status: Completed / Posted Current situation At this po

In MapKit, the MKAnnotation takes a CLLocationCoordinate2D. However, in 3D/Flyover mode, the user marker has a height position on the map. We are currently plotting points which have altitude, speed, heading, etc, and I have a method for creating a CLLocation with this information. What I'm trying to figure out is if there's a way to pass that information along to the MapKit rendering engine / annotations / AnnotationViews to recognize and show when in 3D mode. Is there any support for that currently?

Hello, I’m reviewing the open-source mDNSResponder repository and have a question regarding licensing/provenance in mDNSCore/DNSDigest.c file. That file contains an embedded notice stating that parts of the MD5/digest implementation were derived from older OpenSSL sources and therefore include the legacy OpenSSL/SSLeay license text, even though OpenSSL itself is now Apache-2.0 starting from version 3.0. The legacy OpenSSL/SSLeay license is widely understood to impose additional attribution and notice requirements compared to Apache-2.0, and some downstream projects prefer to avoid it when a permissively licensed alternative is available. Repository: https://github.com/apple-oss-distributions/mDNSResponder File: https://github.com/apple-oss-distributions/mDNSResponder/blob/main/mDNSCore/DNSDigest.c#L66 I’d like to clarify a few points: Is the MD5/digest code in DNSDigest.c still based on pre–OpenSSL-3.0 sources, such that retaining the legacy OpenSSL/SSLeay license block is intentional and re

I received the email from Apple entitled Final reminder: Answer the updated age ratings questions. However if I login to App Connect, or click on the link in the email to go directly to App Connect, there are no questions. There are 6 tabs/sections in App Connect, flicking through them, there are no questions about age ratings. Even if I could find these questions, if there are no apps actually released to the App Store (and no plans to release any) is answering these questions necessary? The Apple email sounds quite threatening in its tone, hinting at consequences if you don't comply, but I can't comply because no questions in App Connect are being presented.

My app updates are repeatedly rejected under Guideline 2.3.6 – Accurate Metadata, with a request to remove “Age Assurance” unless the feature can be located. However, the app does include age assurance. During onboarding, users must enter their date of birth, and users under 16 are blocked from completing registration and using the app. The app contains a women’s health blog and a community Q&A feature (similar to Reddit), where users can ask and answer health-related questions. For this reason, I am considering restricting access to users 18 and older. Each time I explain this to the review team and provide a screenshot of the DOB screen, the app is approved. What is the correct way to document or surface this in App Store Connect so reviewers can easily find it and avoid repeated rejections? Is a DOB gate sufficient for Apple’s definition of Age Assurance?

Hi everyone, I am seeking urgent advice or attention from the App Review team regarding a Pending Termination Notice I received for Section 3.2(f). The Situation: I recently acquired a portfolio of apps from another developer to start my business on the App Store. Three months after the transfer, my account was flagged for removal because one of these acquired apps repeatedly violated guidelines to evade the review process. The Problem: I am being punished for the previous owner's actions. I have never submitted a new build, metadata update, or review request for this specific app since acquiring it. The Timeline (Proof of Innocence): August 4, 2025: Last update submitted by the Previous Owner. September 6, 2025: I signed the Purchase Agreement to start my business. September 9, 2025: App Transferred to my account. December 11, 2025: Termination Notice received. As the timeline proves, the alleged evasion attempts via submissions occurred before I even owned the app. Regarding Unresolved Issues: I am aware th

Hi Apple Staff / App Review Team, We’re following up because we haven’t received a substantive reply to our previous forum post or our messages in App Store Connect. Context (unchanged): Our last update focused on performance/stability, bug fixes, and numeric balance tuning (difficulty/rewards). We also added a small, user-initiated News panel (globe icon in the main menu) that displays one static announcement image and can be closed at any time. There are no links, no navigation, no login/UGC/ads, and no executable content in that panel. We don’t collect personal data (no IDFA/ATT). Safeguards already in place: Post-release changes are restricted to numeric balance values only (no feature toggles, no navigation changes). The announcement is strictly read-only (one static asset from our own domain) with an offline fallback. Internal release policy forbids any post-review feature switches or concept changes. What we’re asking for: Specific guidance on what observation(s) led to the 3.2(f) determinatio

Hello All, I want to implement Text-to-Speech (TTS) and vibration functionality when a push notification arrives. In my app, I am already using Critical Alerts, and the critical alert sound plays correctly in all app states. However, I need to confirm whether it is possible to trigger Text-to-Speech and custom vibration in all app states: Foreground Background Terminated (killed) state My Questions: Is it technically possible for iOS to run Text-to-Speech (using AVSpeechSynthesizer) when a critical alert notification arrives in background or terminated state? Is it possible to trigger custom vibration patterns from a critical alert when the app is not running? If yes, can someone please provide guidance or sample code on how to implement this? If no, can Apple explain the limitation or provide documentation confirming that TTS and vibration cannot be triggered in background/kill states? What works currently: TTS and vibration only work in foreground when the app is active. Critical alert sound works

Hey all, Running into an issue with a WeatherKit. Whenever I make a WeatherKit API call, I get this error: Details: { domain: WeatherDaemon.WDSClientErrors, localizedDescription: invalidAuthorization: 401, underlyingError: Unknown, code: 3 } This only happens when calling via the Swift package: swift WeatherService.shared.weather(for: location).currentWeather When I was calling the WeatherKit REST API directly from Dart, everything worked fine. So far I’ve: Enabled WeatherKit in the Apple Developer account Added the WeatherKit capability to the app Refreshed provisioning profiles Installed the app fresh on device/simulator Has anyone seen this specific invalidAuthorization: 401 from WeatherDaemon.WDSClientErrors when using WeatherService in Swift, and know what might be missing or misconfigured?

I want to enable developer program but after submitting the enrollment I see: Your enrollment in the Apple Developer Program could not be completed at this time.