Overview

I'm building a sleep tracker for couples — the headline feature is a notification to your partner the moment you fall asleep (and another when you wake up), detected on the Apple Watch from accelerometer and heart-rate data. The detection has to happen within minutes of onset for the product to make sense. My setup HKObserverQuery on heart rate with enableBackgroundDelivery(.immediate), re-registered on foreground. WKApplicationRefreshBackgroundTask rescheduled every 15 minutes. CMSensorRecorder.recordAccelerometer(forDuration: 12 * 3600) re-armed on every wake. A van Hees-style stillness classifier reading the last ~35 minutes of the buffer, with heart rate as a soft confirmer. HealthKit and Motion & Fitness authorized on both iPhone and watch. The observer's completionHandler() is called on every branch and the handler stays well under the 15-second watchdog. No HKWorkoutSession as my app is not a workout. Questions Is CMSensorRecorder paused or deprioritized while the Apple Watch's automatic sleep detection has classified the user as asleep? On a worn watch with the recorder armed for 12 hours, accelerometerData(from:to:) over a 35-minute window inside the auto-detected sleep period returns zero samples. The exact same call an hour later, once the watch has decided the user is awake, returns roughly ten thousand samples for an equivalent window. The user never activated Sleep Focus or Theater Mode — the only sleep-related state at play is the watch's own automatic detection, the same one that writes Core / REM / Deep stages into Apple Health. Is this documented power management I missed, or is it unexpected? Happy to file Feedback with a sysdiagnose during the window if you confirm it shouldn't behave this way. Is there a sanctioned non-workout path on current watchOS for detecting sleep onset within a few minutes of it happening? A full night recently produced a five-hour stretch with zero observer callbacks and zero background-refresh deliveries between bedtime and wake. The historical guidance to third-party sleep apps has been to reconstruct nights post-hoc from sleepAnalysis samples rather than attempt live detection. Is that still the recommendation today, or is there an API I've missed that would give an onset-focused app tighter wakes around bedtime? What is the current App Store review stance on HKWorkoutSession for sleep tracking? Would an app that auto-starts a .other / indoor workout only when its own classifier detects pre-sleep signals at the user's typical bedtime, ends the session as soon as onset is confirmed, never starts one outside that gated condition, and explicitly discloses "sleep tracking via workout session" in the App Store metadata — be an acceptable pattern, or grounds for rejection regardless of disclosure?

In the Fitness app under iOS 26, each workout location is displayed on a small map. For workouts with routes, I can already successfully read out the route and thus also determine the starting point. So that works. For indoor workouts such as yoga or indoor rowing, the exact location is also displayed in the Fitness app. I would now also like to read out this location for these indoor workouts in my app. Does anyone know how to do this?

Hi, Overview I would like to add a Swift Package to my Xcode project. Problem In Xcode when I select Project > Package Dependencies and Press + button to add a dependency it keeps spinning and doesn't end Points to note: Xcode 26.5 (17F42) macOS 26.5 (25F71) This is a private GitHub repository I am able to clone the Swift Package URL on the command line. Xcode has the GitHub account I am able to push and pull code on that GitHub account using Xcode My failed attempt rm -rf ~/Library/Developer/Xcode/DerivedData rm -rf ~/Library/Caches/org.swift.swiftpm plutil -remove IDESwiftPackageAdditionAssistantRecentlyUsedPackages ~/Library/Preferences/com.apple.dt.Xcode.plist I have removed GitHub account in Xcode and added it again I am confused if I am missing something very obvious, any help on this is much appreciated. Questions Is there any workaround or way to fix this issue? Why does this take such a long time when I have a specific URL, either it needs to add it or return that the package is not found. Why is it searching?

