📱 Mobile App Integration Track

Source: en/tracks/mobile.md · Live: https://docs.1pass.dev/en/tracks/mobile LLM-sanitized: internal links absolutized, VitePress containers → admonitions, line numbers in the Jump-to Index reference this rendered file (1-indexed).

📍 Jump-to Index

• L29-L37: ## The four core promises
• L38-L45: ## Step 1 · Register the app
• L46-L97: ## Step 2 · Platform quickstart
  • L48-L83: ### iOS — LogiAuth Swift Package (recommended)
  • L84-L97: ### Other platforms
• L98-L104: ## Step 3 · Avoid the mobile-specific pitfalls
• L105-L114: ## Step 4 · Pre-build checks
• L115-L123: ## Common reference (track-agnostic)
• L124-L131: ## Hand the whole thing to an AI

---

📱 Mobile App Integration Track

The fastest path to integrating logi in iOS, Android, Flutter, and React Native native apps.

💡 Tip: Is this the right track?

• ✅ Yes: a native app users install from an app store
• ❌ Web → 🌐 Web Integration Track
• ❌ Machine-to-machine / CLI → 🔧 API · CLI Track

The four core promises

1. Public client + PKCE are required. Never hardcode client_secret into a mobile app.
2. Use a single custom-scheme redirect_uri — for example, com.example.app://oauth/1pass/callback.
3. App-to-app first, in-app browser fallback — works even when the user arrives from an in-app browser like KakaoTalk or Naver.
4. Keep the app RP and the web RP separate — don't mix mobile and web redirects under the same client_id. Details: Common / Public Clients · One RP per surface

---

Step 1 · Register the app

Register one RP with client_type: public. You can do this from the console or the API.

• App registration guide — console UI walkthrough
• Public Clients (PKCE-only) — API registration + redirect_uri policy
• Choosing Public vs Confidential — which one to pick

Step 2 · Platform quickstart

iOS — LogiAuth Swift Package (recommended)

On iOS, the official Swift SDK LogiAuth handles PKCE, ASWebAuthenticationSession, the in-app escape, and keychain storage for you. Reach for the SDK before you roll your own.

// Package.swift
.package(url: "https://github.com/dcode-co/logi-auth-swift.git", from: "0.2.0"),

// App.swift
import LogiAuth

@main
struct MyApp: App {
  init() {
    LogiAuth.configure(LogiAuthConfig(
      clientId: "logi_xxx",
      redirectURI: URL(string: "myapp://oauth/1pass/callback")!
    ))
  }

  var body: some Scene {
    WindowGroup {
      ContentView()
        .onOpenURL { url in _ = LogiAuth.handle(url) }
    }
  }
}

// anywhere
let result = try await LogiAuth.signIn()

Don't forget .onOpenURL { url in _ = LogiAuth.handle(url) } — the SDK receives the login callback there and completes the token exchange.

For full integration and error classification → Swift quickstart

Other platforms

Follow the single page for your stack. The rest are mirrors of the same pattern.

Stack	Guide	SDK / library
iOS (Swift)	integrations/swift	LogiAuth 0.1.2 (recommended) · or roll your own ASWebAuthenticationSession + CryptoKit
Android (Kotlin)	integrations/android	LogiAuth Kotlin SDK (recommended) · or hand-rolled Custom Tabs + DataStore + Keystore
Flutter	integrations/flutter	flutter_web_auth_2 + flutter_secure_storage
React Native	integrations/react-native	react-native-app-auth + react-native-keychain

ℹ️ Note: Storing credentials separately on Android The Android (Kotlin) — Canonical/Merge page covers canonical_sub / linked_subs handling and the pattern for storing credentials separately. For a new integration, read it after you finish the Step 2 guide.

Step 3 · Avoid the mobile-specific pitfalls

• Universal Links integration guide — registering iOS Universal Links and Android App Links
• Escaping the in-app browser — when OAuth is blocked inside the KakaoTalk, Naver, or Facebook in-app browser
• Refresh token rotation policy — rotation-interval differences between Apple Sign In and Google
• First-login completion form — pattern for collecting your own extra info (role/org) once

Step 4 · Pre-build checks

• RP integration testing — verification steps for both the simulator and a real device
• Demo page walkthrough — compare against the reference implementation code
• demo.1pass.dev/oauth — mobile PKCE end-to-end walking sample (scenario deep-links)
• demo.1pass.dev/ios — iOS native (after install) — Universal Link first-try + Swift SDK
• demo.1pass.dev/app-clip — iOS App Clip (before install) — card login via QR scan
• demo.1pass.dev/android — Android native — Intent setPackage first-try + Custom Tabs fallback
• Self-diagnosis — /diagnose — check registration, redirect_uri, and scopes

Common reference (track-agnostic)

• Authorization Code Flow · PKCE · Scope reference
• Error codes · Response headers
• Security best practices (RP side)
• Login button components

---

Hand the whole thing to an AI

Paste @/llms-full.txt into Claude Code, Cursor, or Codex, then say:

"Integrate logi 1pass as an RP into my [iOS Swift / Flutter / Android Kotlin / RN] app, using a public client + PKCE."

→ It generates the quickstart, env, redirect_uri registration, and callback handler automatically.