Overview

iOS Background Location / Geofencing for Automatic Attendance — App Not Triggering Reliably We are developing an enterprise attendance application called Attendo, which uses location-based geofencing for automatic employee check-in/check-out. Business requirement The application needs to work as follows: An employee is assigned an office/work location with a defined radius. When the employee enters the configured radius, the application should automatically record a Check-In. When the employee leaves the radius, the application should automatically record a Check-Out. This should happen without the employee having to open the application. The functionality needs to work even when the application is in the background and, where supported by iOS, after the application has been terminated. For example: «Office geofence = 200 meters Employee enters the 200 m radius → automatic Check-In Employee leaves the 200 m radius → automatic Check-Out» Current iOS implementation We are using iOS location services with: Location permission: Always Precise Location: enabled Background Location capability enabled Background location updates enabled Geofencing / region monitoring The application is intended to respond to location/geofence events without requiring the user to open the app. However, we are seeing cases where the application does not reliably receive/process the required location/geofence event when the application has been in the background for an extended period. The same business workflow works more reliably while the application is active. Our concern Our understanding is that iOS does not allow an application to maintain a continuously running background service in the same way that Android can. However, our requirement does not necessarily require continuous GPS polling if there is an Apple-supported mechanism that can reliably wake/relaunch the application when a user crosses a geofence. We would therefore like to understand the recommended architecture for this use case. Questions Is Core Location Region Monitoring the recommended mechanism for an enterprise geofencing application that needs to detect entry/exit while the app is not running? Can iOS relaunch the application after it has been terminated by the user/system when a monitored region is entered or exited? Is there any supported way to guarantee that an application will continue receiving location/geofence events after it has been in the background for a long period? Does enabling: "UIBackgroundModes = location" "allowsBackgroundLocationUpdates" "CLLocationManager" Region Monitoring provide the expected behavior, or are there additional requirements/configurations we should consider? Are there known limitations regarding: Low Power Mode device movement speed GPS/location accuracy stationary devices iOS terminating/suspending the application force-quitting the application from the App Switcher large/small geofence radius multiple monitored regions Is it possible to use significant-change location updates + region monitoring together for this type of attendance workflow? For an enterprise application where the user explicitly grants Always Allow Location permission and Precise Location is enabled, what level of reliability can realistically be expected from iOS geofencing? Important business constraint We cannot require employees to manually open the application every time they arrive at or leave the workplace. The objective is an automatic attendance system, where the employee's entry and exit from the workplace geofence is detected by iOS and the application records the corresponding attendance event. We understand that iOS is designed to protect battery life and user privacy and that continuous background execution may not be permitted. We are therefore looking for the Apple-recommended architecture for achieving this requirement using supported iOS APIs, rather than trying to circumvent iOS background execution policies. Any guidance from Apple engineers or developers who have implemented reliable enterprise geofencing would be greatly appreciated.

Hey, does anyone know how long the enrolment process needs? enrollment ID is QARGL6A9YV - maybe someone can help, we wanna start as soon as possible :-)

Hi everyone, Is anyone else having problems with Xcode 27? It keeps crashing on me. And when I say ‘constantly’, I mean it shuts down about every minute. You can’t work like this... Am I the only one with this problem?

Hi! We've recently done a big migration to Swift 6 language mode in our app and are now getting reports of crashes occurring due to closures in our SwiftUI code (most often the view builder in ForEach) not running on the main queue but instead running on the queue com.apple.SwiftUI.AsyncRenderer. One example of a call stack (ScheduleListView is our view that is in Swift 6 mode): Thread 16 #0 (null) in _dispatch_assert_queue_fail () #1 (null) in dispatch_assert_queue$V2.cold.1 () #2 (null) in dispatch_assert_queue () #3 (null) in swift_task_isCurrentExecutorWithFlagsImpl(swift::SerialExecutorRef, swift::swift_task_is_current_executor_flag) () #4 (null) in closure #2 in closure #1 in closure #1 in ScheduleListView.body.getter () #5 (null) in closure #1 in ForEachState.item(at:offset:) () #6 (null) in partial apply for closure #1 in ForEachState.item(at:offset:) () #8 (null) in partial apply for closure #1 in _withObservation<A>(do:) () .... (We have many other crashes with similar crash reports but in other views) Has anybody else run into something similar? Is there anything (other than simply reverting to Swift 5 mode again) that we can do to fix or at least reduce the amount of crashes? We're having a hard time finding anything out of the ordinary that we're doing in our views. Regards

