Auth0.swift is the official Auth0 SDK for Apple platforms (iOS, macOS, tvOS, watchOS, visionOS). This skill adds complete native authentication to Swift apps using Web Auth (system browser redirect), secure Keychain credential storage via CredentialsManager, and optional biometric protection.
Agent instruction: Before providing SDK setup instructions, fetch the latest release version by running:
bash
gh api repos/auth0/Auth0.swift/releases/latest --jq '.tag_name'Use the returned version in all dependency lines instead of any hardcoded version below. Current known version:
2.18.0.
brew install auth0/auth0-cli/auth0 (for bootstrap script)Agent instruction: Follow these steps in order. If you encounter an error at any step, attempt to fix it up to 5 times before calling
AskUserQuestionto ask the user for guidance. Always search existing code first — if there are existing login/logout handlers, hook into them rather than creating new ones.
Agent instruction: Check the project directory for an existing package manager file:
Podfilepresent → CocoaPodsCartfilepresent → CarthagePackage.swiftpresent → Swift Package ManagerIf none are found, ask via
AskUserQuestion: "Which dependency manager does your project use — Swift Package Manager, CocoaPods, or Carthage?"Swift Package Manager —
Package.swiftproject: Run this command in the project root to add the dependency automatically, then add"Auth0"to the target'sdependenciesarray inPackage.swift:bash
swift package add-dependency https://github.com/auth0/Auth0.swift --from 2.18.0Swift Package Manager — Xcode project (
.xcodeproj, noPackage.swift): The CLI command does not apply. Instruct the user to add the package via Xcode: File → Add Package Dependencies →https://github.com/auth0/Auth0.swift→ Up to Next Major Version from2.18.0.CocoaPods or Carthage: Follow the matching installation steps in Setup Guide. Do not just show the instructions — perform the file edits and run the commands.
Agent instruction:
- If Auth0 credentials (domain AND client ID) are already in the user's prompt: Write
Auth0.plistdirectly with those values and proceed to Step 3.- If no credentials are provided: Run the bootstrap script — do NOT ask the user to create or configure an Auth0 application manually. Always use the CLI path.
Follow Setup Guide — Auth0 Configuration for pre-flight checks and the script command.
Agent instruction:
- Read
Auth0.plistto obtainClientIdandDomain.- Extract the bundle identifier from
project.pbxproj: search forPRODUCT_BUNDLE_IDENTIFIER, skip values containing$(orTests.- Ask the user via
AskUserQuestion: "Which callback URL scheme would you like to use?"
- Custom scheme (
{bundle}://) — simpler, works on all Apple platforms- HTTPS Universal Links — recommended for production; prevents URL scheme hijacking
Then follow only the matching path below.
Agent instruction: Register the callback URLs using the Auth0 CLI (substitute real values for
CLIENT_ID,BUNDLE_ID,DOMAIN):bash
auth0 apps update CLIENT_ID \ --callbacks "BUNDLE_ID://DOMAIN/ios/BUNDLE_ID/callback" \ --logout-urls "BUNDLE_ID://DOMAIN/ios/BUNDLE_ID/callback" \ --no-inputThen follow the URL scheme registration steps in Setup Guide to register
$(PRODUCT_BUNDLE_IDENTIFIER)as a URL type in Xcode.
Agent instruction: All four steps below are required — skipping any one will cause the callback redirect to fail silently after login.
Step B1 — Register callback URLs via Auth0 CLI: Register both HTTPS and custom scheme so the app works in all scenarios:
bash
auth0 apps update CLIENT_ID \ --callbacks "https://DOMAIN/ios/BUNDLE_ID/callback,BUNDLE_ID://DOMAIN/ios/BUNDLE_ID/callback" \ --logout-urls "https://DOMAIN/ios/BUNDLE_ID/callback,BUNDLE_ID://DOMAIN/ios/BUNDLE_ID/callback" \ --no-inputStep B2 — Configure Device Settings via Auth0 CLI: Extract
DEVELOPMENT_TEAMfromproject.pbxproj(10-character value, e.g.ABC12DE34F). If not found, ask viaAskUserQuestion: "What is your Apple Team ID? (developer.apple.com → Account → Membership Details)"bash
auth0 api patch applications/CLIENT_ID \ --data '{"mobile":{"ios":{"team_id":"TEAM_ID","app_bundle_identifier":"BUNDLE_ID"}}}' \ --no-inputAuth0 will now host
https://DOMAIN/.well-known/apple-app-site-associationautomatically — required for Universal Links to work on device.Step B3 — Add Associated Domains entitlement in Xcode: Add
com.apple.developer.associated-domainsto the app's.entitlementsfile with bothapplinks:andwebcredentials:entries for the Auth0 domain. See Setup Guide — Associated Domains for the complete entitlements XML, Xcode capability steps, and build settings verification.Step B4 — Use
.useHTTPS()in the SDK:swift
Auth0.webAuth().useHTTPS()
Agent instruction: Search the project for
@main struct(SwiftUI) orAppDelegate/UIViewController(UIKit) to detect the UI framework. If ambiguous, ask viaAskUserQuestion: "Does your app use SwiftUI or UIKit?" Then follow only the matching path below.
Agent instruction: Create
AuthenticationService.swiftas anObservableObject, then wire it into the app entry point and root view. Search for the@mainstruct andContentView(or equivalent root view) and update them as shown.
swift
// AuthenticationService.swift
import Auth0
import Combine
class AuthenticationService: ObservableObject {
@Published var isAuthenticated = false
private let credentialsManager = CredentialsManager(authentication: Auth0.authentication())
init() { isAuthenticated = credentialsManager.canRenew() }
func login() async {
do {
let credentials = try await Auth0
.webAuth()
.useHTTPS()
.scope("openid profile email offline_access")
.start()
_ = credentialsManager.store(credentials: credentials)
await MainActor.run { isAuthenticated = true }
} catch WebAuthError.userCancelled { }
catch { print("Login failed: \(error)") }
}
func logout() async {
do { try await Auth0.webAuth().useHTTPS().clearSession() }
catch { print("Logout failed: \(error)") }
_ = credentialsManager.clear()
await MainActor.run { isAuthenticated = false }
}
}
swift
// @main App struct — inject AuthenticationService as environment object
@StateObject private var auth = AuthenticationService()
// In body: ContentView().environmentObject(auth)
// Root ContentView — branch on authentication state
@EnvironmentObject var auth: AuthenticationService
// In body: if auth.isAuthenticated { HomeView() } else { LoginView() }
For complete SwiftUI app lifecycle wiring, see Integration Patterns.
Agent instruction: Create
AuthenticationService.swiftas a plain class, then add login/logout calls to the relevantUIViewController. Also check whether the app usesSFSafariViewController— if so, addWebAuthentication.resume(with:)toAppDelegate/SceneDelegate(see note below).
swift
// AuthenticationService.swift
import Auth0
class AuthenticationService {
private let credentialsManager = CredentialsManager(authentication: Auth0.authentication())
var isAuthenticated: Bool { credentialsManager.canRenew() }
func login() async throws {
let credentials = try await Auth0
.webAuth()
.useHTTPS()
.scope("openid profile email offline_access")
.start()
_ = credentialsManager.store(credentials: credentials)
}
func logout() async throws {
try await Auth0.webAuth().useHTTPS().clearSession()
_ = credentialsManager.clear()
}
}
swift
// In your UIViewController
private let auth = AuthenticationService()
@IBAction func loginTapped(_ sender: UIButton) {
Task {
do {
try await auth.login()
await MainActor.run { navigateToHome() }
} catch WebAuthError.userCancelled { }
catch { print("Login failed: \(error)") }
}
}
@IBAction func logoutTapped(_ sender: UIButton) {
Task {
do { try await auth.logout() }
catch { print("Logout failed: \(error)") }
await MainActor.run { navigateToLogin() }
}
}
Note — SFSafariViewController only: If the app uses
.provider(WebAuthentication.safariProvider())instead of the defaultASWebAuthenticationSession, addWebAuthentication.resume(with: url)toAppDelegate.application(_:open:url:options:)andSceneDelegate.scene(_:openURLContexts:). See Integration Patterns for the exact code.
Agent instruction: Run a build to verify the integration compiles without errors:
bash
xcodebuild build -scheme YOUR_SCHEME -destination "platform=iOS Simulator,name=iPhone 16"If the build fails, review error messages and fix up to 5 times before asking the user.
MistakeFixAuth0 app type not set to NativeIn Auth0 Dashboard, select "Native" when creating the applicationMissing callback URL in Auth0 DashboardAdd both https:// Universal Link and {bundle}:// custom scheme to Allowed Callback URLs and Logout URLsAuth0.plist not added to Xcode targetRight-click file in Navigator → "Add Files to Target" → check your app targetMissing offline_access scopeAdd "offline_access" to scope string to receive a refresh token for silent renewalTokens stored in UserDefaultsAlways use CredentialsManager — it stores tokens in Keychain with access controlCalling credentialsManager.credentials() before store()Store credentials from login result before attempting to retrieveOpening .xcodeproj instead of .xcworkspace (CocoaPods)Always open the .xcworkspace file after pod installNot calling clearSession() on logoutAlways call clearSession() to remove the Auth0 session cookie from the browserBuild error "No such module 'Auth0'"Verify the package is added to the correct target; for CocoaPods, open .xcworkspace
auth0-quickstart - Basic Auth0 setupauth0-cli - Manage Auth0 resources from the terminal