Prioritize user privacy and data security in your app. Discuss best practices for data handling, user consent, and security measures to protect user information.

All subtopics
Posts under Privacy & Security topic

Post

Replies

Boosts

Views

Activity

Privacy & Security Resources
General: Forums topic: Privacy & Security Privacy Resources Security Resources Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com"
0
0
1.5k
Jul ’25
Sign in with Apple: "Sign Up Not Completed" for every App ID in our team — framework returns canceled (1001) with empty userInfo
Sign in with Apple fails for every App ID in our team (K9UFUZF2XW), on every device and every Apple ID we have tried. The system sheet appears, the user authenticates successfully, the sheet then shows "Sign Up Not Completed", and no credential is returned. The failure happens after authentication — this is not a client-side rejection. I have spent several days isolating this and have ruled out everything on my side. Posting the full evidence in case an Apple engineer can look at the server-side state for our team, and in case it helps others hitting the same wall. WHAT THE FRAMEWORK ACTUALLY RETURNS The client library we use (expo-apple-authentication) discards the original NSError, so I patched its native layer to surface the raw error verbatim. This is what ASAuthorizationController hands back to didCompleteWithError, immediately after the user authenticated and the sheet displayed "Sign Up Not Completed": ASAuthorizationError .canceled (rawValue = 1001) domain = com.apple.AuthenticationServices.AuthorizationError code = 1001 desc = The operation couldn't be completed. (com.apple.AuthenticationServices.AuthorizationError, error 1001) userInfo: NSUnderlyingError: So the framework reports a user cancellation that never happened, with a completely empty userInfo and no underlying error. There is no diagnostic information on the client at all — I cannot debug this any further from my side, because the information does not exist there. Note: the same failure surfaces as a different error code depending on the client library version — .unknown (1000) with the older version, .canceled (1001) with the current one. The user-visible behaviour ("Sign Up Not Completed") is identical in both. So the error code is not a reliable signal here. WHAT I RULED OUT Not the App ID. I created a brand-new App ID (kz.auraai.ios) with Sign in with Apple enabled as a primary App ID, built a fresh binary, tested on the same device with the same Apple ID — identical failure. Two independent App IDs in the same team fail the same way. Not the entitlement. Verified inside the signed binary, not just in the portal: application-identifier = K9UFUZF2XW.kz.auraai.ios com.apple.developer.applesignin = ["Default"] I also tried the workaround suggested elsewhere on these forums (removing the entitlement while keeping the capability in the portal). That made it strictly worse: iOS then rejects the request instantly, without showing the sheet at all. Which confirms iOS reads the entitlement correctly, the sheet works, and the user authenticates — the failure is downstream of all of that. No stray or wildcard App IDs. A commonly cited cause is other App IDs in the team lacking the entitlement. I enumerated the whole team via the App Store Connect API: it contains exactly two App IDs, both with APPLE_ID_AUTH = PRIMARY_APP_CONSENT. No wildcard identifiers exist. Not the Apple ID, the device, or the iOS version. The same Apple ID, on the same device, with the same iOS, signs in successfully through another app belonging to a different team (Expo Go, host.exp.Exponent) — a valid identity token is returned. A second, unrelated Apple ID on another device fails in my app in exactly the same way. So this is not scoped to one account: it affects every user of the app. Agreements and membership are in good standing. Program License Agreement accepted 30 June 2026; Developer Agreement accepted 26 June 2026; membership active. Both distribution types fail. TestFlight and ad-hoc. WHAT IS LEFT After all of the above, the only variable that differs between the working case (a different team's app, same device, same Apple ID) and the failing case (my app) is the Apple Developer team itself. This exact signature — sheet renders fully, final server submit fails, "Sign Up Not Completed", delegate reports canceled with no userInfo, not reproducible in other apps on the same device — is documented in thread 122458 ("Error: Sign-Up Not Completed"). In that case it affected multiple developers, including Apple's own sample app, and was ultimately resolved by Apple on the server side, with a recurrence reported in June 2025. THE ASK Could someone from Apple check the server-side Sign in with Apple registration for team K9UFUZF2XW (App IDs kz.auraai.app and kz.auraai.ios)? I am not looking for configuration advice — I have exhausted the client side and there is nothing left to configure. This looks like the same server-side state that was fixed in the referenced cases. Feedback Assistant: FB23716661 (includes sysdiagnose with the Accounts/AuthKit profile, timestamp, and video of the failure). This is currently blocking us: because Sign in with Apple works for none of our users, guideline 4.8 prevents us from offering Google Sign-In, so we are shipping with email-only login. Happy to provide the binary, entitlements dump, or a fresh sysdiagnose on request.
137
6
34k
9h
Reading Mouse Events with CGEvent tap from a background app in macOS 27.3
WIth macOS 27.3 (beta 2) things have changed quite a bit for security, see Updates to Device Control and Data Access, and Full Disk Access in macOS I have an app which uses what (used to be called) the Privacy & Security / Accessibility permissions in order to receive mouse events in the background to read them and occasionally modify them. The method used: The app checks AXIsProcessTrustedWithOptions to see if it has permission. If it doesn't have permission, it uses the kAXTrustedCheckOptionPrompt option which would open up the privacy & Security / Accessibility pane. Because that process has been a little flakey in macOS, my app has a backup option, where it runs 'open "x-apple.systempreferences:com.apple.settings.PrivacySecurity.extension?Privacy_Accessibility"' and then walks the user through the steps with onscreen instructions. When permission is granted, the app creates a CGEvent tap SessionEvent tap using the HeadInsertEvent option to receive mouse and touch mouse events. See CGEvent.tapCreate In macOS 27.3 beta 2, always returns false using kAXTrustedCheckOptionPrompt fails to do anything open "x-apple.systempreferences:com.apple.settings.PrivacySecurity.extension?Privacy_Accessibility fails to do anything. CGEvent tap fails A few questions: will my third party app be allowed to use CGEventTaps to read mouse and touchpad events? Or has this been cut off completely and only available to first party apps? If it is allowed, how? Has the permission for this moved to a different System Preference pane? is a CGEvent tap the way to do it? I totally understand that security is important, and apps should not have wide-ranging permissions. I'd love to find a way to keep my app running with the minimal permissions needed.
5
0
491
10h
ATT prompt not shown and status stays notDetermined: how do you handle it?
Hello, our Unity game (iOS/iPadOS) requests App Tracking Transparency on its first scene, before ads are initialized. Background App Review rejected an earlier build under Guideline 2.1(a) for a blank screen on iPad Air 11-inch (M3), iPadOS 27.0. In that build we called requestTrackingAuthorization right at launch and then waited until trackingAuthorizationStatus was no longer .notDetermined. The status never changed, so the app never left the first screen. Current flow (this build was approved) Wait until UIApplication.shared.applicationState == .active and the app has focus. Call requestTrackingAuthorization(completionHandler:) once and wait for the completion handler. If the completion returns .notDetermined, wait about 4 seconds while the app stays active, then call it one more time. Wait until the status is no longer .notDetermined before loading the next scene. There is no timeout. The first scene runs on every cold launch, so if the status is still .notDetermined, the request is made again on the next launch. [ATTrackingManager requestTrackingAuthorizationWithCompletionHandler:^(ATTrackingManagerAuthorizationStatus status) { dispatch_async(dispatch_get_main_queue(), ^{ // store status; Unity polls it on the main thread }); }];We have not been able to reproduce the original problem on our own devices. Questions for those who have shipped apps with ATT How many times do you retry requestTrackingAuthorization, and how long do you wait between attempts? Is there any limit you know of? If the status still stays .notDetermined after retrying, do you let the user continue and treat it as not authorized (no IDFA), or keep waiting? If you wait, how long before you let the user continue? If you continue without tracking, did App Review ever flag that? Any experience or pointers to documentation would be appreciated.
0
0
18
10h
macOS 27: Accessibility granted via MDM doesn’t cover PostEvent, and leaves a stray TCC managed_overrides row after unenrollment
Our app uses an active CGEventTap (kCGEventTapOptionDefault, mouse down/up events) and relies on the Accessibility permission (Device Control & Data Access). CGEventTapCreate(kCGAnnotatedSessionEventTap, kCGHeadInsertEventTap, kCGEventTapOptionDefault, CGEventMaskBit(kCGEventLeftMouseDown) | CGEventMaskBit(kCGEventLeftMouseUp) | CGEventMaskBit(kCGEventRightMouseDown) | CGEventMaskBit(kCGEventRightMouseUp) | CGEventMaskBit(kCGEventOtherMouseDown) | CGEventMaskBit(kCGEventOtherMouseUp), callback, refcon);On macOS 27.0.1 we see two behaviours when that permission comes from MDM, and we’d like to know whether they’re expected. According to the PrivacyPreferencesPolicyControl.Services documentation, the PPPC Accessibility key is deprecated in macOS 27. It’s replaced by the Privacy → PermissionDefaults setting in the declarative configuration com.apple.configuration.app.settings, and the managed value is a default that the user can change. We tested both the PPPC payload and the DDM configuration. 1. Managed Accessibility grant doesn’t cover PostEvent When the user turns on Accessibility manually in System Settings > Privacy & Security > Accessibility, the event tap works with no further prompts. When Accessibility comes from device management (a PPPC payload or DDM PermissionDefaults): AXIsProcessTrusted() returns true. On the first click through the tap, macOS shows the “control this computer” prompt. tccd adds an access row for kTCCServicePostEvent with auth_value 0 and auth_reason 4. At the same moment, the app’s Accessibility toggle in System Settings switches off. The managed Accessibility row remains auth_value 2, auth_reason 6. After the user accepts the prompt, PostEvent changes to auth_value 2 and the tap works from then on. Questions : Why does a manual Accessibility grant cover an active event tap, while a managed Accessibility default needs a separate PostEvent grant? With PPPC Accessibility deprecated, is DDM Accessibility plus PPPC PostEvent (Allowed) the intended configuration for apps that install active event taps? 2. Stray managed_overrides row after unenrollment On macOS 27, the managed Accessibility value is stored in a new managed_overrides table in /Library/Application Support/com.apple.TCC/TCC.db (schema version 36). On macOS 15 and 26, managed grants were kept in MDMOverrides.plist, and this table doesn’t exist there. Steps : Enroll a never-managed Mac in MDM with user-approved enrollment. Install a profile that grants Accessibility to our app. tccd logs ManagedSettings: inserted managed_overrides for kTCCServiceAccessibility:<bundle id> admin_auth_value=2 auth_value=2. The row is written with policy_id NULL, and policies and active_policy stay empty. Remove the MDM profile from System Settings > General > Device Management. What happens: mdmclient removes the MDM profile first. Removing each TCC payload after that fails with : PlugIn: DetermineUninstallFlags [TCCProfileService] Error: Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied" UserInfo={NSLocalizedDescription=The profile must originate from a user-approved MDM server.}The profiles disappear, MDMOverrides.plist is deleted, and profiles status reports no MDM enrollment. The row remains, with auth_value 1, auth_reason 6 (MDM Policy), policy_id NULL, admin_auth_value 2 and flags 480. tccutil reset Accessibility <bundle id> clears flags but doesn’t remove the row. Later permission prompts and System Settings toggles for the app write to this row instead of to access. Why does the row stay after unenrollment? Is there a supported way to clear it?
2
1
217
11h
No lifecycle notification when entering App Switcher while app remains inactive after Face ID
We use LAContext.evaluatePolicy(.deviceOwnerAuthentication) for a local app lock. On an iPhone 16 Pro running iOS 26.6.2, after authentication succeeds, UIApplication.shared.applicationState can remain .inactive for approximately 2–8 seconds although the app UI is visible. If the user enters the App Switcher during this interval, the app receives no additional willResignActive or didEnterBackground notification. Returning to the app produces only didBecomeActive. This means the app cannot distinguish between: remaining in the app while the Face ID UI finishes dismissing; and entering the App Switcher and returning during the same inactive interval. Reproduction: Run a minimal UIKit app on a physical Face ID device. Call evaluatePolicy(.deviceOwnerAuthentication). Immediately after successful authentication, enter the App Switcher before didBecomeActive. Wait three seconds and return. Is there a supported public API or lifecycle pattern that lets an app lock immediately in this situation without keeping its content covered until didBecomeActive?
1
0
37
12h
App Attest keys stop working after reboot on macOS 27.2.1
App Attest keys stop working after reboot on macOS 27.2.1 On macOS 27.2.1 (26B131), I can reproduce the following in a Developer ID macOS app: Generate and attest a new App Attest key. Generate assertions successfully, including across separate app launches. Reboot the Mac and log back into the same account. Call generateAssertion with the same key ID: it fails with DeviceCheck error 0. I tested two fresh keys created on this OS version; both worked before reboot and failed afterwards. The app and key IDs were unchanged, and isSupported remained true. System logs show: SecKeyCreateSignature failed CryptoTokenKit Code=-3: unable to sign digest AKSError=-536362989A similar failure with the same signing error is reported here: https://github.com/Layr-Labs/d-inference/issues/1161#issuecomment-5824088914 Their workaround involves generating and attesting replacement keys. Is this a known issue? Is there a supported way to keep existing App Attest keys usable across reboots? Reported through Feedback Assistant: FB25075690
0
0
41
3d
Immediate ASAuthorizationError 1000 for some iOS 27 users — FB25610914
We are investigating intermittent native Sign in with Apple failures in TrueScreen, reported on iOS 27.0–27.2.1. Some production attempts return com.apple.AuthenticationServices.AuthorizationError code 1000 (unknown) approximately 15–18 ms after request start, before a visible authorization sheet or any credential. No underlying NSError is supplied to the app. The affected attempts record an active application, foreground-active scene and visible presentation window. The request uses ASAuthorizationAppleIDProvider with fullName/email scopes and a SHA-256 nonce. Each attempt owns its controller, actual presentation window, nonce and continuation; there is no fallback UIWindow. The native failure precedes our Firebase credential exchange. Other users successfully complete Apple sign-in on iOS 27. We do not know whether the cause is account/device state, App ID configuration, our request, the OS or an Apple service. We are not claiming a confirmed iOS regression. Feedback Assistant report: FB25610914. It includes the implementation checks and evidence limits. Our current staging simulator runs on iOS 27.0/27.2 show the normal prompt to sign in to an Apple Account in Settings, rather than reproducing the immediate production failure. We do not yet have an affected physical-device Accounts/AuthKit-profile sysdiagnose or a reliable minimal reproducer. We reviewed TN3107 and the DTS guidance for Sign in with Apple diagnostics. Which additional checks would distinguish the possible causes of this immediate native 1000? Is this an expected error for some unavailable/restricted Apple Account states, and is there a way to obtain a more actionable native error? We will supplement the Feedback report with an affected-device capture when available.
0
0
41
3d
Credential Provider Extension should allow BE=0, BS=0 for device-bound passkeys
In these threads, it was clarified that Credential Provider Extensions must set both Backup Eligible (BE) and Backup State (BS) flags to 1 in authenticator data: https://developer.apple.com/forums/thread/745605 https://developer.apple.com/forums/thread/787629 However, I'm developing a passkey manager that intentionally stores credentials only on the local device. My implementation uses: kSecAttrAccessibleWhenUnlockedThisDeviceOnly for keychain items kSecAttrTokenIDSecureEnclave for private keys No iCloud sync or backup These credentials are, by definition, single-device credentials. According to the WebAuthn specification, they should be represented with BE=0, BS=0. Currently, I'm forced to set BE=1, BS=1 to make the extension work, which misrepresents the actual backup status to relying parties. This is problematic because: Servers using BE/BS flags for security policies will incorrectly classify these as synced passkeys Users who specifically want device-bound credentials for higher security cannot get accurate flag representation Request: Please allow Credential Provider Extensions to return credentials with BE=0, BS=0 for legitimate device-bound passkey implementations. Environment: macOS 26.2 (25C56), Xcode 26.2 (17C52)
2
5
1.4k
3d
AuthorizationRightSet called from an endpoint security extension fails with -60008
The Mac has managed profiles installed giving the endpoint security process full disk access. Most Macs do not get this error and AuthorizationRightSet works properly. However, one Mac gets the -60008 error and I can't determine the cause. Should an endpoint security extension be able to call AuthorizationRightSet?
1
0
60
3d
Sign in with Apple fails for new users only since Nov 14 ("connection problem"), returning users work
Since November 14, 2026 around 08:57 CET, new users can no longer create an account in our iOS app with Sign in with Apple. Users who have used Sign in with Apple with our app before still sign in normally. What happens New user taps Sign in with Apple → Apple's sheet shows "Verbindungsproblem" (connection problem). The app receives ASAuthorizationError 1000 (unknown); no identity token is returned. Our backend never receives a request. Seen on iOS 26.3 through 27.2, multiple devices and users, all day. What still works Returning users: sign-in works. An existing user who removed our app under Settings → Sign in with Apple and signed in again succeeded, but Apple reused their existing user identifier. So only creating a new identifier seems to fail. What we checked No changes to the App ID, Sign in with Apple capability, Services IDs, keys or entitlements. Same app build created 8 new Sign in with Apple accounts on Nov 13. Membership, agreements, tax and banking all Active. Is anyone else seeing new-user Sign in with Apple failures since Nov 14? Apple folks: is there a known issue with creating new user identifiers? Bundle ID: com.paulschmidt.complete anyone else having this issue
17
14
2k
4d
Sign in with Apple fails with "Cannot Connect" on first sign-up for one app only (other apps on the same team work)
Sign in with Apple fails for one of our iOS apps (bundle ID kr.certlab.app) on the very first sign-up, while other apps from the same developer team work on the same device. Steps Tap "Sign in with Apple" in the app (ASAuthorizationAppleIDProvider, scopes: fullName, email). The Apple sheet appears with name and "Share My Email / Hide My Email". Tap "Continue". Alert: "Cannot Connect — Make sure you are connected to Wi-Fi or cellular network." The request fails with ASAuthorizationError (unknown). The app never appears under Settings > Apple Account > Sign-In & Security > Sign in with Apple, so no link is created. Same iPhone, same Wi-Fi, same Apple Account: Works: four other apps from the same team (including a brand-new first-time sign-up). They use the same Flutter code (sign_in_with_apple) and the same entitlement. Fails: kr.certlab.app only. TestFlight builds 4, 5, 7 and 8 all fail. It has never worked since the first build. What we checked App ID kr.certlab.app has Sign in with Apple enabled as a primary App ID (same setting as the working apps). The App Store provisioning profile and the app's entitlements contain com.apple.developer.applesignin = Default. We removed and re-added the capability, created a new provisioning profile and uploaded a new build. Same result. No Services IDs exist on the team, so there is no web configuration that could conflict. Another app of ours showed the same alert once today and worked on the second try. kr.certlab.app fails every time. Has anyone seen Sign in with Apple fail like this for a single App ID? Is there anything on the App ID or App Store Connect side that can block the first consent? Apple Developer Support case: 30000016304083 / Feedback: FB25591915 Thank you.
0
1
99
4d
First-time Sign in with Apple fails with error 1000 for about 45% of users on iOS 26/27 since Nov 14, returning users unaffected
Since 2026-11-14 00:56 UTC, about 45% of people creating a new account with Sign in with Apple in our App Store app fail. The sheet appears, the user picks Share or Hide My Email and confirms with Face ID, then the delegate gets ASAuthorizationError 1000 with an empty userInfo. Customers report a system "could not connect" alert just before it. What we see: Only first-time authorizations fail. Returning users sign in normally. Only iOS 26.x and 27.x. No failures on iOS 18.x. Same rate in Japan and Thailand, on Wi-Fi and cellular, with either email choice. An affected device fails on almost every attempt, then eventually one attempt succeeds. Unaffected devices succeed first time. 1,340 failed attempts from 376 devices so far. The same build signed in 107 of 111 users in the two days before it started. No app release, App ID change or backend change at the time. System Status shows Sign in with Apple as available. We have not been able to reproduce it on our own devices, so we have no sysdiagnose from a failing device yet. Feedback ID: FB25582932 Is anyone else seeing this since November 14? And could someone from Apple check the server side for our client ID?
1
2
297
5d
First-time Sign in with Apple authorisations suddenly return 1000 after the sheet completes; existing users fine
Our iOS app has used Sign in with Apple (SwiftUI SignInWithAppleButton, scopes .fullName and .email, hashed nonce) for over a year without problems. Since about 04:00 UTC on 14 November 2026, most people authorising the app for the first time fail: they tap the button, the system sheet appears, they complete it (Face ID or passcode), and 6 to 20 seconds after the tap the completion handler receives ASAuthorizationError.unknown (1000). People who have authorised the app before sign in normally. No request reaches our server in the failing case. What we see Before the onset this failure was rare: about one person a week against 15 to 24 first-time sign-ups a day. In the first 12 hours after the onset, 10 people got a result from the sheet. 7 never signed in. 3 did, two of them only on the 3rd and 5th attempt. It affects the current App Store build and the previous one, iOS 26.5 to 26.7, several iPhone models, in Canada, the US, Saudi Arabia, Qatar and Morocco, on Wi-Fi and cellular. This is separate from the immediate 1000 a device with no Apple Account returns. Those arrive within 3 seconds and we excluded them. What we checked Sign In with Apple is enabled on the App ID as a primary App ID. The com.apple.developer.applesignin entitlement is unchanged. Distribution certificates are valid and the membership is active. Nothing in the authorisation request, the button or the completion handler changed between the two builds. We could not reproduce it on our own device after revoking our grant in Settings (Stop Using) and signing in again. One possibly related fact: an updated Apple Developer Program License Agreement was issued on 29 October 2026 and we only accepted it on 14 November, about 12 hours after the failures began. We do not yet know whether the failures stopped after acceptance. Questions Can an unaccepted Program License Agreement degrade Sign in with Apple for first-time users, for example after a grace period? Has anyone else seen first-time authorisations start failing around 14 November 2026 with no change on their side? What should we capture from an affected device to identify the cause, given that we cannot reproduce it ourselves? We have no sysdiagnose from a failing attempt yet. The code-level support form requires a sample project, and this cannot be reproduced in one, so I am asking here. I can share the team ID, bundle ID and UTC timestamps of individual failed attempts privately with an Apple engineer. Update: this looks like the same thing as https://developer.apple.com/forums/thread/857623 (new users only since 14 November, returning users fine, agreements all active there). Our first failure was at 04:07 UTC on 14 November.
0
2
375
6d
How can a macOS app safely extend and independently verify an existing Keychain item’s ACL and partition list?
I’m investigating a macOS Keychain access-control question involving an existing generic-password item and a separately code-signed application. The requirement is to authorize the application to access the existing item while preserving all previously authorized applications, partition-list entries, and other security restrictions. The item must remain in its existing Keychain. Recreating, replacing, or migrating it is not acceptable. My understanding is that legacy trusted-application ACLs and Keychain partition lists can impose separate restrictions, and that modifying one does not necessarily preserve or satisfy the other. I would appreciate clarification on four questions: Is there a supported macOS API for adding one trusted application to an existing generic-password item’s ACL while preserving all other ACL entries and restrictions? Is there a supported API for modifying an existing item’s partition list without replacing or inadvertently broadening its existing authorization policy? After making these changes, is there a supported method to independently enumerate and verify the complete resulting ACL and partition-list policy, rather than relying solely on a successful access attempt? If complete independent verification is not supported, what approach does Apple recommend for safely extending access to an existing Keychain item without weakening its current protections? The goal is a narrowly scoped, auditable authorization change, not a general relaxation of Keychain security. I’m particularly interested in the distinction between what macOS technically permits and what Apple officially supports for production applications. Thank you for any guidance or relevant documentation.
1
0
111
1w
Verifying a stored file-based Keychain trusted-application requirement
I'm evaluating a macOS file-based Keychain ACL that should authorize one application identity, defined by an intended code-signing requirement. The application is a shared Python interpreter; I understand that trusting it does not restrict access to an individual script. I read the related Apple Developer Forums discussion, which explains that complete ACL introspection is not supported and that the stored trusted-application code-signing requirement is accessible through SPI rather than public API. My narrower question is whether there is a supported verification operation that does not require exposing that requirement: Given a SecTrustedApplicationRef obtained through SecACLCopyContents, can a public API establish that its stored caller-matching requirement is no broader than the intended application requirement? Confirming that the intended application is accepted would establish only that it matches, not that additional application identities are excluded. I also don't want to assume that CFEqual against a newly created reference, matching paths, or matching SecTrustedApplicationCopyData results proves equivalent authorization. Apple's documentation describes the CopyData result as opaque. If this comparison is unsupported, what documented provisioning or operating-system enforcement guarantees should an application rely on instead? Is controlled provisioning the intended boundary, or is a different supported Keychain design appropriate? Most importantly, if verifying the exact trusted-application restriction isn't supported, what is Apple's recommended secure approach for allowing a local Python trading application to retrieve Keychain credentials without granting access to every script using the same Python interpreter? A fake-only example using a disposable test Keychain and synthetic generic-password item has been prepared but has not been built or run because full Xcode was unavailable. This is an API-contract question; no runtime failure or ACL attack is claimed, and no assumption is made that published source exactly matches the installed framework.
1
0
85
1w
Sign in with Apple fails with ASAuthorizationError.canceled (1001) / "Sign Up Not Completed" — server-side, all config verified
Our app's Sign in with Apple never completes. Apple's create-account sheet renders fully (name + share/hide-my-email step), then the final server submit fails and shows the "Sign Up Not Completed" sheet. The authorization callback returns ASAuthorizationError.canceled (1001) with no userInfo — even though the user did not cancel. Reproduced on multiple physical devices and multiple Apple IDs (all with 2FA), on iOS 26.5.1, since our first build. Team ID: 24XS837728 App ID: C54N9Q226H (bundle com.sucsessmaperrs.careerAssessmentApp) Verified on our side: com.apple.developer.applesignin = [Default] present in the distribution build (codesign -d --entitlements); embedded profile is the explicit App Store profile for the App ID (not wildcard). App ID has Sign in with Apple enabled as a primary App ID; capability deleted + recreated via the App Store Connect API today, no change. Firebase consumes the identity token; the failure is in Apple's UI before our code runs. App Store Connect agreements are clean. Key isolating fact: the same Apple ID on the same device completes a first-time Sign in with Apple sign-up in other third-party apps — only ours fails. So the cause appears scoped to our App ID / team on Apple's side, not the device, the Apple ID, 2FA, or our client code. This matches the widespread server-side "Sign Up Not Completed" failure in thread 675756 — same signature: multiple devices/Apple IDs, no console error, the failure delegate surfacing only as "cancel", newly created apps affected, even Apple's own sample app failing — which Apple ultimately resolved server-side (with a recurrence reported June 2025). Note this is the native ASAuthorizationController flow, not the REST/web flow, so the query-parameter percent-encoding fix from thread 122458 does not apply here. Could an Apple engineer check the server-side Sign in with Apple / account-association state for App ID C54N9Q226H (Team 24XS837728)? Happy to provide a screen recording or sysdiagnose.
13
0
4.7k
1w
Verifying a stored file-based Keychain trusted-application requirement
I'm evaluating a macOS file-based Keychain ACL that should authorize one application identity, defined by an intended code-signing requirement. The application is a shared Python interpreter; I understand that trusting it does not restrict access to an individual script. I read the related Apple Developer Forums discussion, which explains that complete ACL introspection is not supported and that the stored trusted-application code-signing requirement is accessible through SPI rather than public API. My narrower question is whether there is a supported verification operation that does not require exposing that requirement: Given a SecTrustedApplicationRef obtained through SecACLCopyContents, can a public API establish that its stored caller-matching requirement is no broader than the intended application requirement? Confirming that the intended application is accepted would establish only that it matches, not that additional application identities are excluded. I also don't want to assume that CFEqual against a newly created reference, matching paths, or matching SecTrustedApplicationCopyData results proves equivalent authorization. Apple's documentation describes the CopyData result as opaque. If this comparison is unsupported, what documented provisioning or operating-system enforcement guarantees should an application rely on instead? Is controlled provisioning the intended boundary, or is a different supported Keychain design appropriate? Most importantly, if verifying the exact trusted-application restriction isn't supported, what is Apple's recommended secure approach for allowing a local Python trading application to retrieve Keychain credentials without granting access to every script using the same Python interpreter? A fake-only example using a disposable test Keychain and synthetic generic-password item has been prepared but has not been built or run because full Xcode was unavailable. This is an API-contract question; no runtime failure or ACL attack is claimed, and no assumption is made that published source exactly matches the installed framework.
1
0
80
1w
Is com.apple.security.device.serial supported for new Mac App Store updates?
I’m preparing an update to a native macOS serial logger already distributed through the Mac App Store. The app uses IOSerialBSDClient to enumerate serial ports, opens the selected /dev/cu.* device with open(O_RDWR | O_NOCTTY | O_NONBLOCK), and configures it with termios. On macOS 27.2, open() returns EPERM with App Sandbox enabled and the USB and Bluetooth entitlements present. The same port opens successfully from a process without App Sandbox. I reproduced this with several adapters. Apple’s archived Entitlement Key Reference lists com.apple.security.device.serial and describes adding it manually: https://developer.apple.com/library/archive/documentation/Miscellaneous/Reference/EntitlementKeyReference/Chapters/EnablingAppSandbox.html The macOS 27.2 App Sandbox profile still contains a rule for this entitlement, but I couldn’t find it in the current entitlement documentation or in Xcode 27.2’s Signing & Capabilities editor. Is adding com.apple.security.device.serial manually to the app’s signed entitlements still the supported approach for new Mac App Store updates? Does it require separate approval or provisioning authorization? If this entitlement is no longer supported for Mac App Store submissions, what does Apple recommend for accessing system-provided BSD serial ports with App Sandbox enabled? The app needs to work with ports exposed by both system and third-party drivers and configure them through termios. Would a temporary file access exception for /dev/ be appropriate for this use case?
1
0
150
1w
SFAuthorizationPluginView returns nil at the active-session lock screen (screensaver unlock), non-MDM
What we're trying to do We ship a Developer-ID authorization plugin (a SecurityAgent AuthorizationPlugin bundle exporting AuthorizationPluginCreate, hosting an SFAuthorizationPluginView subclass) that presents custom credential + MFA UI at macOS authentication surfaces — the Jamf Connect / NoMAD / XCreds pattern. This works correctly at the login window (system.login.console). We now want the same custom UI at the active-session lock screen (screensaver unlock), so a managed user can satisfy an MFA step on unlock — without MDM. We understand Platform SSO is the MDM-based path; we're specifically asking about the non-MDM AuthorizationPlugin path, which Cisco Duo and RSA appear to ship on macOS 14/15. Environment macOS Sonoma 14.8.7 and Sequoia 15.7.7 / 15.7.9, Apple Silicon (arm64). Non-MDM. Standard Developer ID distribution, no configuration profiles. Plugin bundle: Developer ID Application + Hardened Runtime (flags=runtime), satisfies its DR, notarized. Bundle has an empty NSPrincipalClass and no NSMainNibFile; construction follows the NameAndPassword DTS sample exactly (alloc the SFAuthorizationPluginView subclass via -initWithCallbacks:andEngineRef: in MechanismInvoke, then -displayView). Reproduction Install the plugin into /Library/Security/SecurityAgentPlugins/. Define a custom right (class = evaluate-mechanisms, mechanisms = [ OurPlugin:invoke ]) — we do not replace the screensaver rule. Append that right to the existing rule, keeping use-login-window-ui: system.login.screensaver (class = rule): rule = [ use-login-window-ui, com.example.screensaver-mfa ] (This "append after use-login-window-ui" arming matches what Cisco Duo's installer does — native password unlock runs first, then the appended mechanism runs in the post-password phase.) Lock, then unlock. What we observe Our mechanism is invoked at unlock (MechanismInvoke runs — so the arming is correct; the modern path otherwise never invokes third-party plugins). But inside MechanismInvoke, on the main thread, in SecurityAgentHelper-arm64: host check: AgentPluginViewHelper = PRESENT // we're in the SecurityAgent GUI host probe: callbacks->version = 4, GetHintValue = <ptr> // engine callbacks, unmodified probe: authorize-right PRESENT rc=0 val=system.login.screensaver presenter alloc'd p = 0x0 (nil = 1) // init returns nil -[SFAuthorizationPluginView initWithCallbacks:andEngineRef:] returns nil. Every downstream symptom we'd chased earlier (black screen, spinner, "ViewBridge … Connection invalid") is just a consequence of there being no view object. What we've ruled out Tracing the construction path (-initWithCallbacks:andEngineRef: → -loadPlugin → [AgentPluginViewHelper loadPluginForRight:engineRef:pluginView:]), we've eliminated: Host process — AgentPluginViewHelper is present; we're in SecurityAgent, not authorizationhost (our UI mechanism is non-privileged). The authorize-right hint — present and correct (system.login.screensaver), read straight through callbacks->GetHintValue. Callbacks / engineRef — valid, version == 4, passed through unmodified (same pointer the engine handed us). The nib — no NSMainNibFile set. The right→product mapping — the right maps to the builtin product, whose plugin object constructs unconditionally. That leaves the display_view re-host step, which appears bound to whether this SecurityAgent instance currently has a live, connection-accepting view-hosting session. Our hypothesis: use-login-window-ui completes the native unlock and tears down its view-hosting session, so our appended mechanism runs after teardown → no live host for display_view → the builtin display mechanism's init fails → SFAuthorizationPluginView init returns nil. The experiment that should have fixed it — but didn't The vendor that ships this (Duo) brackets its non-privileged GUI mechanism with a leading privileged mechanism (and a trailing one). A privileged mechanism runs in authorizationhost; we hypothesized the privileged→non-privileged transition makes authd re-activate SecurityAgent and stand up a fresh view-hosting session before the GUI mechanism runs. We mirrored exactly that: [ OurPlugin:precheck,privileged, OurPlugin:invoke, OurPlugin:complete,privileged ] where precheck/complete are no-op privileged mechanisms that just SetResult(allow). The logs confirm the transition happened: precheck ran in authorizationhosthelper, then invoke ran in a freshly spawned SecurityAgentHelper process (so SecurityAgent did re-activate), with AgentPluginViewHelper present and the hint correct — yet SFAuthorizationPluginView init still returned nil. So replicating the vendor's authorizationdb structure is not sufficient. The remaining difference is either an OS precondition that simply isn't met during a locked-session unlock (the agent isn't accepting view-hosting connections in that context), or something in the vendor's bundle/build (entitlements, embedded XPC/frameworks) rather than the authdb wiring. Questions Is presenting a custom SFAuthorizationPluginView at the active-session lock screen a supported scenario for a non-MDM Developer-ID authorization plugin on macOS 14/15? If yes — what is the supported way to ensure a live view-hosting session exists for a mechanism appended to system.login.screensaver after use-login-window-ui? Is the leading-privileged-mechanism pattern intended, or is there a documented right/API we should use? If SFAuthorizationPluginView init returning nil in this context is expected, please confirm and point us to the sanctioned alternative for custom credential UI at screensaver unlock without MDM. Does any of this differ on Managed vs. non-Managed devices, or depend on SIP / FileVault / Secure Enclave state? References Forums 110667 — use-login-window-ui blocks third-party plugins; legacy path invokes them ("not a bug"). Forums 744211, 771114 — SFAuthorizationPluginView / ViewBridge / viewForType: never called at the lock screen on macOS 15. Feedback FB13238136, FB13128730 — third-party plugin at the lock shield; Data-Protection keychain from screensaver context. Sample code: NameAndPassword — our construction shape matches it exactly. I can provide a minimal reproducer bundle and a sysdiagnose + unified-log capture around a failed unlock on request.
1
0
93
1w
Privacy & Security Resources
General: Forums topic: Privacy & Security Privacy Resources Security Resources Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com"
Replies
0
Boosts
0
Views
1.5k
Activity
Jul ’25
Sign in with Apple: "Sign Up Not Completed" for every App ID in our team — framework returns canceled (1001) with empty userInfo
Sign in with Apple fails for every App ID in our team (K9UFUZF2XW), on every device and every Apple ID we have tried. The system sheet appears, the user authenticates successfully, the sheet then shows "Sign Up Not Completed", and no credential is returned. The failure happens after authentication — this is not a client-side rejection. I have spent several days isolating this and have ruled out everything on my side. Posting the full evidence in case an Apple engineer can look at the server-side state for our team, and in case it helps others hitting the same wall. WHAT THE FRAMEWORK ACTUALLY RETURNS The client library we use (expo-apple-authentication) discards the original NSError, so I patched its native layer to surface the raw error verbatim. This is what ASAuthorizationController hands back to didCompleteWithError, immediately after the user authenticated and the sheet displayed "Sign Up Not Completed": ASAuthorizationError .canceled (rawValue = 1001) domain = com.apple.AuthenticationServices.AuthorizationError code = 1001 desc = The operation couldn't be completed. (com.apple.AuthenticationServices.AuthorizationError, error 1001) userInfo: NSUnderlyingError: So the framework reports a user cancellation that never happened, with a completely empty userInfo and no underlying error. There is no diagnostic information on the client at all — I cannot debug this any further from my side, because the information does not exist there. Note: the same failure surfaces as a different error code depending on the client library version — .unknown (1000) with the older version, .canceled (1001) with the current one. The user-visible behaviour ("Sign Up Not Completed") is identical in both. So the error code is not a reliable signal here. WHAT I RULED OUT Not the App ID. I created a brand-new App ID (kz.auraai.ios) with Sign in with Apple enabled as a primary App ID, built a fresh binary, tested on the same device with the same Apple ID — identical failure. Two independent App IDs in the same team fail the same way. Not the entitlement. Verified inside the signed binary, not just in the portal: application-identifier = K9UFUZF2XW.kz.auraai.ios com.apple.developer.applesignin = ["Default"] I also tried the workaround suggested elsewhere on these forums (removing the entitlement while keeping the capability in the portal). That made it strictly worse: iOS then rejects the request instantly, without showing the sheet at all. Which confirms iOS reads the entitlement correctly, the sheet works, and the user authenticates — the failure is downstream of all of that. No stray or wildcard App IDs. A commonly cited cause is other App IDs in the team lacking the entitlement. I enumerated the whole team via the App Store Connect API: it contains exactly two App IDs, both with APPLE_ID_AUTH = PRIMARY_APP_CONSENT. No wildcard identifiers exist. Not the Apple ID, the device, or the iOS version. The same Apple ID, on the same device, with the same iOS, signs in successfully through another app belonging to a different team (Expo Go, host.exp.Exponent) — a valid identity token is returned. A second, unrelated Apple ID on another device fails in my app in exactly the same way. So this is not scoped to one account: it affects every user of the app. Agreements and membership are in good standing. Program License Agreement accepted 30 June 2026; Developer Agreement accepted 26 June 2026; membership active. Both distribution types fail. TestFlight and ad-hoc. WHAT IS LEFT After all of the above, the only variable that differs between the working case (a different team's app, same device, same Apple ID) and the failing case (my app) is the Apple Developer team itself. This exact signature — sheet renders fully, final server submit fails, "Sign Up Not Completed", delegate reports canceled with no userInfo, not reproducible in other apps on the same device — is documented in thread 122458 ("Error: Sign-Up Not Completed"). In that case it affected multiple developers, including Apple's own sample app, and was ultimately resolved by Apple on the server side, with a recurrence reported in June 2025. THE ASK Could someone from Apple check the server-side Sign in with Apple registration for team K9UFUZF2XW (App IDs kz.auraai.app and kz.auraai.ios)? I am not looking for configuration advice — I have exhausted the client side and there is nothing left to configure. This looks like the same server-side state that was fixed in the referenced cases. Feedback Assistant: FB23716661 (includes sysdiagnose with the Accounts/AuthKit profile, timestamp, and video of the failure). This is currently blocking us: because Sign in with Apple works for none of our users, guideline 4.8 prevents us from offering Google Sign-In, so we are shipping with email-only login. Happy to provide the binary, entitlements dump, or a fresh sysdiagnose on request.
Replies
137
Boosts
6
Views
34k
Activity
9h
Reading Mouse Events with CGEvent tap from a background app in macOS 27.3
WIth macOS 27.3 (beta 2) things have changed quite a bit for security, see Updates to Device Control and Data Access, and Full Disk Access in macOS I have an app which uses what (used to be called) the Privacy & Security / Accessibility permissions in order to receive mouse events in the background to read them and occasionally modify them. The method used: The app checks AXIsProcessTrustedWithOptions to see if it has permission. If it doesn't have permission, it uses the kAXTrustedCheckOptionPrompt option which would open up the privacy & Security / Accessibility pane. Because that process has been a little flakey in macOS, my app has a backup option, where it runs 'open "x-apple.systempreferences:com.apple.settings.PrivacySecurity.extension?Privacy_Accessibility"' and then walks the user through the steps with onscreen instructions. When permission is granted, the app creates a CGEvent tap SessionEvent tap using the HeadInsertEvent option to receive mouse and touch mouse events. See CGEvent.tapCreate In macOS 27.3 beta 2, always returns false using kAXTrustedCheckOptionPrompt fails to do anything open "x-apple.systempreferences:com.apple.settings.PrivacySecurity.extension?Privacy_Accessibility fails to do anything. CGEvent tap fails A few questions: will my third party app be allowed to use CGEventTaps to read mouse and touchpad events? Or has this been cut off completely and only available to first party apps? If it is allowed, how? Has the permission for this moved to a different System Preference pane? is a CGEvent tap the way to do it? I totally understand that security is important, and apps should not have wide-ranging permissions. I'd love to find a way to keep my app running with the minimal permissions needed.
Replies
5
Boosts
0
Views
491
Activity
10h
ATT prompt not shown and status stays notDetermined: how do you handle it?
Hello, our Unity game (iOS/iPadOS) requests App Tracking Transparency on its first scene, before ads are initialized. Background App Review rejected an earlier build under Guideline 2.1(a) for a blank screen on iPad Air 11-inch (M3), iPadOS 27.0. In that build we called requestTrackingAuthorization right at launch and then waited until trackingAuthorizationStatus was no longer .notDetermined. The status never changed, so the app never left the first screen. Current flow (this build was approved) Wait until UIApplication.shared.applicationState == .active and the app has focus. Call requestTrackingAuthorization(completionHandler:) once and wait for the completion handler. If the completion returns .notDetermined, wait about 4 seconds while the app stays active, then call it one more time. Wait until the status is no longer .notDetermined before loading the next scene. There is no timeout. The first scene runs on every cold launch, so if the status is still .notDetermined, the request is made again on the next launch. [ATTrackingManager requestTrackingAuthorizationWithCompletionHandler:^(ATTrackingManagerAuthorizationStatus status) { dispatch_async(dispatch_get_main_queue(), ^{ // store status; Unity polls it on the main thread }); }];We have not been able to reproduce the original problem on our own devices. Questions for those who have shipped apps with ATT How many times do you retry requestTrackingAuthorization, and how long do you wait between attempts? Is there any limit you know of? If the status still stays .notDetermined after retrying, do you let the user continue and treat it as not authorized (no IDFA), or keep waiting? If you wait, how long before you let the user continue? If you continue without tracking, did App Review ever flag that? Any experience or pointers to documentation would be appreciated.
Replies
0
Boosts
0
Views
18
Activity
10h
macOS 27: Accessibility granted via MDM doesn’t cover PostEvent, and leaves a stray TCC managed_overrides row after unenrollment
Our app uses an active CGEventTap (kCGEventTapOptionDefault, mouse down/up events) and relies on the Accessibility permission (Device Control & Data Access). CGEventTapCreate(kCGAnnotatedSessionEventTap, kCGHeadInsertEventTap, kCGEventTapOptionDefault, CGEventMaskBit(kCGEventLeftMouseDown) | CGEventMaskBit(kCGEventLeftMouseUp) | CGEventMaskBit(kCGEventRightMouseDown) | CGEventMaskBit(kCGEventRightMouseUp) | CGEventMaskBit(kCGEventOtherMouseDown) | CGEventMaskBit(kCGEventOtherMouseUp), callback, refcon);On macOS 27.0.1 we see two behaviours when that permission comes from MDM, and we’d like to know whether they’re expected. According to the PrivacyPreferencesPolicyControl.Services documentation, the PPPC Accessibility key is deprecated in macOS 27. It’s replaced by the Privacy → PermissionDefaults setting in the declarative configuration com.apple.configuration.app.settings, and the managed value is a default that the user can change. We tested both the PPPC payload and the DDM configuration. 1. Managed Accessibility grant doesn’t cover PostEvent When the user turns on Accessibility manually in System Settings > Privacy & Security > Accessibility, the event tap works with no further prompts. When Accessibility comes from device management (a PPPC payload or DDM PermissionDefaults): AXIsProcessTrusted() returns true. On the first click through the tap, macOS shows the “control this computer” prompt. tccd adds an access row for kTCCServicePostEvent with auth_value 0 and auth_reason 4. At the same moment, the app’s Accessibility toggle in System Settings switches off. The managed Accessibility row remains auth_value 2, auth_reason 6. After the user accepts the prompt, PostEvent changes to auth_value 2 and the tap works from then on. Questions : Why does a manual Accessibility grant cover an active event tap, while a managed Accessibility default needs a separate PostEvent grant? With PPPC Accessibility deprecated, is DDM Accessibility plus PPPC PostEvent (Allowed) the intended configuration for apps that install active event taps? 2. Stray managed_overrides row after unenrollment On macOS 27, the managed Accessibility value is stored in a new managed_overrides table in /Library/Application Support/com.apple.TCC/TCC.db (schema version 36). On macOS 15 and 26, managed grants were kept in MDMOverrides.plist, and this table doesn’t exist there. Steps : Enroll a never-managed Mac in MDM with user-approved enrollment. Install a profile that grants Accessibility to our app. tccd logs ManagedSettings: inserted managed_overrides for kTCCServiceAccessibility:<bundle id> admin_auth_value=2 auth_value=2. The row is written with policy_id NULL, and policies and active_policy stay empty. Remove the MDM profile from System Settings > General > Device Management. What happens: mdmclient removes the MDM profile first. Removing each TCC payload after that fails with : PlugIn: DetermineUninstallFlags [TCCProfileService] Error: Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied" UserInfo={NSLocalizedDescription=The profile must originate from a user-approved MDM server.}The profiles disappear, MDMOverrides.plist is deleted, and profiles status reports no MDM enrollment. The row remains, with auth_value 1, auth_reason 6 (MDM Policy), policy_id NULL, admin_auth_value 2 and flags 480. tccutil reset Accessibility <bundle id> clears flags but doesn’t remove the row. Later permission prompts and System Settings toggles for the app write to this row instead of to access. Why does the row stay after unenrollment? Is there a supported way to clear it?
Replies
2
Boosts
1
Views
217
Activity
11h
No lifecycle notification when entering App Switcher while app remains inactive after Face ID
We use LAContext.evaluatePolicy(.deviceOwnerAuthentication) for a local app lock. On an iPhone 16 Pro running iOS 26.6.2, after authentication succeeds, UIApplication.shared.applicationState can remain .inactive for approximately 2–8 seconds although the app UI is visible. If the user enters the App Switcher during this interval, the app receives no additional willResignActive or didEnterBackground notification. Returning to the app produces only didBecomeActive. This means the app cannot distinguish between: remaining in the app while the Face ID UI finishes dismissing; and entering the App Switcher and returning during the same inactive interval. Reproduction: Run a minimal UIKit app on a physical Face ID device. Call evaluatePolicy(.deviceOwnerAuthentication). Immediately after successful authentication, enter the App Switcher before didBecomeActive. Wait three seconds and return. Is there a supported public API or lifecycle pattern that lets an app lock immediately in this situation without keeping its content covered until didBecomeActive?
Replies
1
Boosts
0
Views
37
Activity
12h
App Attest keys stop working after reboot on macOS 27.2.1
App Attest keys stop working after reboot on macOS 27.2.1 On macOS 27.2.1 (26B131), I can reproduce the following in a Developer ID macOS app: Generate and attest a new App Attest key. Generate assertions successfully, including across separate app launches. Reboot the Mac and log back into the same account. Call generateAssertion with the same key ID: it fails with DeviceCheck error 0. I tested two fresh keys created on this OS version; both worked before reboot and failed afterwards. The app and key IDs were unchanged, and isSupported remained true. System logs show: SecKeyCreateSignature failed CryptoTokenKit Code=-3: unable to sign digest AKSError=-536362989A similar failure with the same signing error is reported here: https://github.com/Layr-Labs/d-inference/issues/1161#issuecomment-5824088914 Their workaround involves generating and attesting replacement keys. Is this a known issue? Is there a supported way to keep existing App Attest keys usable across reboots? Reported through Feedback Assistant: FB25075690
Replies
0
Boosts
0
Views
41
Activity
3d
Immediate ASAuthorizationError 1000 for some iOS 27 users — FB25610914
We are investigating intermittent native Sign in with Apple failures in TrueScreen, reported on iOS 27.0–27.2.1. Some production attempts return com.apple.AuthenticationServices.AuthorizationError code 1000 (unknown) approximately 15–18 ms after request start, before a visible authorization sheet or any credential. No underlying NSError is supplied to the app. The affected attempts record an active application, foreground-active scene and visible presentation window. The request uses ASAuthorizationAppleIDProvider with fullName/email scopes and a SHA-256 nonce. Each attempt owns its controller, actual presentation window, nonce and continuation; there is no fallback UIWindow. The native failure precedes our Firebase credential exchange. Other users successfully complete Apple sign-in on iOS 27. We do not know whether the cause is account/device state, App ID configuration, our request, the OS or an Apple service. We are not claiming a confirmed iOS regression. Feedback Assistant report: FB25610914. It includes the implementation checks and evidence limits. Our current staging simulator runs on iOS 27.0/27.2 show the normal prompt to sign in to an Apple Account in Settings, rather than reproducing the immediate production failure. We do not yet have an affected physical-device Accounts/AuthKit-profile sysdiagnose or a reliable minimal reproducer. We reviewed TN3107 and the DTS guidance for Sign in with Apple diagnostics. Which additional checks would distinguish the possible causes of this immediate native 1000? Is this an expected error for some unavailable/restricted Apple Account states, and is there a way to obtain a more actionable native error? We will supplement the Feedback report with an affected-device capture when available.
Replies
0
Boosts
0
Views
41
Activity
3d
Credential Provider Extension should allow BE=0, BS=0 for device-bound passkeys
In these threads, it was clarified that Credential Provider Extensions must set both Backup Eligible (BE) and Backup State (BS) flags to 1 in authenticator data: https://developer.apple.com/forums/thread/745605 https://developer.apple.com/forums/thread/787629 However, I'm developing a passkey manager that intentionally stores credentials only on the local device. My implementation uses: kSecAttrAccessibleWhenUnlockedThisDeviceOnly for keychain items kSecAttrTokenIDSecureEnclave for private keys No iCloud sync or backup These credentials are, by definition, single-device credentials. According to the WebAuthn specification, they should be represented with BE=0, BS=0. Currently, I'm forced to set BE=1, BS=1 to make the extension work, which misrepresents the actual backup status to relying parties. This is problematic because: Servers using BE/BS flags for security policies will incorrectly classify these as synced passkeys Users who specifically want device-bound credentials for higher security cannot get accurate flag representation Request: Please allow Credential Provider Extensions to return credentials with BE=0, BS=0 for legitimate device-bound passkey implementations. Environment: macOS 26.2 (25C56), Xcode 26.2 (17C52)
Replies
2
Boosts
5
Views
1.4k
Activity
3d
AuthorizationRightSet called from an endpoint security extension fails with -60008
The Mac has managed profiles installed giving the endpoint security process full disk access. Most Macs do not get this error and AuthorizationRightSet works properly. However, one Mac gets the -60008 error and I can't determine the cause. Should an endpoint security extension be able to call AuthorizationRightSet?
Replies
1
Boosts
0
Views
60
Activity
3d
Sign in with Apple fails for new users only since Nov 14 ("connection problem"), returning users work
Since November 14, 2026 around 08:57 CET, new users can no longer create an account in our iOS app with Sign in with Apple. Users who have used Sign in with Apple with our app before still sign in normally. What happens New user taps Sign in with Apple → Apple's sheet shows "Verbindungsproblem" (connection problem). The app receives ASAuthorizationError 1000 (unknown); no identity token is returned. Our backend never receives a request. Seen on iOS 26.3 through 27.2, multiple devices and users, all day. What still works Returning users: sign-in works. An existing user who removed our app under Settings → Sign in with Apple and signed in again succeeded, but Apple reused their existing user identifier. So only creating a new identifier seems to fail. What we checked No changes to the App ID, Sign in with Apple capability, Services IDs, keys or entitlements. Same app build created 8 new Sign in with Apple accounts on Nov 13. Membership, agreements, tax and banking all Active. Is anyone else seeing new-user Sign in with Apple failures since Nov 14? Apple folks: is there a known issue with creating new user identifiers? Bundle ID: com.paulschmidt.complete anyone else having this issue
Replies
17
Boosts
14
Views
2k
Activity
4d
Sign in with Apple fails with "Cannot Connect" on first sign-up for one app only (other apps on the same team work)
Sign in with Apple fails for one of our iOS apps (bundle ID kr.certlab.app) on the very first sign-up, while other apps from the same developer team work on the same device. Steps Tap "Sign in with Apple" in the app (ASAuthorizationAppleIDProvider, scopes: fullName, email). The Apple sheet appears with name and "Share My Email / Hide My Email". Tap "Continue". Alert: "Cannot Connect — Make sure you are connected to Wi-Fi or cellular network." The request fails with ASAuthorizationError (unknown). The app never appears under Settings > Apple Account > Sign-In & Security > Sign in with Apple, so no link is created. Same iPhone, same Wi-Fi, same Apple Account: Works: four other apps from the same team (including a brand-new first-time sign-up). They use the same Flutter code (sign_in_with_apple) and the same entitlement. Fails: kr.certlab.app only. TestFlight builds 4, 5, 7 and 8 all fail. It has never worked since the first build. What we checked App ID kr.certlab.app has Sign in with Apple enabled as a primary App ID (same setting as the working apps). The App Store provisioning profile and the app's entitlements contain com.apple.developer.applesignin = Default. We removed and re-added the capability, created a new provisioning profile and uploaded a new build. Same result. No Services IDs exist on the team, so there is no web configuration that could conflict. Another app of ours showed the same alert once today and worked on the second try. kr.certlab.app fails every time. Has anyone seen Sign in with Apple fail like this for a single App ID? Is there anything on the App ID or App Store Connect side that can block the first consent? Apple Developer Support case: 30000016304083 / Feedback: FB25591915 Thank you.
Replies
0
Boosts
1
Views
99
Activity
4d
First-time Sign in with Apple fails with error 1000 for about 45% of users on iOS 26/27 since Nov 14, returning users unaffected
Since 2026-11-14 00:56 UTC, about 45% of people creating a new account with Sign in with Apple in our App Store app fail. The sheet appears, the user picks Share or Hide My Email and confirms with Face ID, then the delegate gets ASAuthorizationError 1000 with an empty userInfo. Customers report a system "could not connect" alert just before it. What we see: Only first-time authorizations fail. Returning users sign in normally. Only iOS 26.x and 27.x. No failures on iOS 18.x. Same rate in Japan and Thailand, on Wi-Fi and cellular, with either email choice. An affected device fails on almost every attempt, then eventually one attempt succeeds. Unaffected devices succeed first time. 1,340 failed attempts from 376 devices so far. The same build signed in 107 of 111 users in the two days before it started. No app release, App ID change or backend change at the time. System Status shows Sign in with Apple as available. We have not been able to reproduce it on our own devices, so we have no sysdiagnose from a failing device yet. Feedback ID: FB25582932 Is anyone else seeing this since November 14? And could someone from Apple check the server side for our client ID?
Replies
1
Boosts
2
Views
297
Activity
5d
First-time Sign in with Apple authorisations suddenly return 1000 after the sheet completes; existing users fine
Our iOS app has used Sign in with Apple (SwiftUI SignInWithAppleButton, scopes .fullName and .email, hashed nonce) for over a year without problems. Since about 04:00 UTC on 14 November 2026, most people authorising the app for the first time fail: they tap the button, the system sheet appears, they complete it (Face ID or passcode), and 6 to 20 seconds after the tap the completion handler receives ASAuthorizationError.unknown (1000). People who have authorised the app before sign in normally. No request reaches our server in the failing case. What we see Before the onset this failure was rare: about one person a week against 15 to 24 first-time sign-ups a day. In the first 12 hours after the onset, 10 people got a result from the sheet. 7 never signed in. 3 did, two of them only on the 3rd and 5th attempt. It affects the current App Store build and the previous one, iOS 26.5 to 26.7, several iPhone models, in Canada, the US, Saudi Arabia, Qatar and Morocco, on Wi-Fi and cellular. This is separate from the immediate 1000 a device with no Apple Account returns. Those arrive within 3 seconds and we excluded them. What we checked Sign In with Apple is enabled on the App ID as a primary App ID. The com.apple.developer.applesignin entitlement is unchanged. Distribution certificates are valid and the membership is active. Nothing in the authorisation request, the button or the completion handler changed between the two builds. We could not reproduce it on our own device after revoking our grant in Settings (Stop Using) and signing in again. One possibly related fact: an updated Apple Developer Program License Agreement was issued on 29 October 2026 and we only accepted it on 14 November, about 12 hours after the failures began. We do not yet know whether the failures stopped after acceptance. Questions Can an unaccepted Program License Agreement degrade Sign in with Apple for first-time users, for example after a grace period? Has anyone else seen first-time authorisations start failing around 14 November 2026 with no change on their side? What should we capture from an affected device to identify the cause, given that we cannot reproduce it ourselves? We have no sysdiagnose from a failing attempt yet. The code-level support form requires a sample project, and this cannot be reproduced in one, so I am asking here. I can share the team ID, bundle ID and UTC timestamps of individual failed attempts privately with an Apple engineer. Update: this looks like the same thing as https://developer.apple.com/forums/thread/857623 (new users only since 14 November, returning users fine, agreements all active there). Our first failure was at 04:07 UTC on 14 November.
Replies
0
Boosts
2
Views
375
Activity
6d
How can a macOS app safely extend and independently verify an existing Keychain item’s ACL and partition list?
I’m investigating a macOS Keychain access-control question involving an existing generic-password item and a separately code-signed application. The requirement is to authorize the application to access the existing item while preserving all previously authorized applications, partition-list entries, and other security restrictions. The item must remain in its existing Keychain. Recreating, replacing, or migrating it is not acceptable. My understanding is that legacy trusted-application ACLs and Keychain partition lists can impose separate restrictions, and that modifying one does not necessarily preserve or satisfy the other. I would appreciate clarification on four questions: Is there a supported macOS API for adding one trusted application to an existing generic-password item’s ACL while preserving all other ACL entries and restrictions? Is there a supported API for modifying an existing item’s partition list without replacing or inadvertently broadening its existing authorization policy? After making these changes, is there a supported method to independently enumerate and verify the complete resulting ACL and partition-list policy, rather than relying solely on a successful access attempt? If complete independent verification is not supported, what approach does Apple recommend for safely extending access to an existing Keychain item without weakening its current protections? The goal is a narrowly scoped, auditable authorization change, not a general relaxation of Keychain security. I’m particularly interested in the distinction between what macOS technically permits and what Apple officially supports for production applications. Thank you for any guidance or relevant documentation.
Replies
1
Boosts
0
Views
111
Activity
1w
Verifying a stored file-based Keychain trusted-application requirement
I'm evaluating a macOS file-based Keychain ACL that should authorize one application identity, defined by an intended code-signing requirement. The application is a shared Python interpreter; I understand that trusting it does not restrict access to an individual script. I read the related Apple Developer Forums discussion, which explains that complete ACL introspection is not supported and that the stored trusted-application code-signing requirement is accessible through SPI rather than public API. My narrower question is whether there is a supported verification operation that does not require exposing that requirement: Given a SecTrustedApplicationRef obtained through SecACLCopyContents, can a public API establish that its stored caller-matching requirement is no broader than the intended application requirement? Confirming that the intended application is accepted would establish only that it matches, not that additional application identities are excluded. I also don't want to assume that CFEqual against a newly created reference, matching paths, or matching SecTrustedApplicationCopyData results proves equivalent authorization. Apple's documentation describes the CopyData result as opaque. If this comparison is unsupported, what documented provisioning or operating-system enforcement guarantees should an application rely on instead? Is controlled provisioning the intended boundary, or is a different supported Keychain design appropriate? Most importantly, if verifying the exact trusted-application restriction isn't supported, what is Apple's recommended secure approach for allowing a local Python trading application to retrieve Keychain credentials without granting access to every script using the same Python interpreter? A fake-only example using a disposable test Keychain and synthetic generic-password item has been prepared but has not been built or run because full Xcode was unavailable. This is an API-contract question; no runtime failure or ACL attack is claimed, and no assumption is made that published source exactly matches the installed framework.
Replies
1
Boosts
0
Views
85
Activity
1w
Sign in with Apple fails with ASAuthorizationError.canceled (1001) / "Sign Up Not Completed" — server-side, all config verified
Our app's Sign in with Apple never completes. Apple's create-account sheet renders fully (name + share/hide-my-email step), then the final server submit fails and shows the "Sign Up Not Completed" sheet. The authorization callback returns ASAuthorizationError.canceled (1001) with no userInfo — even though the user did not cancel. Reproduced on multiple physical devices and multiple Apple IDs (all with 2FA), on iOS 26.5.1, since our first build. Team ID: 24XS837728 App ID: C54N9Q226H (bundle com.sucsessmaperrs.careerAssessmentApp) Verified on our side: com.apple.developer.applesignin = [Default] present in the distribution build (codesign -d --entitlements); embedded profile is the explicit App Store profile for the App ID (not wildcard). App ID has Sign in with Apple enabled as a primary App ID; capability deleted + recreated via the App Store Connect API today, no change. Firebase consumes the identity token; the failure is in Apple's UI before our code runs. App Store Connect agreements are clean. Key isolating fact: the same Apple ID on the same device completes a first-time Sign in with Apple sign-up in other third-party apps — only ours fails. So the cause appears scoped to our App ID / team on Apple's side, not the device, the Apple ID, 2FA, or our client code. This matches the widespread server-side "Sign Up Not Completed" failure in thread 675756 — same signature: multiple devices/Apple IDs, no console error, the failure delegate surfacing only as "cancel", newly created apps affected, even Apple's own sample app failing — which Apple ultimately resolved server-side (with a recurrence reported June 2025). Note this is the native ASAuthorizationController flow, not the REST/web flow, so the query-parameter percent-encoding fix from thread 122458 does not apply here. Could an Apple engineer check the server-side Sign in with Apple / account-association state for App ID C54N9Q226H (Team 24XS837728)? Happy to provide a screen recording or sysdiagnose.
Replies
13
Boosts
0
Views
4.7k
Activity
1w
Verifying a stored file-based Keychain trusted-application requirement
I'm evaluating a macOS file-based Keychain ACL that should authorize one application identity, defined by an intended code-signing requirement. The application is a shared Python interpreter; I understand that trusting it does not restrict access to an individual script. I read the related Apple Developer Forums discussion, which explains that complete ACL introspection is not supported and that the stored trusted-application code-signing requirement is accessible through SPI rather than public API. My narrower question is whether there is a supported verification operation that does not require exposing that requirement: Given a SecTrustedApplicationRef obtained through SecACLCopyContents, can a public API establish that its stored caller-matching requirement is no broader than the intended application requirement? Confirming that the intended application is accepted would establish only that it matches, not that additional application identities are excluded. I also don't want to assume that CFEqual against a newly created reference, matching paths, or matching SecTrustedApplicationCopyData results proves equivalent authorization. Apple's documentation describes the CopyData result as opaque. If this comparison is unsupported, what documented provisioning or operating-system enforcement guarantees should an application rely on instead? Is controlled provisioning the intended boundary, or is a different supported Keychain design appropriate? Most importantly, if verifying the exact trusted-application restriction isn't supported, what is Apple's recommended secure approach for allowing a local Python trading application to retrieve Keychain credentials without granting access to every script using the same Python interpreter? A fake-only example using a disposable test Keychain and synthetic generic-password item has been prepared but has not been built or run because full Xcode was unavailable. This is an API-contract question; no runtime failure or ACL attack is claimed, and no assumption is made that published source exactly matches the installed framework.
Replies
1
Boosts
0
Views
80
Activity
1w
Is com.apple.security.device.serial supported for new Mac App Store updates?
I’m preparing an update to a native macOS serial logger already distributed through the Mac App Store. The app uses IOSerialBSDClient to enumerate serial ports, opens the selected /dev/cu.* device with open(O_RDWR | O_NOCTTY | O_NONBLOCK), and configures it with termios. On macOS 27.2, open() returns EPERM with App Sandbox enabled and the USB and Bluetooth entitlements present. The same port opens successfully from a process without App Sandbox. I reproduced this with several adapters. Apple’s archived Entitlement Key Reference lists com.apple.security.device.serial and describes adding it manually: https://developer.apple.com/library/archive/documentation/Miscellaneous/Reference/EntitlementKeyReference/Chapters/EnablingAppSandbox.html The macOS 27.2 App Sandbox profile still contains a rule for this entitlement, but I couldn’t find it in the current entitlement documentation or in Xcode 27.2’s Signing & Capabilities editor. Is adding com.apple.security.device.serial manually to the app’s signed entitlements still the supported approach for new Mac App Store updates? Does it require separate approval or provisioning authorization? If this entitlement is no longer supported for Mac App Store submissions, what does Apple recommend for accessing system-provided BSD serial ports with App Sandbox enabled? The app needs to work with ports exposed by both system and third-party drivers and configure them through termios. Would a temporary file access exception for /dev/ be appropriate for this use case?
Replies
1
Boosts
0
Views
150
Activity
1w
SFAuthorizationPluginView returns nil at the active-session lock screen (screensaver unlock), non-MDM
What we're trying to do We ship a Developer-ID authorization plugin (a SecurityAgent AuthorizationPlugin bundle exporting AuthorizationPluginCreate, hosting an SFAuthorizationPluginView subclass) that presents custom credential + MFA UI at macOS authentication surfaces — the Jamf Connect / NoMAD / XCreds pattern. This works correctly at the login window (system.login.console). We now want the same custom UI at the active-session lock screen (screensaver unlock), so a managed user can satisfy an MFA step on unlock — without MDM. We understand Platform SSO is the MDM-based path; we're specifically asking about the non-MDM AuthorizationPlugin path, which Cisco Duo and RSA appear to ship on macOS 14/15. Environment macOS Sonoma 14.8.7 and Sequoia 15.7.7 / 15.7.9, Apple Silicon (arm64). Non-MDM. Standard Developer ID distribution, no configuration profiles. Plugin bundle: Developer ID Application + Hardened Runtime (flags=runtime), satisfies its DR, notarized. Bundle has an empty NSPrincipalClass and no NSMainNibFile; construction follows the NameAndPassword DTS sample exactly (alloc the SFAuthorizationPluginView subclass via -initWithCallbacks:andEngineRef: in MechanismInvoke, then -displayView). Reproduction Install the plugin into /Library/Security/SecurityAgentPlugins/. Define a custom right (class = evaluate-mechanisms, mechanisms = [ OurPlugin:invoke ]) — we do not replace the screensaver rule. Append that right to the existing rule, keeping use-login-window-ui: system.login.screensaver (class = rule): rule = [ use-login-window-ui, com.example.screensaver-mfa ] (This "append after use-login-window-ui" arming matches what Cisco Duo's installer does — native password unlock runs first, then the appended mechanism runs in the post-password phase.) Lock, then unlock. What we observe Our mechanism is invoked at unlock (MechanismInvoke runs — so the arming is correct; the modern path otherwise never invokes third-party plugins). But inside MechanismInvoke, on the main thread, in SecurityAgentHelper-arm64: host check: AgentPluginViewHelper = PRESENT // we're in the SecurityAgent GUI host probe: callbacks->version = 4, GetHintValue = <ptr> // engine callbacks, unmodified probe: authorize-right PRESENT rc=0 val=system.login.screensaver presenter alloc'd p = 0x0 (nil = 1) // init returns nil -[SFAuthorizationPluginView initWithCallbacks:andEngineRef:] returns nil. Every downstream symptom we'd chased earlier (black screen, spinner, "ViewBridge … Connection invalid") is just a consequence of there being no view object. What we've ruled out Tracing the construction path (-initWithCallbacks:andEngineRef: → -loadPlugin → [AgentPluginViewHelper loadPluginForRight:engineRef:pluginView:]), we've eliminated: Host process — AgentPluginViewHelper is present; we're in SecurityAgent, not authorizationhost (our UI mechanism is non-privileged). The authorize-right hint — present and correct (system.login.screensaver), read straight through callbacks->GetHintValue. Callbacks / engineRef — valid, version == 4, passed through unmodified (same pointer the engine handed us). The nib — no NSMainNibFile set. The right→product mapping — the right maps to the builtin product, whose plugin object constructs unconditionally. That leaves the display_view re-host step, which appears bound to whether this SecurityAgent instance currently has a live, connection-accepting view-hosting session. Our hypothesis: use-login-window-ui completes the native unlock and tears down its view-hosting session, so our appended mechanism runs after teardown → no live host for display_view → the builtin display mechanism's init fails → SFAuthorizationPluginView init returns nil. The experiment that should have fixed it — but didn't The vendor that ships this (Duo) brackets its non-privileged GUI mechanism with a leading privileged mechanism (and a trailing one). A privileged mechanism runs in authorizationhost; we hypothesized the privileged→non-privileged transition makes authd re-activate SecurityAgent and stand up a fresh view-hosting session before the GUI mechanism runs. We mirrored exactly that: [ OurPlugin:precheck,privileged, OurPlugin:invoke, OurPlugin:complete,privileged ] where precheck/complete are no-op privileged mechanisms that just SetResult(allow). The logs confirm the transition happened: precheck ran in authorizationhosthelper, then invoke ran in a freshly spawned SecurityAgentHelper process (so SecurityAgent did re-activate), with AgentPluginViewHelper present and the hint correct — yet SFAuthorizationPluginView init still returned nil. So replicating the vendor's authorizationdb structure is not sufficient. The remaining difference is either an OS precondition that simply isn't met during a locked-session unlock (the agent isn't accepting view-hosting connections in that context), or something in the vendor's bundle/build (entitlements, embedded XPC/frameworks) rather than the authdb wiring. Questions Is presenting a custom SFAuthorizationPluginView at the active-session lock screen a supported scenario for a non-MDM Developer-ID authorization plugin on macOS 14/15? If yes — what is the supported way to ensure a live view-hosting session exists for a mechanism appended to system.login.screensaver after use-login-window-ui? Is the leading-privileged-mechanism pattern intended, or is there a documented right/API we should use? If SFAuthorizationPluginView init returning nil in this context is expected, please confirm and point us to the sanctioned alternative for custom credential UI at screensaver unlock without MDM. Does any of this differ on Managed vs. non-Managed devices, or depend on SIP / FileVault / Secure Enclave state? References Forums 110667 — use-login-window-ui blocks third-party plugins; legacy path invokes them ("not a bug"). Forums 744211, 771114 — SFAuthorizationPluginView / ViewBridge / viewForType: never called at the lock screen on macOS 15. Feedback FB13238136, FB13128730 — third-party plugin at the lock shield; Data-Protection keychain from screensaver context. Sample code: NameAndPassword — our construction shape matches it exactly. I can provide a minimal reproducer bundle and a sysdiagnose + unified-log capture around a failed unlock on request.
Replies
1
Boosts
0
Views
93
Activity
1w