I am posting this because I genuinely do not know what else to do. My company is based in Nigeria, and we submitted our app, MyCove, for App Store review. The app was rejected under Guideline 5.6. We responded to the rejection and explained the application, its purpose, its users, and how the functionality works. We also provided the information and access required for Apple to review the app. We have since: Communicated with the App Review team through App Store Connect Raised support cases regarding the rejection Requested clarification about the specific reason for the rejection Escalated the matter Submitted an appeal to the App Review Board Followed up repeatedly And yet, almost one month later, we still have not received a substantive answer to our questions or a meaningful update on the appeal. This is not simply a delay in getting an app reviewed. This is a business that has been unable to move forward for almost a month because we cannot even get a clear answer about what Apple believes is wrong with the application or what we need to do to resolve it. Apple's own documentation states that 90% of submissions are reviewed in less than 24 hours, and Apple's App Review FAQ states that Resolution Center messages are generally answered within 24 hours. Apple also states that developers can appeal when they believe an app was misunderstood or that they were treated unfairly during review. So my question is: If this were a company based in the United States, would the same situation be considered acceptable, almost one month without a substantive response to an App Review dispute or appeal? I am not asking for preferential treatment because we are a Nigerian company. I am asking whether Nigerian developers and companies receive the same level of responsiveness and due process during App Review as developers and companies in the United States and other major markets. If the answer is yes, then I would genuinely like to understand what is happening with our case, because almost a month without a substantive response does not appear consistent with Apple's published App Review communication timelines. I am not looking for someone to approve the app without review. I want Apple to tell us clearly what the problem is, what evidence led to the rejection, and what we need to do to resolve it. Case references: 102953967427 Has anyone else experienced an App Review appeal or rejection being left without a substantive response for this long? And, if so, how was it eventually resolved?

Hello, I’m experiencing a sudden TestFlight issue affecting multiple unrelated apps under the same Apple Developer account/team. Several TestFlight builds across my apps suddenly changed to Expired at the same time, even though many of them were uploaded only a few days ago and were nowhere near the normal 90-day expiration period. I also uploaded a brand-new build to check whether the problem was related only to existing builds. The new build: Processed successfully Appears normally in App Store Connect Appears in the TestFlight app Shows 90 days remaining Shows the Update button However, when I try to install or update it, TestFlight immediately displays: “The requested app is not available or doesn’t exist.” So build upload and processing appear to work correctly, but TestFlight distribution/install does not. Since multiple completely separate apps under the same developer team became affected at approximately the same time, this appears to be an account/team-level TestFlight issue rather than an issue with a specific Bundle ID, provisioning profile, certificate, project, or individual build. I have also seen recent reports mentioning: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING and TestFlight Beta Contract issues. Has anyone confirmed whether this is currently an Apple-side TestFlight backend / Beta Contract issue? If Apple staff see this post, could you please check whether TestFlight beta distribution provisioning or the Beta Contract for affected developer teams needs to be re-provisioned? I can provide screenshots showing: Existing builds suddenly marked as Expired A newly uploaded build showing 90 days remaining The installation error Thank you

