Overview

Post

Replies

Boosts

Views

Activity

Apple Developer Program paid but individual enrollment still Pending after 16 days
Hello Apple Developer Community, I am experiencing an issue with my individual Apple Developer Program enrollment and would appreciate any guidance from Apple staff or developers who have faced a similar situation. On November 2, 2026, I purchased the annual Apple Developer Program membership through the Apple Developer app on my iPhone for USD 98.99. The payment was successful, and my Apple Account shows the subscription with a renewal date of November 2, 2027. However, after 16 days, my individual enrollment still shows "Pending." What I have verified: My Apple Account recognizes the annual subscription and its renewal date. The Apple Developer app continues to display "Pending." On the Apple Developer website, my individual team appears as "Pending" and cannot be selected for membership operations. I cannot access certificates or provisioning resources under my individual membership. My Apple Account is also associated with a separate organization's developer team, where my role is Developer, not Account Holder. I have an open Apple Developer Support case and have submitted a follow-up request, but I have not received a resolution or an explanation. The available Developer Support contact options only offer email, with no telephone option. I am concerned that the subscription payment and developer enrollment may not have been correctly synchronized in Apple's systems. My questions are: Has anyone experienced a successful Apple Developer membership payment while the individual enrollment remained stuck in "Pending"? Could being a Developer on another organization's team affect activation of an individual membership? Is there a known way to resolve an enrollment synchronization issue or request a manual review? I need my own individual membership to publish my educational application independently from the organization I also work with. Any guidance would be greatly appreciated. Thank you.
0
1
128
6m
Apple In-App Purchase availability.
Hello, I am a developer based in Somalia and I have recently enrolled in the Apple Developer Program. I am planning to build an iOS app exclusively for users in Somalia. The app will offer premium digital features, and I would like to use WaafiPay, a local Somali payment provider that supports mobile-money payments such as EVC Plus, ZAAD and SAHAL. Somalia does not have an Apple App Store storefront or Apple In-App Purchase availability. Before I start development, I would like to confirm whether an app distributed to users in Somalia can use WaafiPay to process payments for premium digital features directly inside the app. If this is permitted, please let me know whether I need any special entitlement, approval, or implementation requirements. Thank you.
0
0
343
32m
iOS and Android
I currently have a iOS app live on the App Store but I also want to release it on Android, the whole code is in Swift so would that be possible or would I have to rewrite my whole apps code in a different coding language.
4
0
4k
36m
When IAPs would be available for Apple Watch?
I need someone from Apple to answer my question. I've added French localization to every of my IAP but I can't submit them due to this warning that sayws "In-app purchases and subscriptions are currently not supported on Apple Watch." The app is watchOS-only. Could you tell me please, when Could you tell me please, when IAPs would be supported?
2
0
207
1h
Can I identify the card network, such as Cartes Bancaires, from decrypted Apple Pay paymentData?
We are a merchant based in Europe and work with multiple PSPs, some of which do not support the Cartes Bancaires network. After decrypting the Apple Pay paymentData, is it possible to identify the card network or card brand, such as Cartes Bancaires, before submitting the transaction for authorization? If so, which field contains this information, and is Cartes Bancaires returned as a distinct value? For co-badged cards, does the decrypted payload indicate all available networks or only the network selected for the transaction? We would like to use this information to route transactions to a PSP that supports the relevant network, helping us improve authorization rates and reduce processing costs. Thank you.
0
0
123
4h
Disappointed with Apple Developer Support.
My company’s Apple Developer Program enrollment was declined without providing any specific reason or explanation. As a legally incorporated company, I submitted the required business documentation and identification. However, my enrollment was rejected without clarification about what went wrong. I respect Apple's verification and security procedures, but I believe developers and businesses deserve transparency, especially when they have followed the required process. A simple explanation of the reason for rejection would make a big difference. I'm hoping someone from Apple Developer Relations can help review this situation and provide clarification. #Apple #AppleDeveloper #DeveloperSupport #Entrepreneurship #Startups
0
0
135
4h
Version 1.0.0 stuck in "Waiting for Review" for ~2 weeks after an automated Guideline 2.5.1 message about the Family Controls entitlement
Our app — a screen-time / focus app — has had no App Review activity for two weeks, and we believe the trigger was an automated Guideline 2.5.1 check that froze an otherwise actively progressing review. (This forum account is linked to the developer account in question; we can provide the App ID, bundle IDs, submission IDs, and support case numbers through any private channel on request.) Context: Jul 2–5: Our first submission (Version 1.0.0) was under active review. We went through several ordinary metadata / paywall-related iterations, and the reviewer responded within roughly 24 hours each time. Nothing related to Screen Time was raised in these human reviews of builds 9 and 10. Jul 8: After we submitted build 11 — which addressed the remaining human-review feedback — we received an automated Guideline 2.5.1 (Performance: Software Requirements) message stating that the app uses the Screen Time API but has not been submitted with the Family Controls entitlement, and that review of the submission cannot proceed. All reviewer activity stopped at that point, and there has been none since. What we verified: The Family Controls (Distribution) entitlement is granted to our account and assigned to all four bundle IDs (the main app plus its DeviceActivityMonitor, ShieldAction, and ShieldConfiguration extensions). We verified with codesign that com.apple.developer.family-controls = true is present in the code signature and embedded provisioning profile of every one of the four executables in the submitted IPA — so the entitlement named in the automated message is present in the flagged build. For context: builds 9 and 10, with an identical Screen Time API surface and identical entitlements (verified at the binary level with nm against the submitted artifacts), had been human-reviewed on Jul 2–5 with no Screen Time-related objection. We recognize those builds may simply not have reached the automated analysis stage before being superseded, so we do not draw firm conclusions from that. What we did anyway (build 12, submitted Jul 9): In case the automated check actually concerns the separate com.apple.developer.family-controls.app-and-website-usage entitlement (which we do not request and do not need), we removed every reference from our main app to the APIs associated with it: AuthorizationStatus.approvedWithDataAccess, ManagedSettings.Application.bundleIdentifier, ManagedSettings.Application.localizedDisplayName, ManagedSettings.ActivityCategory.localizedDisplayName, and ManagedSettings.WebDomain.domain. We verified with nm that none of the four executables in the build 12 IPA reference these APIs. The app does not use FamilyActivityData, DeviceActivityReport, app usage events, web usage events, or App and Website Usage data access. No automated message has appeared for build 12. What has happened since: Jul 9–14: No reviewer activity on build 12. We filed an expedited review request and opened two Developer Support cases (Jul 8 and Jul 14). No response to any of them. Around Jul 15: Hoping to clear the frozen state, we cancelled and resubmitted the same Version 1.0.0 / build 12. Around Jul 17: Filed a second expedited review request for the new submission. Jul 22 (today): The new submission has been in "Waiting for Review" since Jul 15, with no reviewer activity and no reply to either support case or either expedite request. What we are asking: Could someone check whether the Jul 8 automated flag is still attached to the app record and blocking reviewer assignment, and help get the current submission assigned to a reviewer? If the automated check flags build 12 again, could the message specify which entitlement and which binary / API references triggered it, so we can address it precisely? We can provide codesign output, entitlement plists, provisioning profile dumps, and nm symbol listings on request. Thank you.
4
2
1.3k
4h
Automated 2.5.1 "not submitted with the Family Controls entitlement" although entitlement is assigned and in the build
My first submission was stopped by an automated App Review message, and I can't find anything on my side to fix. It looks the same as the reports in thread 838802. The message (Guideline 2.5.1): "An automated analysis indicates the app uses one or more Screen Time APIs but the app has not been submitted with the Family Controls entitlement." App Name: blorbs, Apple ID 6836228369 Bundle ID: app.blorb.ios, Team ID: WVVPTV9U33 Version 1.0.0 (1), submitted Nov 18, 2026, 1:29 AM PT Automated message received Nov 18, 10:34 AM PT Submission ID: 4d3288f6-3a5b-48cb-8f1e-20fc01a55c14 Built with Xcode 26.6 (iOS 26.5 SDK), minimum iOS 17, automatic signing What the app is A personal focus app. The user picks apps to lock on their own device (individual authorization) and unlocks them by tapping an NFC accessory. Targets: the main app, a DeviceActivityMonitor extension, a ShieldConfiguration extension, and a widget / Live Activity extension. What I verified Approval: Apple Developer Relations emailed on Nov 11, 2026 that Family Controls (Distribution) "has been assigned to your account". Portal: Capability Requests shows Family Controls (Distribution) as Assigned on app.blorb.ios, app.blorb.ios.monitor and app.blorb.ios.shield. Provisioning Support lists Development, Ad hoc, App Store Connect. The uploaded build: App Store Connect > TestFlight > Build Metadata > Entitlements shows com.apple.developer.family-controls: true on the main app, the monitor extension and the shield extension. Binary State: Validated. The widget extension has no Screen Time code and links none of FamilyControls, ManagedSettings, ManagedSettingsUI or DeviceActivity, so it correctly has no entitlement. What the app does not use No App and Website Usage entitlement, no approvedWithDataAccess, no FamilyActivityData No DeviceActivityReport extension, no ShieldAction extension The only related calls are Application.localizedDisplayName and WebDomain.domain, read inside the ShieldConfigurationDataSource to show the name of the shielded app or site, as the documentation describes. What I've done Replied in App Store Connect with the details above Submitted an appeal to the App Review Board Questions Could someone from App Review or DTS check whether this automated flag is correct for this submission, and whether it's blocking reviewer assignment? Can the message say which binary or API triggered it? Apple's own record of the build lists the entitlement on every Screen Time binary. Has anyone had this cleared, and what did it take? Happy to share build IDs, entitlement dumps or anything else privately.
0
0
143
4h
"Your Apple Account isn't enabled for App Store Connect"
I'm the Account Holder for my company. The organization's membership became active on November 16, 2026 (welcome email at 5:25 PM Central), and every agreement is accepted on developer.apple.com/account. Certificates, Identifiers & Profiles works for the team. Signing in to App Store Connect with the same Account Holder Apple Account gives "Your Apple Account isn't enabled for App Store Connect", at https://appstoreconnect.apple.com/m/INVALIDITCUSER?errorKey=ITC.signin.error.invalidUser.asc. I've tried a private window, another browser, and signing out and back in. Any idea how to fix?
3
1
229
5h
iPhone Duo Unfolded Safe Areas
Hi, my app is currently built on Xcode 27.1 I am working on upgrading to Xcode 27.2 We have a regression issue whereby, the top safeArea is 82 despite the vertical bar being opted in and active. This only happens on unfolded landscape. Our right safeArea is 0 for the window and is 84 for the view safeArea. Both window and view safeAreas have the top safe area of 82 though. We would like to know what could be the cause behind the top safeArea being activated. Note: this is not an issue for iOS 27.1
2
0
180
5h
SwiftUI Architecture Guide
Application Types Applications are divided into Document-based and Library-based. A document-based application stores user data in individual, standalone files. Users manually name and organize those files in a local system or synced cloud storage such as iCloud. The software typically opens multiple windows for different projects. This framing is for standalone, complex files that need to be shared, exported, or handled independently. A library-based application manages data in one unified, central repository, locally or through remote cloud databases. Spotify, Netflix, and Notion are the examples shown. The file system is hidden; updates are saved automatically in real time; and a single window supports browsing, search, and access to the synchronized data collection from any device. Model Types Four model types: Data, Domain, Application, and Presentation. Apple Platforms In Apple MVC (AppKit / UIKit), the model branches to Data, Domain, and Presentation. In SwiftUI, Model branches to Data and Domain. Project Structure SwiftUI App Folders Swift Package Folders App Modularization Not every module in a large application needs to be extracted into a separate framework or Swift Package. Logical modularization can also be achieved through a well-organized folder structure within the main project. Introduce separate packages or frameworks only when there is a clear benefit, such as independent reuse, distribution, build isolation or ownership. Avoid unnecessary project and dependency management overhead. State Management & Data Flow Source of truth is “a key concept in SwiftUI”: a single place to store a piece of data, with everywhere else reading the same piece of data. Environment is SwiftUI’s native dependency-injection mechanism. It allows shared dependencies, domain models, and services to be injected at the appropriate view-hierarchy level and accessed where needed without explicit parameter passing or unnecessary coupling. It is described as a tool for managing dependencies and sharing state across the view hierarchy. Domain Model Ownership Domain Models should be owned by the highest relevant SwiftUI view in the hierarchy that defines their context and lifecycle. NavigationStack owns the Domain Models for its navigation context and makes them available to descendant views through @Environment. When a NavigationStack is embedded in a TabView or NavigationSplitView, ownership moves up to the TabView or NavigationSplitView so the models can be shared across tabs or split views. The stated result is clear ownership scope, sharing where needed, and isolation between independent navigation contexts. Previews & UI Testing Environment injection makes SwiftUI Previews and UI Tests easier to configure by allowing real Domain Models to be replaced with mock or dummy instances. Views can be tested independently with controlled data and predictable states, without requiring real services, network requests, or application setup. Domain and Data Model Examples For a library-based app with remote data. Additional Domain Model Examples E-commerce Catalog, ShoppingCart, OrderHistory, Wishlist Banking MyAccounts, MyCards, MyTransactions, MyInvestments Social Network Feed, Conversations, Notifications, Friends Healthcare MyAppointments, MedicalHistory, Prescriptions, MyHealth Education Courses, MyCourses, Assignments, MyGrades, LearningProgress Real Estate PropertyCatalog, MyProperties, Favorites, Appointments Hotel Booking Destinations, Search, MyBookings, TravelHistory Food Delivery RestaurantCatalog, ShoppingCart, MyOrders, DeliveryTracking Project Management Projects, MyTasks, TeamMembers, Notifications Insurance MyPolicies, MyClaims, Coverage, Documents Smart Home MyHomes, Devices, Automations, EnergyUsage Fitness MyPlans, MyProgress, MyGoals, WorkoutHistory Other Search, Dashboard, Favorites, Notifications, Settings, ActivityHistory, Recommendations, Subscription, DocumentLibrary ViewModel? - MVVM In SwiftUI, the View encapsulates the UI content (body), its state (properties), and its actions or tasks (functions). This is possible because SwiftUI is designed around a declarative, state-driven UI model. In Android and .NET platforms, a separate ViewModel is typically required to hold and manage the View's state. Projects that intoduce ViewModels in SwiftUI add unnecessary architectural complexity, boilerplate, and code duplication; synchronization issues; unclear state ownership; additional lifecycle management; more abstractions; harder debugging; and increased maintenance, without meaningful benefits over SwiftUI's native state management. In UIKit, introducing a separate ViewModel layer is often unnecessary, as UIViewController already serves as the presentation model, handling presentation logic and coordinating the view. Non-UI responsibilities can be delegated to dedicated ModelControllers or Managers, avoiding unnecessary layers and abstractions. Domain Models vs. ViewModels Domain Models are view-independent, while ViewModels are view-dependent. A ViewModel is tightly coupled to the structure, state, and lifecycle of a specific View. Whenever the View code changes, its ViewModel often requires corresponding coding changes, and vice versa, creating additional maintenance and synchronization overhead. Domain Models, on the other hand, represent application context and business functionality independently of the UI. This separation preserves UI independence and allows the same Domain Models to be shared across different screens and platforms, such as iPhone, iPhone Duo, iPad, and macOS, without duplicating or adapting business logic for each View. This makes Domain Models a more scalable and maintainable approach for modern SwiftUI applications, particularly those targeting multiple screen sizes and platforms.
1
0
205
5h
Accessibility Inspector Element Detection and contrast failures with SwiftUI sheets
I am investigating Accessibility Inspector/XCTest audit results in a SwiftUI app (Target Keeper), without suppressing warnings. Environment: Xcode 27.1 (27A9275), iPadOS 27.0 Simulator, macOS 27.0.1. Debug and Release builds pass. The app uses scalable text and labeled controls. Element Detection / native sheet Main-screen Element Detection passes when the sheet is closed. With a SwiftUI .sheet presented, the iPad audit reports “Potentially inaccessible text”; XCUIAccessibilityAuditIssue.element is nil. Exported Inspector HTML highlights background labels behind/outside the sheet, rather than a foreground control. The separate, data-free SwiftUI application below reproduces the modal-only warning; it links no application modules or persistence. Actual iPad Simulator VoiceOver testing using XCUIDevice.shared.voiceOverService passes forward/backward traversal of the real application's modal controls, without reaching the background labels. This is simulator evidence, not physical-device acceptance. A trial explicit modal container/.isModal trait did not clear the audit and was reverted; no warnings are filtered. Minimal independent app: import SwiftUI @main struct ModalRepro: App { @State private var showing=false private let names=["Vegetables","Protein","Fruit","Dairy","Grains","Healthy Fats"] var body:some Scene {WindowGroup { NavigationStack { VStack(spacing:24) { Button("Nutrition") {}.accessibilityLabel("Choose Page").accessibilityValue("Nutrition") LazyVGrid(columns:[GridItem(.flexible()),GridItem(.flexible()),GridItem(.flexible())],spacing:40) { ForEach(names,id:\.self) { name in Button {} label: { VStack(spacing:10) { Circle().fill(.blue.opacity(0.3)).frame(width:250,height:250) Text(name).font(.system(size:17)).accessibilityHidden(true) } }.buttonStyle(.plain).accessibilityLabel(name) } } Button("Show modal") {showing=true} }.padding(24).frame(maxWidth:.infinity,maxHeight:.infinity).background(Color.black) }.preferredColorScheme(.dark) .sheet(isPresented:$showing) { NavigationStack { VStack {Text("Foreground content");Button("Close") {showing=false}} .frame(maxWidth:.infinity,maxHeight:.infinity).background(Color.black) .navigationTitle("Modal flow") }.preferredColorScheme(.dark) } }} }In an Xcode UI-test target, launch this app, run try app.performAccessibilityAudit(for: [.elementDetection]), tap “Show modal”, then run the same audit again. The first passes and the second fails. No issue handler ignores failures. Contrast / scrolling — separate unresolved finding All four iPhone combined-audit configurations (portrait/landscape, normal/maximum Dynamic Type) pass in the tested picker state. However, iPad maximum-text combined audits and a separate scrolled iPhone maximum-text landscape contrast audit still fail; we are not calling these resolved. In the scrolled iPhone case, XCTest identifies a count label whose frame is entirely above the visible results viewport. Inspector's exported HTML reports 1.37:1 using #252526 versus #000000; its marked screenshot rectangle overlaps the dark search/header area, not visible count text. Visible sampled labels instead have white or light foregrounds on opaque dark fills (e.g. #FFFFFF/#1C1C1E = 17.01:1; #98989F/#1C1C1E = 5.94:1). These are screenshot core-pixel measurements, not proof every warning is false. We compare ordinary text against 4.5:1 and interactive non-text against 3:1. iPad maximum-text warnings have not yet been matched to an exact visible color pair. Original failures and HTML exports are preserved privately. Questions Is Element Detection expected to inspect background elements behind a presented native SwiftUI sheet? Is this a known tool limitation/framework issue, or does the sample need different semantics? What is the supported way to establish modal accessibility boundaries with SwiftUI sheets, and when should .isModal be added explicitly? How should we distinguish a real contrast defect from clipping, occlusion, translucency, or sampling of an offscreen element? Which Inspector export fields/diagnostics should establish the actual sampled text/background pair? What additional evidence/manual and physical-device tests does Apple recommend before qualifying accessibility when the minimal audit reproduction fails but actual VoiceOver modal focus behaves correctly? We are not asking to waive audits or declare full accessibility from a VoiceOver pass alone. I read Apple's audit guidance and modal trait documentation: https://developer.apple.com/documentation/accessibility/performing-accessibility-audits-for-your-app https://developer.apple.com/documentation/swiftui/accessibilitytraits/ismodal https://developer.apple.com/help/app-store-connect/manage-app-accessibility/sufficient-contrast-evaluation-criteria/ Related discussion https://developer.apple.com/forums/thread/823968 recommends Feedback for a different apparent Dynamic Type false positive; it does not answer these modal/contrast questions. A Feedback draft is prepared but not submitted, so I have no Feedback ID yet. No private data, identifiers, credentials, app containers or confidential application source are included.
2
0
1k
6h
Supported non-admin service identity for a macOS LaunchDaemon
I'm developing a private macOS application on an Apple-silicon Mac mini running macOS Golden Gate 27.2. I'm evaluating a system LaunchDaemon running under a dedicated, non-administrator identity that cannot log in interactively. A separate desktop application would communicate with the daemon through authenticated local IPC. Before implementing this architecture, I would like to establish the officially supported approach. My main question: What is the Apple-supported method for creating and maintaining a dedicated, non-administrator, non-interactive service identity for a system LaunchDaemon on macOS 27.2? In particular: Is there a documented procedure for creating, restricting, disabling, recovering and eventually removing this identity? Are dscl, sysadminctl or another account-management mechanism supported for this purpose? Can a LaunchDaemon run under this identity without an interactive user login, including when registered through SMAppService? Are there any secure-token, FileVault, volume-ownership or keychain restrictions that would affect this design? If a dedicated non-login service identity is not a supported architecture, what alternative does Apple recommend? I'd particularly appreciate links to official Apple documentation or guidance from Apple engineers. Thank you.
8
0
544
6h
Why Does Apple Vision Pro Still Lack 3DoF / Head-Locked Display Support After Nearly 3 Years?
Why is this still not supported on Apple Vision Pro? For a premium device that has been on the market for nearly three years and costs thousands of dollars, it's difficult to understand why Apple still hasn't provided a basic option to disable spatial anchoring when it isn't needed. This limitation becomes particularly frustrating in moving environments such as cars, buses, trains, airplanes, and cruise ships. Users have repeatedly reported issues with virtual windows drifting, shifting, becoming unstable, or losing tracking entirely. Apple introduced Travel Mode to address some of these challenges, but reports of tracking problems persist, and certain environments remain unsupported. Why should something as simple as watching a movie or using a virtual monitor require constant 6DoF spatial tracking? Not every use case requires a fully spatial experience. Sometimes users simply want a stable virtual screen without the operating system constantly attempting to anchor it to their surroundings. At a minimum, visionOS should provide three display options: 6DoF Spatial Mode: The existing experience, with windows anchored to the physical environment. 3DoF Rotation-Only Mode: Virtual screens respond to head rotation without relying on positional tracking. Head-Locked Mode: A screen remains positioned directly in front of the user without requiring environmental anchoring. Other headsets have offered simplified tracking options for years. It's disappointing that a product at this price point still lacks comparable flexibility. Users shouldn't have to struggle with spatial tracking just to watch a movie, browse Safari, or use Mac Virtual Display, particularly when the hardware is capable of delivering an otherwise excellent viewing experience. Apple Vision Pro has been available for nearly three years. Why is such a fundamental display option still missing? Is there an actual technical limitation preventing Apple from implementing this, or has it simply not been prioritized? At this stage in the product's lifecycle, this shouldn't remain an unresolved limitation. Apple should provide users with greater control over display tracking rather than forcing every use case into the same spatial computing model. I'd like to hear whether Apple has any plans to address this in future visionOS releases.
2
0
586
6h
NEURLFilterManager: inconsistent per-domain blocking (some sites never block, one flaps) - confirmed PIR database is correct
Hello, Some context: DropBet is an app that helps people with gambling addiction stay off gambling sites and apps, using NEURLFilterManager/PIR to block a large list of known gambling domains system-wide. For a lot of our users this filter is a core part of their recovery > reliability really matters here. Since fixing an unrelated HPKE encryption bug (separate thread, now closed), the filter works end-to-end for the first time, but blocking is inconsistent per domain in a way I can't explain from my side: winamax.fr and the Winamax app: blocked reliably, every single time > clean "connection failed" style block, confirmed to load fine with protection off. unibet.fr and betclic.fr: never blocked, consistently > confirmed even after a full device reboot (rules out stale caching), and confirmed identical across both Safari and Chrome on iOS tested side-by-side (so not browser-specific). olybet.fr: flaps > the page reloads every 2-3 seconds with protection on, also identical across both browsers. Confirmed this only happens with the filter enabled (tested toggling protection off/on against the same page). unibet.fr auto-redirects into the native Unibet app via a Universal Link before the page loads, unlike betclic.fr which stays in the browser > different code path, possibly relevant. To rule out any issue on our end, I wrote a standalone test that queries our deployed PIR database shards directly - bypassing OHTTP, the app, and the device entirely - for all of the domains above plus their www. variants. All of them correctly return the blocked value, no exceptions, including unibet.fr and betclic.fr which never block on the actual device. So the database, the PIR protocol implementation, and the server are confirmed correct for every domain I've tested. This points at something in how NEURLFilterManager/ciphermld applies a correctly-received PIR verdict on-device - possibly related to query batching, an evaluation-key edge case, or Universal Link handling bypassing the filter before a web request is even made. Is there anything you can share about how the client applies results once decrypted, or known issues around any of this?
7
0
333
6h
StoreKit introductoryOfferEligibility: safe retry after JWS expiration
How should a server safely retire or renew an unused JWS for Product.PurchaseOption.introductoryOfferEligibility(compactJWS:) after cancellation or interruption? Our application allows a first-purchase discount once per application account across payment platforms. We bind the signed eligibility request to a verified Apple app transaction, product, and purchase attempt, persist the exact JWS, and reuse it for the same attempt. Once a paid purchase is verified, we consume the application's eligibility. We do not automatically issue another nonce after cancellation, a signature error, or an empty transaction history. Apple's JWS documentation describes a one-time nonce and expiration calculated from iat, and says not to include exp: https://developer.apple.com/documentation/storekit/generating-jws-to-sign-app-store-requests I could not find the lifetime or a supported retirement/renewal procedure for the introductory-offer-eligibility audience. Keeping an unusable authorization forever would prevent the customer from trying another checkout; replacing it without retiring the original might leave two redeemable authorizations. What we observed Environment: Xcode 27.2 (27B52), macOS 26.6.2, physical iPhone 16 with iOS 27.0, Apple Sandbox. Verify the Apple-signed AppTransaction and issue one eligibility JWS. Start the purchase using that JWS, then cancel the payment sheet (userCancelled). Terminate and relaunch the app without resetting purchase history or replacing the authorization. Retry the same product and Apple account using the byte-for-byte identical JWS. Complete the Sandbox purchase and verify the Apple-signed transaction on an isolated server. The successful verification happened about 164 seconds after issuance. This is one successful cancellation/retry observation, not a reproduced expiration failure or proof of a general validity/nonce-consumption rule. It also did not verify our intended introductory price. The purchase call uses the persisted value: let result = try await product.purchase(options: [ .introductoryOfferEligibility(compactJWS: existingJWS) ])Supported lifecycle questions What is the validity period derived from iat, including clock-skew allowances and any Sandbox/production differences? Which API or documented error can establish that a previously issued authorization is definitively unusable, rather than merely absent from transaction history? When is the nonce consumed, and what happens after userCancelled, interruption, pending approval, expiration, or an uncertain result? Is invalidOfferSignature specific enough to distinguish expiration from consumption, account mismatch, or a bad signature? Is it supported to keep the same nonce and all bindings, update only iat, and re-sign? If so, is one-time use enforced across every version and for what retention period? If renewal requires a new nonce, how can the prior authorization be invalidated first? Is there another recommended recovery flow that prevents duplicate redemption without indefinitely blocking checkout? DTS directed us to ask this lifecycle question on the forums. A sanitized minimal Xcode project was already supplied privately to DTS; it demonstrates the observed cancel/relaunch/same-JWS retry, not an expiration failure. We would appreciate a supported procedure or documentation reference.
1
0
75
7h
TestFlight dead on new account: internal invites never sent, 422 ENTITY_UNPROCESSABLE on beta review
Since my first TestFlight upload on November 2, 2026, TestFlight does not work for my app at all. This looks like the same account-level issue many developers have reported since late October 2026. Region: Türkiye Account: individual, enrolled October 26, 2026; latest Program License Agreement accepted November 6 App ID: 6828238853, builds 1.0 (1) and 1.0 (2) Symptoms: Internal testers stay "Invited", the INVITES column stays empty and no invitation email is ever sent. Submitting a build for external beta review always fails: POST /iris/v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE "There was an error processing your request. Please try again later." Error ID: a254e078-e9a9-44c4-be23-3d75d6d8daad API correlation key: 4IHT4ZPBDXIOSMH6J2GPZTDU5E Even saving "What to Test" notes for an internal build fails with "Validation Error". Already checked: Free Apps Agreement and DSA are active, Test Information, privacy policy, App Privacy, age rating and export compliance are complete, ITSAppUsesNonExemptEncryption = NO. A new build, reinvites and removing/re-adding testers did not help. Developer Support case 30000005085209 has been open since November 4. A reply dated November 17 shows on the case but the email never arrived. Could someone from the TestFlight team please check and re-provision the TestFlight setup for my account?
1
0
79
7h
W-8BEN line 2 locked with the wrong citizenship, Finance not replying
Same problem as threads 847696 and 80916, still happening in October 2026. I'm a Brazilian citizen living in the UK, enrolled as an individual. The U.S. Certificate of Foreign Status I submitted on 28 September recorded United Kingdom on line 2, and the W-8BEN copies it into its line 2 (citizenship) as locked text. I can't submit a W-8BEN with the wrong citizenship, so my Paid Apps Agreement is stuck at Pending User Info. Finance case 22532856 has had no reply since 28 September apart from the automatic acknowledgement. Has anyone had this reset? Did it take a phone call, or did someone at Apple reset the tax forms for you?
11
6
794
8h
Apple Developer Program paid but individual enrollment still Pending after 16 days
Hello Apple Developer Community, I am experiencing an issue with my individual Apple Developer Program enrollment and would appreciate any guidance from Apple staff or developers who have faced a similar situation. On November 2, 2026, I purchased the annual Apple Developer Program membership through the Apple Developer app on my iPhone for USD 98.99. The payment was successful, and my Apple Account shows the subscription with a renewal date of November 2, 2027. However, after 16 days, my individual enrollment still shows "Pending." What I have verified: My Apple Account recognizes the annual subscription and its renewal date. The Apple Developer app continues to display "Pending." On the Apple Developer website, my individual team appears as "Pending" and cannot be selected for membership operations. I cannot access certificates or provisioning resources under my individual membership. My Apple Account is also associated with a separate organization's developer team, where my role is Developer, not Account Holder. I have an open Apple Developer Support case and have submitted a follow-up request, but I have not received a resolution or an explanation. The available Developer Support contact options only offer email, with no telephone option. I am concerned that the subscription payment and developer enrollment may not have been correctly synchronized in Apple's systems. My questions are: Has anyone experienced a successful Apple Developer membership payment while the individual enrollment remained stuck in "Pending"? Could being a Developer on another organization's team affect activation of an individual membership? Is there a known way to resolve an enrollment synchronization issue or request a manual review? I need my own individual membership to publish my educational application independently from the organization I also work with. Any guidance would be greatly appreciated. Thank you.
Replies
0
Boosts
1
Views
128
Activity
6m
Apple In-App Purchase availability.
Hello, I am a developer based in Somalia and I have recently enrolled in the Apple Developer Program. I am planning to build an iOS app exclusively for users in Somalia. The app will offer premium digital features, and I would like to use WaafiPay, a local Somali payment provider that supports mobile-money payments such as EVC Plus, ZAAD and SAHAL. Somalia does not have an Apple App Store storefront or Apple In-App Purchase availability. Before I start development, I would like to confirm whether an app distributed to users in Somalia can use WaafiPay to process payments for premium digital features directly inside the app. If this is permitted, please let me know whether I need any special entitlement, approval, or implementation requirements. Thank you.
Replies
0
Boosts
0
Views
343
Activity
32m
iOS and Android
I currently have a iOS app live on the App Store but I also want to release it on Android, the whole code is in Swift so would that be possible or would I have to rewrite my whole apps code in a different coding language.
Replies
4
Boosts
0
Views
4k
Activity
36m
When IAPs would be available for Apple Watch?
I need someone from Apple to answer my question. I've added French localization to every of my IAP but I can't submit them due to this warning that sayws "In-app purchases and subscriptions are currently not supported on Apple Watch." The app is watchOS-only. Could you tell me please, when Could you tell me please, when IAPs would be supported?
Replies
2
Boosts
0
Views
207
Activity
1h
Can I identify the card network, such as Cartes Bancaires, from decrypted Apple Pay paymentData?
We are a merchant based in Europe and work with multiple PSPs, some of which do not support the Cartes Bancaires network. After decrypting the Apple Pay paymentData, is it possible to identify the card network or card brand, such as Cartes Bancaires, before submitting the transaction for authorization? If so, which field contains this information, and is Cartes Bancaires returned as a distinct value? For co-badged cards, does the decrypted payload indicate all available networks or only the network selected for the transaction? We would like to use this information to route transactions to a PSP that supports the relevant network, helping us improve authorization rates and reduce processing costs. Thank you.
Replies
0
Boosts
0
Views
123
Activity
4h
Disappointed with Apple Developer Support.
My company’s Apple Developer Program enrollment was declined without providing any specific reason or explanation. As a legally incorporated company, I submitted the required business documentation and identification. However, my enrollment was rejected without clarification about what went wrong. I respect Apple's verification and security procedures, but I believe developers and businesses deserve transparency, especially when they have followed the required process. A simple explanation of the reason for rejection would make a big difference. I'm hoping someone from Apple Developer Relations can help review this situation and provide clarification. #Apple #AppleDeveloper #DeveloperSupport #Entrepreneurship #Startups
Replies
0
Boosts
0
Views
135
Activity
4h
Version 1.0.0 stuck in "Waiting for Review" for ~2 weeks after an automated Guideline 2.5.1 message about the Family Controls entitlement
Our app — a screen-time / focus app — has had no App Review activity for two weeks, and we believe the trigger was an automated Guideline 2.5.1 check that froze an otherwise actively progressing review. (This forum account is linked to the developer account in question; we can provide the App ID, bundle IDs, submission IDs, and support case numbers through any private channel on request.) Context: Jul 2–5: Our first submission (Version 1.0.0) was under active review. We went through several ordinary metadata / paywall-related iterations, and the reviewer responded within roughly 24 hours each time. Nothing related to Screen Time was raised in these human reviews of builds 9 and 10. Jul 8: After we submitted build 11 — which addressed the remaining human-review feedback — we received an automated Guideline 2.5.1 (Performance: Software Requirements) message stating that the app uses the Screen Time API but has not been submitted with the Family Controls entitlement, and that review of the submission cannot proceed. All reviewer activity stopped at that point, and there has been none since. What we verified: The Family Controls (Distribution) entitlement is granted to our account and assigned to all four bundle IDs (the main app plus its DeviceActivityMonitor, ShieldAction, and ShieldConfiguration extensions). We verified with codesign that com.apple.developer.family-controls = true is present in the code signature and embedded provisioning profile of every one of the four executables in the submitted IPA — so the entitlement named in the automated message is present in the flagged build. For context: builds 9 and 10, with an identical Screen Time API surface and identical entitlements (verified at the binary level with nm against the submitted artifacts), had been human-reviewed on Jul 2–5 with no Screen Time-related objection. We recognize those builds may simply not have reached the automated analysis stage before being superseded, so we do not draw firm conclusions from that. What we did anyway (build 12, submitted Jul 9): In case the automated check actually concerns the separate com.apple.developer.family-controls.app-and-website-usage entitlement (which we do not request and do not need), we removed every reference from our main app to the APIs associated with it: AuthorizationStatus.approvedWithDataAccess, ManagedSettings.Application.bundleIdentifier, ManagedSettings.Application.localizedDisplayName, ManagedSettings.ActivityCategory.localizedDisplayName, and ManagedSettings.WebDomain.domain. We verified with nm that none of the four executables in the build 12 IPA reference these APIs. The app does not use FamilyActivityData, DeviceActivityReport, app usage events, web usage events, or App and Website Usage data access. No automated message has appeared for build 12. What has happened since: Jul 9–14: No reviewer activity on build 12. We filed an expedited review request and opened two Developer Support cases (Jul 8 and Jul 14). No response to any of them. Around Jul 15: Hoping to clear the frozen state, we cancelled and resubmitted the same Version 1.0.0 / build 12. Around Jul 17: Filed a second expedited review request for the new submission. Jul 22 (today): The new submission has been in "Waiting for Review" since Jul 15, with no reviewer activity and no reply to either support case or either expedite request. What we are asking: Could someone check whether the Jul 8 automated flag is still attached to the app record and blocking reviewer assignment, and help get the current submission assigned to a reviewer? If the automated check flags build 12 again, could the message specify which entitlement and which binary / API references triggered it, so we can address it precisely? We can provide codesign output, entitlement plists, provisioning profile dumps, and nm symbol listings on request. Thank you.
Replies
4
Boosts
2
Views
1.3k
Activity
4h
Automated 2.5.1 "not submitted with the Family Controls entitlement" although entitlement is assigned and in the build
My first submission was stopped by an automated App Review message, and I can't find anything on my side to fix. It looks the same as the reports in thread 838802. The message (Guideline 2.5.1): "An automated analysis indicates the app uses one or more Screen Time APIs but the app has not been submitted with the Family Controls entitlement." App Name: blorbs, Apple ID 6836228369 Bundle ID: app.blorb.ios, Team ID: WVVPTV9U33 Version 1.0.0 (1), submitted Nov 18, 2026, 1:29 AM PT Automated message received Nov 18, 10:34 AM PT Submission ID: 4d3288f6-3a5b-48cb-8f1e-20fc01a55c14 Built with Xcode 26.6 (iOS 26.5 SDK), minimum iOS 17, automatic signing What the app is A personal focus app. The user picks apps to lock on their own device (individual authorization) and unlocks them by tapping an NFC accessory. Targets: the main app, a DeviceActivityMonitor extension, a ShieldConfiguration extension, and a widget / Live Activity extension. What I verified Approval: Apple Developer Relations emailed on Nov 11, 2026 that Family Controls (Distribution) "has been assigned to your account". Portal: Capability Requests shows Family Controls (Distribution) as Assigned on app.blorb.ios, app.blorb.ios.monitor and app.blorb.ios.shield. Provisioning Support lists Development, Ad hoc, App Store Connect. The uploaded build: App Store Connect > TestFlight > Build Metadata > Entitlements shows com.apple.developer.family-controls: true on the main app, the monitor extension and the shield extension. Binary State: Validated. The widget extension has no Screen Time code and links none of FamilyControls, ManagedSettings, ManagedSettingsUI or DeviceActivity, so it correctly has no entitlement. What the app does not use No App and Website Usage entitlement, no approvedWithDataAccess, no FamilyActivityData No DeviceActivityReport extension, no ShieldAction extension The only related calls are Application.localizedDisplayName and WebDomain.domain, read inside the ShieldConfigurationDataSource to show the name of the shielded app or site, as the documentation describes. What I've done Replied in App Store Connect with the details above Submitted an appeal to the App Review Board Questions Could someone from App Review or DTS check whether this automated flag is correct for this submission, and whether it's blocking reviewer assignment? Can the message say which binary or API triggered it? Apple's own record of the build lists the entitlement on every Screen Time binary. Has anyone had this cleared, and what did it take? Happy to share build IDs, entitlement dumps or anything else privately.
Replies
0
Boosts
0
Views
143
Activity
4h
"Your Apple Account isn't enabled for App Store Connect"
I'm the Account Holder for my company. The organization's membership became active on November 16, 2026 (welcome email at 5:25 PM Central), and every agreement is accepted on developer.apple.com/account. Certificates, Identifiers & Profiles works for the team. Signing in to App Store Connect with the same Account Holder Apple Account gives "Your Apple Account isn't enabled for App Store Connect", at https://appstoreconnect.apple.com/m/INVALIDITCUSER?errorKey=ITC.signin.error.invalidUser.asc. I've tried a private window, another browser, and signing out and back in. Any idea how to fix?
Replies
3
Boosts
1
Views
229
Activity
5h
iPhone Duo Unfolded Safe Areas
Hi, my app is currently built on Xcode 27.1 I am working on upgrading to Xcode 27.2 We have a regression issue whereby, the top safeArea is 82 despite the vertical bar being opted in and active. This only happens on unfolded landscape. Our right safeArea is 0 for the window and is 84 for the view safeArea. Both window and view safeAreas have the top safe area of 82 though. We would like to know what could be the cause behind the top safeArea being activated. Note: this is not an issue for iOS 27.1
Replies
2
Boosts
0
Views
180
Activity
5h
SwiftUI Architecture Guide
Application Types Applications are divided into Document-based and Library-based. A document-based application stores user data in individual, standalone files. Users manually name and organize those files in a local system or synced cloud storage such as iCloud. The software typically opens multiple windows for different projects. This framing is for standalone, complex files that need to be shared, exported, or handled independently. A library-based application manages data in one unified, central repository, locally or through remote cloud databases. Spotify, Netflix, and Notion are the examples shown. The file system is hidden; updates are saved automatically in real time; and a single window supports browsing, search, and access to the synchronized data collection from any device. Model Types Four model types: Data, Domain, Application, and Presentation. Apple Platforms In Apple MVC (AppKit / UIKit), the model branches to Data, Domain, and Presentation. In SwiftUI, Model branches to Data and Domain. Project Structure SwiftUI App Folders Swift Package Folders App Modularization Not every module in a large application needs to be extracted into a separate framework or Swift Package. Logical modularization can also be achieved through a well-organized folder structure within the main project. Introduce separate packages or frameworks only when there is a clear benefit, such as independent reuse, distribution, build isolation or ownership. Avoid unnecessary project and dependency management overhead. State Management & Data Flow Source of truth is “a key concept in SwiftUI”: a single place to store a piece of data, with everywhere else reading the same piece of data. Environment is SwiftUI’s native dependency-injection mechanism. It allows shared dependencies, domain models, and services to be injected at the appropriate view-hierarchy level and accessed where needed without explicit parameter passing or unnecessary coupling. It is described as a tool for managing dependencies and sharing state across the view hierarchy. Domain Model Ownership Domain Models should be owned by the highest relevant SwiftUI view in the hierarchy that defines their context and lifecycle. NavigationStack owns the Domain Models for its navigation context and makes them available to descendant views through @Environment. When a NavigationStack is embedded in a TabView or NavigationSplitView, ownership moves up to the TabView or NavigationSplitView so the models can be shared across tabs or split views. The stated result is clear ownership scope, sharing where needed, and isolation between independent navigation contexts. Previews & UI Testing Environment injection makes SwiftUI Previews and UI Tests easier to configure by allowing real Domain Models to be replaced with mock or dummy instances. Views can be tested independently with controlled data and predictable states, without requiring real services, network requests, or application setup. Domain and Data Model Examples For a library-based app with remote data. Additional Domain Model Examples E-commerce Catalog, ShoppingCart, OrderHistory, Wishlist Banking MyAccounts, MyCards, MyTransactions, MyInvestments Social Network Feed, Conversations, Notifications, Friends Healthcare MyAppointments, MedicalHistory, Prescriptions, MyHealth Education Courses, MyCourses, Assignments, MyGrades, LearningProgress Real Estate PropertyCatalog, MyProperties, Favorites, Appointments Hotel Booking Destinations, Search, MyBookings, TravelHistory Food Delivery RestaurantCatalog, ShoppingCart, MyOrders, DeliveryTracking Project Management Projects, MyTasks, TeamMembers, Notifications Insurance MyPolicies, MyClaims, Coverage, Documents Smart Home MyHomes, Devices, Automations, EnergyUsage Fitness MyPlans, MyProgress, MyGoals, WorkoutHistory Other Search, Dashboard, Favorites, Notifications, Settings, ActivityHistory, Recommendations, Subscription, DocumentLibrary ViewModel? - MVVM In SwiftUI, the View encapsulates the UI content (body), its state (properties), and its actions or tasks (functions). This is possible because SwiftUI is designed around a declarative, state-driven UI model. In Android and .NET platforms, a separate ViewModel is typically required to hold and manage the View's state. Projects that intoduce ViewModels in SwiftUI add unnecessary architectural complexity, boilerplate, and code duplication; synchronization issues; unclear state ownership; additional lifecycle management; more abstractions; harder debugging; and increased maintenance, without meaningful benefits over SwiftUI's native state management. In UIKit, introducing a separate ViewModel layer is often unnecessary, as UIViewController already serves as the presentation model, handling presentation logic and coordinating the view. Non-UI responsibilities can be delegated to dedicated ModelControllers or Managers, avoiding unnecessary layers and abstractions. Domain Models vs. ViewModels Domain Models are view-independent, while ViewModels are view-dependent. A ViewModel is tightly coupled to the structure, state, and lifecycle of a specific View. Whenever the View code changes, its ViewModel often requires corresponding coding changes, and vice versa, creating additional maintenance and synchronization overhead. Domain Models, on the other hand, represent application context and business functionality independently of the UI. This separation preserves UI independence and allows the same Domain Models to be shared across different screens and platforms, such as iPhone, iPhone Duo, iPad, and macOS, without duplicating or adapting business logic for each View. This makes Domain Models a more scalable and maintainable approach for modern SwiftUI applications, particularly those targeting multiple screen sizes and platforms.
Replies
1
Boosts
0
Views
205
Activity
5h
Accessibility Inspector Element Detection and contrast failures with SwiftUI sheets
I am investigating Accessibility Inspector/XCTest audit results in a SwiftUI app (Target Keeper), without suppressing warnings. Environment: Xcode 27.1 (27A9275), iPadOS 27.0 Simulator, macOS 27.0.1. Debug and Release builds pass. The app uses scalable text and labeled controls. Element Detection / native sheet Main-screen Element Detection passes when the sheet is closed. With a SwiftUI .sheet presented, the iPad audit reports “Potentially inaccessible text”; XCUIAccessibilityAuditIssue.element is nil. Exported Inspector HTML highlights background labels behind/outside the sheet, rather than a foreground control. The separate, data-free SwiftUI application below reproduces the modal-only warning; it links no application modules or persistence. Actual iPad Simulator VoiceOver testing using XCUIDevice.shared.voiceOverService passes forward/backward traversal of the real application's modal controls, without reaching the background labels. This is simulator evidence, not physical-device acceptance. A trial explicit modal container/.isModal trait did not clear the audit and was reverted; no warnings are filtered. Minimal independent app: import SwiftUI @main struct ModalRepro: App { @State private var showing=false private let names=["Vegetables","Protein","Fruit","Dairy","Grains","Healthy Fats"] var body:some Scene {WindowGroup { NavigationStack { VStack(spacing:24) { Button("Nutrition") {}.accessibilityLabel("Choose Page").accessibilityValue("Nutrition") LazyVGrid(columns:[GridItem(.flexible()),GridItem(.flexible()),GridItem(.flexible())],spacing:40) { ForEach(names,id:\.self) { name in Button {} label: { VStack(spacing:10) { Circle().fill(.blue.opacity(0.3)).frame(width:250,height:250) Text(name).font(.system(size:17)).accessibilityHidden(true) } }.buttonStyle(.plain).accessibilityLabel(name) } } Button("Show modal") {showing=true} }.padding(24).frame(maxWidth:.infinity,maxHeight:.infinity).background(Color.black) }.preferredColorScheme(.dark) .sheet(isPresented:$showing) { NavigationStack { VStack {Text("Foreground content");Button("Close") {showing=false}} .frame(maxWidth:.infinity,maxHeight:.infinity).background(Color.black) .navigationTitle("Modal flow") }.preferredColorScheme(.dark) } }} }In an Xcode UI-test target, launch this app, run try app.performAccessibilityAudit(for: [.elementDetection]), tap “Show modal”, then run the same audit again. The first passes and the second fails. No issue handler ignores failures. Contrast / scrolling — separate unresolved finding All four iPhone combined-audit configurations (portrait/landscape, normal/maximum Dynamic Type) pass in the tested picker state. However, iPad maximum-text combined audits and a separate scrolled iPhone maximum-text landscape contrast audit still fail; we are not calling these resolved. In the scrolled iPhone case, XCTest identifies a count label whose frame is entirely above the visible results viewport. Inspector's exported HTML reports 1.37:1 using #252526 versus #000000; its marked screenshot rectangle overlaps the dark search/header area, not visible count text. Visible sampled labels instead have white or light foregrounds on opaque dark fills (e.g. #FFFFFF/#1C1C1E = 17.01:1; #98989F/#1C1C1E = 5.94:1). These are screenshot core-pixel measurements, not proof every warning is false. We compare ordinary text against 4.5:1 and interactive non-text against 3:1. iPad maximum-text warnings have not yet been matched to an exact visible color pair. Original failures and HTML exports are preserved privately. Questions Is Element Detection expected to inspect background elements behind a presented native SwiftUI sheet? Is this a known tool limitation/framework issue, or does the sample need different semantics? What is the supported way to establish modal accessibility boundaries with SwiftUI sheets, and when should .isModal be added explicitly? How should we distinguish a real contrast defect from clipping, occlusion, translucency, or sampling of an offscreen element? Which Inspector export fields/diagnostics should establish the actual sampled text/background pair? What additional evidence/manual and physical-device tests does Apple recommend before qualifying accessibility when the minimal audit reproduction fails but actual VoiceOver modal focus behaves correctly? We are not asking to waive audits or declare full accessibility from a VoiceOver pass alone. I read Apple's audit guidance and modal trait documentation: https://developer.apple.com/documentation/accessibility/performing-accessibility-audits-for-your-app https://developer.apple.com/documentation/swiftui/accessibilitytraits/ismodal https://developer.apple.com/help/app-store-connect/manage-app-accessibility/sufficient-contrast-evaluation-criteria/ Related discussion https://developer.apple.com/forums/thread/823968 recommends Feedback for a different apparent Dynamic Type false positive; it does not answer these modal/contrast questions. A Feedback draft is prepared but not submitted, so I have no Feedback ID yet. No private data, identifiers, credentials, app containers or confidential application source are included.
Replies
2
Boosts
0
Views
1k
Activity
6h
Supported non-admin service identity for a macOS LaunchDaemon
I'm developing a private macOS application on an Apple-silicon Mac mini running macOS Golden Gate 27.2. I'm evaluating a system LaunchDaemon running under a dedicated, non-administrator identity that cannot log in interactively. A separate desktop application would communicate with the daemon through authenticated local IPC. Before implementing this architecture, I would like to establish the officially supported approach. My main question: What is the Apple-supported method for creating and maintaining a dedicated, non-administrator, non-interactive service identity for a system LaunchDaemon on macOS 27.2? In particular: Is there a documented procedure for creating, restricting, disabling, recovering and eventually removing this identity? Are dscl, sysadminctl or another account-management mechanism supported for this purpose? Can a LaunchDaemon run under this identity without an interactive user login, including when registered through SMAppService? Are there any secure-token, FileVault, volume-ownership or keychain restrictions that would affect this design? If a dedicated non-login service identity is not a supported architecture, what alternative does Apple recommend? I'd particularly appreciate links to official Apple documentation or guidance from Apple engineers. Thank you.
Replies
8
Boosts
0
Views
544
Activity
6h
Why Does Apple Vision Pro Still Lack 3DoF / Head-Locked Display Support After Nearly 3 Years?
Why is this still not supported on Apple Vision Pro? For a premium device that has been on the market for nearly three years and costs thousands of dollars, it's difficult to understand why Apple still hasn't provided a basic option to disable spatial anchoring when it isn't needed. This limitation becomes particularly frustrating in moving environments such as cars, buses, trains, airplanes, and cruise ships. Users have repeatedly reported issues with virtual windows drifting, shifting, becoming unstable, or losing tracking entirely. Apple introduced Travel Mode to address some of these challenges, but reports of tracking problems persist, and certain environments remain unsupported. Why should something as simple as watching a movie or using a virtual monitor require constant 6DoF spatial tracking? Not every use case requires a fully spatial experience. Sometimes users simply want a stable virtual screen without the operating system constantly attempting to anchor it to their surroundings. At a minimum, visionOS should provide three display options: 6DoF Spatial Mode: The existing experience, with windows anchored to the physical environment. 3DoF Rotation-Only Mode: Virtual screens respond to head rotation without relying on positional tracking. Head-Locked Mode: A screen remains positioned directly in front of the user without requiring environmental anchoring. Other headsets have offered simplified tracking options for years. It's disappointing that a product at this price point still lacks comparable flexibility. Users shouldn't have to struggle with spatial tracking just to watch a movie, browse Safari, or use Mac Virtual Display, particularly when the hardware is capable of delivering an otherwise excellent viewing experience. Apple Vision Pro has been available for nearly three years. Why is such a fundamental display option still missing? Is there an actual technical limitation preventing Apple from implementing this, or has it simply not been prioritized? At this stage in the product's lifecycle, this shouldn't remain an unresolved limitation. Apple should provide users with greater control over display tracking rather than forcing every use case into the same spatial computing model. I'd like to hear whether Apple has any plans to address this in future visionOS releases.
Replies
2
Boosts
0
Views
586
Activity
6h
NEURLFilterManager: inconsistent per-domain blocking (some sites never block, one flaps) - confirmed PIR database is correct
Hello, Some context: DropBet is an app that helps people with gambling addiction stay off gambling sites and apps, using NEURLFilterManager/PIR to block a large list of known gambling domains system-wide. For a lot of our users this filter is a core part of their recovery > reliability really matters here. Since fixing an unrelated HPKE encryption bug (separate thread, now closed), the filter works end-to-end for the first time, but blocking is inconsistent per domain in a way I can't explain from my side: winamax.fr and the Winamax app: blocked reliably, every single time > clean "connection failed" style block, confirmed to load fine with protection off. unibet.fr and betclic.fr: never blocked, consistently > confirmed even after a full device reboot (rules out stale caching), and confirmed identical across both Safari and Chrome on iOS tested side-by-side (so not browser-specific). olybet.fr: flaps > the page reloads every 2-3 seconds with protection on, also identical across both browsers. Confirmed this only happens with the filter enabled (tested toggling protection off/on against the same page). unibet.fr auto-redirects into the native Unibet app via a Universal Link before the page loads, unlike betclic.fr which stays in the browser > different code path, possibly relevant. To rule out any issue on our end, I wrote a standalone test that queries our deployed PIR database shards directly - bypassing OHTTP, the app, and the device entirely - for all of the domains above plus their www. variants. All of them correctly return the blocked value, no exceptions, including unibet.fr and betclic.fr which never block on the actual device. So the database, the PIR protocol implementation, and the server are confirmed correct for every domain I've tested. This points at something in how NEURLFilterManager/ciphermld applies a correctly-received PIR verdict on-device - possibly related to query batching, an evaluation-key edge case, or Universal Link handling bypassing the filter before a web request is even made. Is there anything you can share about how the client applies results once decrypted, or known issues around any of this?
Replies
7
Boosts
0
Views
333
Activity
6h
StoreKit introductoryOfferEligibility: safe retry after JWS expiration
How should a server safely retire or renew an unused JWS for Product.PurchaseOption.introductoryOfferEligibility(compactJWS:) after cancellation or interruption? Our application allows a first-purchase discount once per application account across payment platforms. We bind the signed eligibility request to a verified Apple app transaction, product, and purchase attempt, persist the exact JWS, and reuse it for the same attempt. Once a paid purchase is verified, we consume the application's eligibility. We do not automatically issue another nonce after cancellation, a signature error, or an empty transaction history. Apple's JWS documentation describes a one-time nonce and expiration calculated from iat, and says not to include exp: https://developer.apple.com/documentation/storekit/generating-jws-to-sign-app-store-requests I could not find the lifetime or a supported retirement/renewal procedure for the introductory-offer-eligibility audience. Keeping an unusable authorization forever would prevent the customer from trying another checkout; replacing it without retiring the original might leave two redeemable authorizations. What we observed Environment: Xcode 27.2 (27B52), macOS 26.6.2, physical iPhone 16 with iOS 27.0, Apple Sandbox. Verify the Apple-signed AppTransaction and issue one eligibility JWS. Start the purchase using that JWS, then cancel the payment sheet (userCancelled). Terminate and relaunch the app without resetting purchase history or replacing the authorization. Retry the same product and Apple account using the byte-for-byte identical JWS. Complete the Sandbox purchase and verify the Apple-signed transaction on an isolated server. The successful verification happened about 164 seconds after issuance. This is one successful cancellation/retry observation, not a reproduced expiration failure or proof of a general validity/nonce-consumption rule. It also did not verify our intended introductory price. The purchase call uses the persisted value: let result = try await product.purchase(options: [ .introductoryOfferEligibility(compactJWS: existingJWS) ])Supported lifecycle questions What is the validity period derived from iat, including clock-skew allowances and any Sandbox/production differences? Which API or documented error can establish that a previously issued authorization is definitively unusable, rather than merely absent from transaction history? When is the nonce consumed, and what happens after userCancelled, interruption, pending approval, expiration, or an uncertain result? Is invalidOfferSignature specific enough to distinguish expiration from consumption, account mismatch, or a bad signature? Is it supported to keep the same nonce and all bindings, update only iat, and re-sign? If so, is one-time use enforced across every version and for what retention period? If renewal requires a new nonce, how can the prior authorization be invalidated first? Is there another recommended recovery flow that prevents duplicate redemption without indefinitely blocking checkout? DTS directed us to ask this lifecycle question on the forums. A sanitized minimal Xcode project was already supplied privately to DTS; it demonstrates the observed cancel/relaunch/same-JWS retry, not an expiration failure. We would appreciate a supported procedure or documentation reference.
Replies
1
Boosts
0
Views
75
Activity
7h
TestFlight dead on new account: internal invites never sent, 422 ENTITY_UNPROCESSABLE on beta review
Since my first TestFlight upload on November 2, 2026, TestFlight does not work for my app at all. This looks like the same account-level issue many developers have reported since late October 2026. Region: Türkiye Account: individual, enrolled October 26, 2026; latest Program License Agreement accepted November 6 App ID: 6828238853, builds 1.0 (1) and 1.0 (2) Symptoms: Internal testers stay "Invited", the INVITES column stays empty and no invitation email is ever sent. Submitting a build for external beta review always fails: POST /iris/v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE "There was an error processing your request. Please try again later." Error ID: a254e078-e9a9-44c4-be23-3d75d6d8daad API correlation key: 4IHT4ZPBDXIOSMH6J2GPZTDU5E Even saving "What to Test" notes for an internal build fails with "Validation Error". Already checked: Free Apps Agreement and DSA are active, Test Information, privacy policy, App Privacy, age rating and export compliance are complete, ITSAppUsesNonExemptEncryption = NO. A new build, reinvites and removing/re-adding testers did not help. Developer Support case 30000005085209 has been open since November 4. A reply dated November 17 shows on the case but the email never arrived. Could someone from the TestFlight team please check and re-provision the TestFlight setup for my account?
Replies
1
Boosts
0
Views
79
Activity
7h
W-8BEN line 2 locked with the wrong citizenship, Finance not replying
Same problem as threads 847696 and 80916, still happening in October 2026. I'm a Brazilian citizen living in the UK, enrolled as an individual. The U.S. Certificate of Foreign Status I submitted on 28 September recorded United Kingdom on line 2, and the W-8BEN copies it into its line 2 (citizenship) as locked text. I can't submit a W-8BEN with the wrong citizenship, so my Paid Apps Agreement is stuck at Pending User Info. Finance case 22532856 has had no reply since 28 September apart from the automatic acknowledgement. Has anyone had this reset? Did it take a phone call, or did someone at Apple reset the tax forms for you?
Replies
11
Boosts
6
Views
794
Activity
8h