Hello everyone, We are experiencing a serious issue with consumable In-App Purchase products in App Store Connect and could not find a clear solution. Our app previously had approved In-App Purchase products. Later, we removed the old products from sale, deleted them, and created new consumable IAP products with new product identifiers. The new products are: Points_50 Points_100 Points_250 Points_500 Points_1000 Points_2500 These products are used in the live app’s Points Store. The problem is that the live production app now depends on these new product IDs, but the products have not been approved yet. Because of this, prices are not displayed correctly in production and users cannot complete purchases. The IAP products have now been stuck In Review for about one week. Here is the timeline: We created the new consumable IAP products and submitted them for review. They were rejected under Guideline 3.1.1 with the following message: “We have begun the review of your In-App Purchase products but are not able to continue because you have submitted In-App Purchase products for the Consumable type, but you have not yet submitted an updated binary for review. To resolve this issue, please upload a new binary and resubmit the In-App Purchase products for review.” We followed this instruction. We uploaded a new binary and submitted a new app version for review. In the App Review Notes, we clearly explained that the new version was submitted because App Review requested an updated binary for the pending consumable IAP products. The new app version was approved. However, the six IAP products are still stuck In Review and have not been approved. The confusing part is that the In-App Purchases page still shows the following general message: “Your first in-app purchase must be submitted with a new app version. Create your in-app purchase, then select it from the app’s In-App Purchases and Subscriptions section on the version page before submitting the version to App Review. Once your binary has been uploaded and your first-in app purchase has been submitted for review, additional in-app purchases can be submitted from the In-App Purchases section.” However, these are not the first In-App Purchases ever created for this app. The app previously had approved IAP products. The old products were removed from sale and deleted, and the app now uses the new product identifiers listed above. Because these are not the app’s first-ever IAP products, when we uploaded the new binary and submitted the new app version, App Store Connect did not show an “In-App Purchases and Subscriptions” section where we could manually attach or select these pending IAP products. This makes the request to “upload a new binary and resubmit the IAP products” confusing in our case. We did upload a new binary, the app version was approved, but there was no way to manually select the IAP products on the version page, and the IAPs are still stuck In Review. We have already contacted support several times, but the issue is still unresolved. Has anyone experienced a similar situation? What is the correct workflow when: an app previously had approved IAPs, those old IAPs were deleted, new consumable IAPs were created, App Review requested a new binary, the new binary was uploaded and approved, but App Store Connect did not show any IAP selection section on the app version page, and the IAP products remain stuck In Review for about one week? Is there any way to manually associate these pending IAP products with the approved app version, or is this something that only App Review / Developer Support can resolve? Any guidance would be appreciated.

Hi, My app was rejected on May 24 with guideline violations 2.3.10 and 1.1. I fixed both issues and resubmitted the same day. It's now been 4+ days and the status is still "Waiting for Review" with no movement. This update also includes a critical bug fix that needs to reach users as soon as possible. I submitted two expedited review requests — no response. Contacted Developer Support as well — case ID 102900051339, also no response yet. Is this normal after a rejection + resubmit, or is something stuck on the review side?