Dear Apple Developer Support, I am developing HushRise, an iPhone alarm application intended to help people in Ukraine manage sleep disrupted by wartime air-raid alerts. Nighttime alerts can force people to interrupt their sleep and seek shelter, sometimes repeatedly. Families must then plan work, school, and other responsibilities around these disruptions. Educational institutions and other services may suspend in-person activities during alerts, making a fixed wake-up time less useful than a wake-up signal that takes the current alert status into account. The purpose of HushRise is to support rest and daily routines under these conditions. It is not an official emergency-warning service and must not replace civil-defence alerts or encourage people to ignore them. The intended behavior is: A user sets a wake-up time and selects their region. At that time, the alarm starts only after a fresh server response confirms that no air-raid alert is active. If an alert is active, the application waits for the reported all-clear. Multiple alarms postponed during the same alert should produce one wake-up signal after the all-clear. A snoozed alarm must also obtain fresh confirmation before starting again. An alarm that has already started may continue until the user stops or snoozes it. We have tested a native AlarmKit integration on a physical iPhone. The system alarm, Lock Screen controls, Apple Watch presentation, and Stop action work. However, without ongoing background audio, iOS suspends our application’s status checks. In one test, an alarm due at 20:09 was not scheduled until the application returned to the foreground at 20:11. Audible background playback helped in experiments, but requiring continuous sound is not appropriate for the intended quiet sleep experience. Could your technical team please advise: What supported architecture should we use for an AlarmKit alarm whose trigger depends on a server event occurring at an unknown time? Can a server notification initiate the necessary validation and alarm scheduling while the iPhone is locked, and what execution guarantees or limitations apply? Is there an entitlement or approval process appropriate to this use case? Would Critical Alerts be applicable, or would another mechanism be more suitable? Which capabilities require Apple Developer Program membership? Our current prototype is installed through a free Personal Team. We understand that an offline device cannot receive new server information and that notification delivery may be delayed. We want to communicate these limitations honestly and build within Apple’s supported APIs. We can provide a minimal reproducible project, sanitized device logs, and a description of our physical-device tests. Thank you for helping us identify a reliable and appropriate approach for people whose sleep and daily lives are affected by the war in Ukraine. Kind regards, HushRise developer

case 20000135074872. Support asked me to renew the Paid Applications agreement, which I did, and then sent the migration checklist. On August 20 I replied confirming every item was complete and that I was ready to begin. I followed up again on September 9, and opened a second case on September 15 (20000153338342), but I haven't received a response since. I have a finished app ready to launch, and this migration is the only thing holding it up. Could someone from Developer Support confirm whether the migration has started, let me know if anything else is needed from me, and link the two cases? Thank you.

MacBook Air (M4) Current build: macOS 27 Developer Beta (26A5368g) I have a system-wide Location Services failure affecting Apple Maps, Safari geolocation APIs, and any application requesting the current location. Symptoms: Apple Maps cannot determine current location. Safari and browser geolocation APIs fail. Websites report that location cannot be found. Location Services are enabled and permissions are granted. The issue has persisted across: macOS 26.5 beta macOS 26.6 beta macOS 26.6 beta 2 macOS 27 Developer Beta Troubleshooting already performed: Multiple Wi-Fi networks tested. iPhone hotspot tested. VPN enabled and disabled. Location Services reset. Permissions reset and reauthorized. New clean local user account created (no Apple ID, no third-party software). Issue reproduces identically in the clean account. Technical observations: locationd logs repeatedly show: knownCount = 0 AlsWifi = unknown while Wi-Fi scanning itself appears successful: queryMacAddresses.size = 57 The system sees dozens of nearby access points, but none appear to be recognized for Wi-Fi positioning. Additional findings: Wi-Fi hardware functions normally. Internet connectivity is normal. Bluetooth and Find My device presence work. GeoServices resources are present on disk. No successful location fix is ever produced. Has anyone seen similar CoreLocation / GeoServices behavior where Wi-Fi scans succeed but knownCount always remains 0 and no location fix is generated?

Hello App Review Team, Our app MagicMatch has been in "Waiting for Review" status for 7+ days now (submitted Friday, September 18). We previously addressed a Guideline 4.3(a) rejection and resubmitted with substantial changes to the app's structure and design. Could you please confirm: • Is there a specific reason for this extended hold? • Is any action required from our side? • When can we expect the review to proceed? We have not withdrawn or resubmitted the build during this wait, to avoid resetting the queue. Any update would be greatly appreciated. Thank you.

