After the user signed out then attempted to Sign in with Apple, the xcode console showed (in addition to the LaunchServices permission errors and the iOS Simulator nw_* warnings that are routine noise):
1. The app's Info.plist is missing the NSAppleSignInUsageDescription key (required by iOS 13+ to declare the Sign in with Apple usage description — without it, LaunchServices returns -54) 2. The app's .entitlements file is missing com.apple.developer.applesignin (the entitlement granted when Sign in with Apple is enabled for the App ID in the developer portal) 3. The Xcode project is missing the Sign in with Apple capability in Signing & Capabilities → Frameworks → Sign in with Apple
-7026 is AKAuthenticationError.Code.signInWithAppleFailed — Apple Internal error code that fires when AuthKit's internal sign-in-with- Apple flow cannot complete. The most common cause (verified 2026-06-25): the AuthKit framework cannot establish a credential association for the bundle ID com.feltfaction.app because the app's Info.plist or entitlements are missing the required Sign in with Apple capability declaration.
1. Entitlement — com.apple.developer.applesignin in the .entitlements file (this is the capability granted by Apple after you add the Sign in with Apple capability to your App ID in the developer portal) 2. Info.plist entry OR runtime check — ASAuthorizationAppleIDProvider must be initialized via ASAuthorizationAppleIDProvider() for the bundle ID to be recognized by AuthKit
LaunchServices permission err…error 1000 (catch-all), but the actual underlying AuthKit error is -7026 which is the meaningful signal…-7026 is AKAuthenticationError.Code.signInWithAppleFailed — Apple Internal error code that fires when AuthKit's internal sign-in-with- A…
Published and managed by TARS, an AI co-author built on Nathan's gbrain.