I have a small example where adding a new property to a persisted Codable struct causes a crash on launch instead of decoding the missing property using its default value. Steps Run this app once and press "Insert Event" to persist data: import SwiftUI import SwiftData @main struct SwiftDataCrash: App { var body: some Scene { WindowGroup { ContentView() } .modelContainer(for: Event.self) } } struct ContentView: View { @Environment(\.modelContext) private var modelContext @Query private var events: [Event] var body: some View { VStack(spacing: 12) { Text("Events: \(events.count)") Button("Insert Event") { let event = Event( recurrence: Recurrence( interval: 1 ) ) modelContext.insert(event) try? modelContext.save() } List(events) { event in Text(String(describing: event.recurrence)) } } .padding() } } @Model final class Event { var recurrence: Recurrence? = nil init(recurrence: Recurrence? = nil) { self.recurrence = recurrence } } struct Recurrence: Codable { var interval: Int // STEP 2: // After first run + inserting an Event, uncomment this and run again. // Expected: old data decodes with default [] // Actual: SwiftData may crash while reading Event.recurrence // // var exceptionDates: [Date] = [] } Then uncomment: var exceptionDates: [Date] = [] and run again without deleting the store. Actual result App crashes on launch with: Could not cast value of type 'Swift.Optional<Any>' to 'Swift.Array<Foundation.Date>' The crash appears to happen inside generated SwiftData persisted-property getter code. Expected result I expected the old persisted Recurrence values to decode with: exceptionDates == [] Is this expected behavior or a SwiftData bug?

Hello guys I am experiencing a very concerning issue with App Store Connect regarding auto-renewable subscriptions for my Tyira Companion App. Current situation: The app is live One subscription was approved All remaining subscriptions have been stuck in “In Review” for several weeks. I have already opened multiple support cases: 102865116552 102893708354 Unfortunately, I have not received any meaningful response so far. I already verified: pricing configuration, screenshots, localization, tax/banking agreements, subscription metadata, review information. Everything appears correctly configured. At this point the issue seems to be an internally stuck review state. The problem is now causing ongoing revenue loss because users cannot purchase the subscriptions in production. How can I escalate this since I'm not getting any responses.

Hi Kevin, I'm starting this new thread to focus on alignment optimization and recalibrating our HBA constraints. Following up on your suggestion about UserReportHBAConstraints and alignment optimization, here are our current DEXT settings: Via UserReportHBAConstraints(): kIOMaximumSegmentCountRead/WriteKey: 129 kIOMaximumSegmentByteCountRead/WriteKey: 65,536 (64 KB) kIOMinimumSegmentAlignmentByteCountKey: 4 bytes kIOMaximumSegmentAddressableBitCountKey: 32 kIOMinimumHBADataAlignmentMaskKey: 0 Via SetProperties() (additional injection): kIOMaximumByteCountRead/WriteKey: 524,288 (512 KB) kIOMaximumBlockCountRead/WriteKey: 1,024 We inherited the segment count (129) and max I/O length (512 KB) from our legacy KEXT, which were originally calculated based on a 4 KB segment size (Max I/O 512 KB / 4 KB + 1 = 129). The current alignment value of 4 was essentially a placeholder, as the legacy hardware didn't enforce strict page-level alignment. Given that our testing is on Apple Silicon, we are considering increasing kIOMinimumSegmentAlignmentByteCountKey to 16,384 (16 KB) to match the native page size. However, I have two specific questions regarding this: Stripe Size vs. Page Size: Our RAID stripe size is typically larger than 16 KB (e.g., 64 KB or 128 KB). Should we be aligning the system to the RAID stripe size for hardware efficiency, or is it more critical to stick to the 16 KB page size to optimize the IOMMU/DART mapping overhead in DriverKit? Recalibration: If we increase the alignment to 16 KB, should we also adjust the kIOMaximumSegmentByteCount to match (i.e., 16 KB), or is it better to keep it at 64 KB to allow fewer, larger segments per I/O? We suspect that the 38% gain we saw in 4 KB Random Reads might improve even further if we fix this alignment bottleneck. Looking forward to your thoughts. Best regards, Charles

Hello, I am posting here after exhausting the official support channels available to developers, in the hope that someone from Apple can help review our case internally. I have also confirmed several other developers reporting the exact same situation on this forum within the past 7 days, and I would like to flag this as a broader pattern rather than an isolated incident. Summary of our situation: We submitted a critical app update that requires both a build review and an In-App Purchase review to go live. We filed an Expedited Review Request for the build, and the build review itself has been approved without issue — every expedited request we submitted for the build was accepted. However, the In-App Purchase items associated with this update remain in review and have not been processed, which means the update cannot actually be released to users despite the build being cleared. To our knowledge, there is no expedited review process available for In-App Purchases. This appears to be a structural gap: the build can be fast-tracked, but the IAPs that the build depends on cannot. What we have already tried: Submitted the Expedited Review Request for the build 2–3 times, each time including a detailed explanation in the request notes asking that the associated In-App Purchases also be reviewed alongside the build. The build was approved; the IAPs were not addressed. Sent inquiries through both available email contact channels for App Review / Developer Support. No substantive response so far. As an additional attempt, we added a test IAP item and used its review notes field to write a detailed explanation of the situation, politely requesting that the IAP review be picked up. Still no movement. Where this leaves us: The build is ready and approved, our team has done everything that the documented process allows, but the release is fully blocked on IAP review with no available escalation channel. Time-sensitive update content cannot reach our users, and we have no visibility into when, or whether, the IAP review will proceed. Within just the past 7 days, I have seen multiple posts on this forum describing the exact same pattern — build approved (often via expedited review), IAPs left pending, and no documented way to escalate the IAP side. Some of those threads were eventually resolved only after Apple staff intervened directly on the forum. What I am asking for: Could someone from Apple please check internally whether our pending IAP submissions can be routed for review, given that the corresponding build has already been approved through expedited review? More broadly, is there any official guidance on how developers should handle the case where a build is approved expeditedly but its associated IAPs are blocked with no expedited path of their own? I am happy to provide our Team ID, app identifier, and the specific submission references through a private channel. Thank you very much for your time, and apologies for the long post — I tried to lay out the full timeline so anyone looking into this has the complete picture.

I was having some trouble installing app to test on my Apple Watch (Series 9) so I removed it and thought to re-add it. However, after removing it, it no longer shows under my iPhone for me to add it as a possible run destination. I have tried numerous actions: Restart all devices Repair my watch Use hotspot so everything is on the same network Delete and reinstall Xcode None of these actions seem to be working. Does anyone have a way to get my watch to show up?

We added a running tab to the app this month. I need active testers that like to run to see if our route plotting, and enrollment plans adapt accurately based on users physically fit condition. Plan should adapt due to time constraints, injury, sickness and help adjust as you need. https://testflight.apple.com/join/zkV5Gznz

I've tried to add the "Pass Type Identifiers" entitlement manually in .entitlements, but it will not archive and shows the error: Entitlement com.apple.developer.pass-type-identifiers not found and could not be included in profile. This likely is not a valid entitlement and should be removed from your entitlements file. It works correctly for the App (parent of ), but without it the App Clip can't see any passes. The documentation says this should be possible: Note In iOS 17 and later, App Clips can use the Wallet capability. For more information on functionality that’s available to App Clips, see Choosing the right functionality for your App Clip. It is not visible in the portal either. Is this an entitlement that I need to specifically request, and if so, how would I go about doing so? Thanks! Wes

Hi everyone, Our app (version 1.0, first-time submission) has been in "Waiting for Review" status since May 8, 2026 — it has now been 20 days with no movement to "In Review". Some context: This is an educational app built to support our language education center's daily operations (attendance, assignments, learning progress, and internal management for students, teachers, and staff). The submitted build is complete and ready for review. Demo account credentials are provided in App Review Information and are active. Our backend services are stable and accessible for testing at any time. What I've already tried: Opened a support case and received responses confirming the submission is in queue and that reviewers have been notified. Submitted an expedited review request, which was accepted — but the status has not changed. Followed up multiple times, but the most recent replies have been identical template responses with no specific update. I understand review times can vary, but 20 days significantly exceeds the typical 24–48 hour window. I've also noticed several recent forum posts describing similar extended delays, so I'm wondering whether this is part of a broader issue or something specific to my submission. Has anyone experienced similar delays recently? Are there any additional steps I could take, or any insight from the App Review team would be greatly appreciated. Thank you.

As shown in the image, Apple's Wi-Fi Aware framework mentions support for Mac 26.0+

Hi, I’m trying to find an authoritative and up-to-date answer regarding the maximum file size supported by CKAsset uploads in CloudKit. I know Apple documentation has historically referenced a 50 MB limit in some places, but from what I can tell, that limit appears to specifically apply to CloudKit Web Services rather than native CloudKit framework usage through CKAsset. At the same time, I frequently see reports from developers claiming they are successfully uploading significantly larger assets through CloudKit, sometimes well beyond 50 MB. However, I haven’t been able to find clear documentation confirming whether this behavior is officially supported, recommended, or simply tolerated under certain conditions. My use case involves potentially syncing assets larger than 50 MB, and I need to determine whether: CloudKit officially supports larger CKAsset uploads today There is a documented hard limit for native CloudKit CKAsset uploads Uploading larger assets is considered reliable/safe for production apps I should instead design around chunked uploads and reconstruction logic I’m specifically interested in current practical and documented limits for CKAsset in 2026, especially for private database usage on Apple platforms. If anyone from Apple or developers with production experience can clarify this, I’d appreciate it. I also opened a DTS incident regarding this question and was advised to ask on the forums so the answer can benefit other developers. Thanks. (I also opened a DTS incident regarding this question and was advised to ask on the forums so the answer can benefit other developers.)

Hello, I am posting here as a last resort after multiple unsuccessful attempts to contact Apple Developer Support through other channels. Timeline of my situation: I enrolled in the Apple Developer Program through the Apple Developer app on iPhone, and the annual membership fee was successfully charged to my credit card. The subscription appears as active under my Apple ID subscriptions. I was then asked by Apple Developer Relations to provide identity verification documents. I submitted my government-issued ID as requested. I received an email from the Apple Developer Relations Team confirming receipt of the documents, stating: "Thank you for providing the documents we requested. We will review them and follow up with you within two business days." That two-business-day window has now been exceeded by more than a week. Total elapsed time since document submission: 10 days. I have since sent three follow-up emails to Apple Developer Support. None of them have received any response. The Apple Developer app shows the message: "Enrollment through the Apple Developer app is not available for this Apple Account", and redirects to the web. On the web, the enrollment page shows "Purchase your membership" and asks me to complete my purchase, as if I had never paid. I have not clicked that button to avoid being charged a second time. reportaproblem.apple.com does not allow me to take any action on this subscription. At this point my payment, my submitted documents, and my enrollment status appear to be disconnected from each other in Apple's systems. The payment is confirmed, the documents were submitted as requested, but the enrollment remains in a pending state with no communication. I have seen several similar cases in this forum during 2026, some of which were resolved when Apple staff intervened directly. I would greatly appreciate if someone from Apple could review my case internally, confirm that the payment is linked to my enrollment, and allow the document review to proceed. If that is not possible, I would need clear guidance on how to obtain a refund of the membership fee that was already charged. I am happy to provide my Apple ID, the date of the charge, or any other information needed via a private channel. Thank you in advance for any help.

Hello, Is anyone currently having issues with App Store review submissions or missing confirmation emails? My app was stuck in review for about 2 weeks, and I never received the usual “Thanks for submitting your app” email. I removed the submission and submitted again, but still no confirmation email. Has anyone experienced this recently?

To the App Store Review and Developer Support Teams, I am reaching out via this forum as a last resort because my communication through standard support channels has been entirely ignored, causing significant disruption to my business. The Timeline of the Issue: May 16: I submitted 5 In-App Purchases (IAPs) with version 2.0. While 2 were approved, 3 were rejected. I immediately resubmitted them for review on the same day. May 21: Version 2.0.1 was approved, but the 3 IAPs remained "Under Review." May 25: Version 2.0.2 was approved. I specifically included a Note to the Reviewer explaining that the IAPs were stuck, but this was completely disregarded. The Bottleneck: It has been 12 days since the resubmission. I have opened multiple support cases to resolve this, yet I have received no response or actionable feedback from the support team. This lack of communication and the extreme delay in IAP synchronization is creating a broken experience for my users and causing financial loss. Reference Information: App ID: 6744109858 Current App Version: 2.0.2 Related Case IDs: 102900240277, 102896872200, 102896192600 I request an immediate investigation into why these IAPs are stuck and why my support cases are being ignored. I am looking for a direct resolution from an Apple representative. Regards,

I have a SwiftUI view inside a NavigationStack with a custom navigation bar background color. I want the navigation bar buttons to have a consistent color throughout the app. The issue is that the navigation bar button color changes depending on the first/root view in the body. When the root view is a ScrollView var body: some View { ScrollView { // content } .toolbarBackground(Color(red: 0.02, green: 0.27, blue: 0.13), for: .navigationBar) .toolbarBackground(.visible, for: .navigationBar) .toolbarColorScheme(.dark, for: .navigationBar) } The navigation bar buttons appear white. However, if I replace the ScrollView with a VStack, while keeping the same modifiers, the navigation bar buttons appear black: var body: some View { VStack { // content } .toolbarBackground(Color(red: 0.02, green: 0.27, blue: 0.13), for: .navigationBar) .toolbarBackground(.visible, for: .navigationBar) .toolbarColorScheme(.dark, for: .navigationBar) } The navigation bar buttons appear black. How can I make the navigation bar buttons stay the same colour in both cases?

To the App Review and Developer Support Teams, I am writing this post to bring an ongoing and critical issue to your attention, as standard support channels have failed to provide any resolution or clear communication. Issue Summary: My application’s last two versions have been successfully reviewed and approved. However, three In-App Purchases remain stuck in the review process. Lack of Communication: I have opened several support cases regarding this delay, yet I have received no response or actionable feedback. The lack of synchronization between the App Review and Support teams is causing significant operational disruptions. The current communication gap and the slow response times are directly impacting my business and user experience. Impact: It is unacceptable to have a live application with "Pending" monetization features for such an extended period. This delay is causing financial loss and preventing my users from accessing the services they need. Request: I request an immediate update on the status of these IAPs and a clarification on why the support cases remain unanswered. I am looking for a direct escalation or a response from an Apple representative who can resolve this bottleneck. App ID: 6744109858 Related Case IDs: 102900240277 102896872200 102896192600 I look forward to a prompt resolution. Sincerely