Title: Unable to enroll in the Apple Developer Program through the app or website Hi, I’m trying to enroll in the Apple Developer Program with my Apple Account, but I’m blocked on both the app and the website. I signed in to the Apple Developer app and completed the account profile questions. In the Account tab, “Enroll Now” is greyed out. Below it, I see: “Enrollment through the Apple Developer app is not available for this Apple Account. Visit https://developer.apple.com/programs/enroll/.” When I open the enrollment page in Safari and try to continue, I get: “We are unable to process your request. An unknown error occurred.” My Apple Account is set to Canada. Could that be related, or is there something else I need to check on my account? Has anyone encountered these two errors together and found a way to resolve them?

I’ve tried every online recommendation but nothing works, someone helps me out , my WiFi is pretty good, 100GB storage space and I have left the phone plugged in for 5 consecutive days

Hello Apple Developer Community, Our app Divya Maarg, version 1.0.8, has remained in “Waiting for Review” since September 22, 2026. The previous submission received feedback under Guideline 4.3(b). We addressed the feedback, updated the application, provided clarification to App Review, and submitted a new build. We have also contacted Developer Support and submitted an expedited review request. However, the current submission has not yet moved from “Waiting for Review” to “In Review.” We understand review times can vary. We would simply like to know whether an extended Waiting for Review period can occur following a previous 4.3(b) review, and whether we should continue waiting or take any further action. We do not want to withdraw and resubmit unnecessarily if the submission is already correctly queued. Has anyone experienced a similar delay after addressing 4.3(b) feedback? Thank you.

I am using Coding Intelligence, powered by Claude, in the first production release of Xcode 27.0 (in MacOS 26.7). Initially it was working ok. But after less than a day, it now crashes every time it needs to ask for permission for any shell command. And each time I restart things, it burns through a ton of tokens. ☹️ Any suggestions? (I'll file a bug report right now…)

I’m trying to distribute a macOS application outside the Mac App Store using Developer ID signing and notarization. The Sensitive Content Analysis capability is enabled for this App ID in Certificates, Identifiers & Profiles. My application requires the following entitlement: com.apple.developer.sensitivecontentanalysis.client However, when I create and download a new Developer ID provisioning profile for this App ID, the generated profile does not contain this entitlement. I have regenerated and downloaded the profile after confirming that Sensitive Content Analysis is enabled. I also decoded the newly generated .provisionprofile to inspect its entitlements. It contains the application identifier, team identifier, and keychain access groups, but does not contain com.apple.developer.sensitivecontentanalysis.client. As a result, Xcode will not export the Developer ID build because the application requests the Sensitive Content Analysis entitlement but the provisioning profile does not authorize it. Does anyone know the answers to these questions: Is com.apple.developer.sensitivecontentanalysis.client supported for macOS applications distributed outside the Mac App Store using Developer ID? If it is supported, why is the entitlement not being included in newly generated Developer ID provisioning profiles for this App ID? Is there an additional approval, agreement, or configuration required for this entitlement to be included in a Developer ID profile? Sensitive Content Analysis is a required feature of this application, so removing the entitlement is not an option for our distribution build.

We are designing a bounded local macOS operation with a supervisor, controller and helper. All three must be unable to cause prohibited network effects, including attributable delegated requests, before admission and until quiescence. Unrelated applications must retain their normal network access. We are seeking an API contract clarification, not reporting a reproduced OS bug. No NetworkExtension provider has been activated for this design. Our reviewed SDK is MacOSX27.0.sdk; its presence is not a runtime qualification. Please identify the supported macOS versions for your answer. The design must tolerate provider crash, termination, disconnection and unresponsiveness, and operation lease expiry/revocation. Administrative filter disablement or privileged reconfiguration is a separate unresolved threat-model case, not something we assume ordinary failure handling covers. We reviewed content-filter deployment in TN3134 and the nullable/delegated audit tokens in NEFilterFlow. We understand that NEURLFilterManager.shouldFailClosed concerns URL-filter decisions, not an established guarantee for arbitrary content-filter traffic. EndpointSecurity AUTH deadlines are also a separate mechanism. The VPN routing article documents dropping during specific transitions, but has system exceptions; TN3120 excludes using a packet tunnel as a dropping content filter. We therefore have not adopted that workaround. For macOS NEFilterDataProvider / NEFilterPacketProvider, is there a supported configuration that keeps prohibited operation traffic denied when the provider crashes, is killed, disconnects, hangs or cannot deliver a decision? Please distinguish new flows, existing/previously permitted flows, queued data, restart intervals, and configuration disable/removal. What supported admission and teardown guarantees allow releasing the first protected process only after enforcement is effective, then retaining denial through lease revocation and shutdown? An enabled configuration alone would not demonstrate that barrier. How should this guarantee cover operation-caused DNS and delegated system-service traffic, including absent/ambiguous audit tokens, without denying unrelated host traffic? If content filters cannot meet that scope, can App Sandbox without network entitlements provide the independent denial boundary for these roles, and what documented exclusions or additional constraints apply? A reference to the supported contract, or a precise statement of the requirement that needs to change, would let us select an architecture before implementing and activating a native provider. We are not requesting private APIs or an unsupported packet-tunnel filter.

2 days since I paid for my Apple Developer membership and still nothing 💀 Meanwhile, Google approved everything almost immediately Apple, you’re making it really hard not to say Google is better!

Hi, I’m seeing a CloudKit Production sync failure in an iOS app using SwiftData/Core Data with private CloudKit mirroring. Sync worked correctly after release, then stopped working without any new app build being released. Device logs show: CKInternalErrorDomain Code=1011 and Core Data reports that CloudKit mirroring was never successfully initialized. CloudKit Production logs also show a native PRIVATE database request failing with: USER_ERROR / BAD_REQUEST involving the internal record type: _pcs_data The Production schema, private zone, and subscription are still present. I have not reset Production or deleted any zones/subscriptions. I have already filed a Feedback Assistant report with diagnostics. Has anyone seen this pattern before? Is there a safe developer-side remediation, or is this typically an Apple-side CloudKit/PCS issue? I want to avoid any destructive action that could risk existing user data.

Apple's InputTargetComponent documentation shows this code for an entity that should receive input without participating in physics: // Create a collision component with an empty group and mask. var collision = CollisionComponent(shapes: [.generateSphere(radius: 0.1)]) collision.filter = CollisionFilter(group: [], mask: []) myEntity.components.set(collision) In my RealityKit scene, myEntity also has an enabled InputTargetComponent and a GestureComponent with a TapGesture callback. I use .trigger collision mode. With the empty group and mask, the callback runs on visionOS but does not run on macOS or iOS. Changing the filter to CollisionFilter.default makes the callback run on macOS and iOS. The entity and gesture setup are otherwise the same. Should the documented empty filter still allow input hit testing on macOS and iOS? Is this a RealityKit bug, or does input targeting on those platforms require a different collision filter or additional setup?

I have two apps; one is a subset of functionality of the other. The smaller app has about 170 Swift files. The larger app has these files plus about 120 more. So I would expect the larger app to take around twice as long to build. Instead, the smaller app takes less than a minute to build while the larger app takes over 13 minutes to build; to be exact, it takes 15.3 times longer. While reviewing the build report, I noticed that the smaller app compiles the Swift files in batches, with each batch taking around 10 seconds, but with up to 17 batches running at once. In contrast, the larger app compiles all 290 Swift files in one giant batch, so apparently there is no multithreading of the Swift compilation (see screen shots below). The difference in the number of batches the smaller app compiles at once roughly corresponds to the difference in overall build time. Is there a build setting I can change to make the larger app compile Swift files in multiple smaller batches as the smaller app is doing? I checked SWIFT_COMPILATION_MODE and it's the same in both apps (Incremental for debugging and Whole Module for release) but I don't know what other settings I should check.