Firebase Authentication을 사용하면 임시 익명 계정을 생성 및 사용하여 Firebase에 인증할 수 있습니다. 이 임시 익명 계정을 통해 아직 앱에 가입하지 않은 사용자들도 보안 규칙으로 보호받는 데이터를 사용할 수 있습니다. 익명 사용자가 앱에 가입하기로 결정하면 이 사용자의 로그인 인증 정보를 해당 익명 계정에 연결하여 사용자가 추후 세션에서도 보호받는 데이터를 계속 사용하도록 할 수 있습니다.
시작하기 전에
Swift Package Manager를 사용해 Firebase 종속 항목을 설치하고 관리하세요.
앱 프로젝트를 연 상태로 Xcode에서 File(파일) > Add Packages(패키지 추가)로 이동합니다.
선택사항: 프로젝트를 Firebase Authentication with Identity Platform으로 업그레이드한 경우 자동 정리를 사용 설정할 수 있습니다. 이 설정을 사용하면 30일이 지난 익명 계정은 자동으로 삭제됩니다. 자동 정리가 사용 설정된 프로젝트에서는 익명 인증이 더 이상 사용량 한도 또는 결제 할당량에 포함되지 않습니다. 자동 정리를 참조하세요.
Firebase에 익명으로 인증
로그아웃 상태의 사용자가 Firebase에 인증이 필요한 앱 기능을 사용할 때 다음 절차를 밟으면 사용자를 익명으로 로그인시킬 수 있습니다.
UIApplicationDelegate로 FirebaseCore 모듈과 앱 대리자가 사용하는 다른 Firebase 모듈을 가져옵니다.
예를 들어 Cloud Firestore와 Authentication을 사용하려면 다음을 따르세요.
앱 대리자의 application(_:didFinishLaunchingWithOptions:) 메서드에서 FirebaseApp 공유 인스턴스를 구성합니다.
SwiftUI
// Use Firebase library to configure APIsFirebaseApp.configure()
Swift
// Use Firebase library to configure APIsFirebaseApp.configure()
Objective-C
// Use Firebase library to configure APIs[FIRAppconfigure];
SwiftUI를 사용하는 경우 앱 대리자를 만들고 UIApplicationDelegateAdaptor 또는 NSApplicationDelegateAdaptor를 통해 App 구조체에 연결해야 합니다. 앱 대리자 재구성도 중지해야 합니다. 자세한 내용은 SwiftUI 안내를 참조하세요.
SwiftUI
@mainstructYourApp:App{// register app delegate for Firebase setup@UIApplicationDelegateAdaptor(AppDelegate.self)vardelegatevarbody:someScene{WindowGroup{NavigationView{ContentView()}}}}
linkWithCredential:completion: 호출이 성공하면 사용자의 신규 계정에서 익명 계정의 Firebase 데이터에 액세스할 수 있습니다.
자동 정리
프로젝트를 Firebase Authentication with Identity Platform으로 업그레이드한 경우 Firebase Console에서 자동 정리를 사용 설정할 수 있습니다. 이 기능을 사용 설정하면 Firebase에서 30일이 지난 익명 계정을 자동으로 삭제할 수 있습니다. 자동 정리가 사용 설정된 프로젝트에서는 익명 인증이 사용량 한도 또는 결제 할당량에 포함되지 않습니다.
자동 정리를 사용 설정한 후 만든 익명 계정은 생성 후 30일이 지나면 언제든지 자동으로 삭제될 수 있습니다.
기존 익명 계정은 자동 정리를 사용 설정한 후 30일이 지나면 자동으로 삭제될 수 있습니다.
자동 정리를 사용 중지해도 삭제 예약된 익명 계정은 삭제가 예약된 상태로 유지됩니다.
익명 계정을 로그인 방법에 연결하여 '업그레이드'할 경우 계정이 자동으로 삭제되지 않습니다.
[null,null,["최종 업데이트: 2025-08-16(UTC)"],[],[],null,["You can use Firebase Authentication to create and use temporary anonymous accounts\nto authenticate with Firebase. These temporary anonymous accounts can be used to\nallow users who haven't yet signed up to your app to work with data protected\nby security rules. If an anonymous user decides to sign up to your app, you can\n[link their sign-in credentials to the anonymous\naccount](/docs/auth/ios/account-linking) so that they can continue to work with their protected data in\nfuture sessions.\n\nBefore you begin\n\n1. Use Swift Package Manager to install and manage Firebase dependencies.\n\n | Visit [our installation guide](/docs/ios/installation-methods) to learn about the different ways you can add Firebase SDKs to your Apple project, including importing frameworks directly and using CocoaPods.\n 1. In Xcode, with your app project open, navigate to **File \\\u003e Add Packages**.\n 2. When prompted, add the Firebase Apple platforms SDK repository: \n\n ```text\n https://github.com/firebase/firebase-ios-sdk.git\n ```\n | **Note:** New projects should use the default (latest) SDK version, but you can choose an older version if needed.\n 3. Choose the Firebase Authentication library.\n 4. Add the `-ObjC` flag to the *Other Linker Flags* section of your target's build settings.\n 5. When finished, Xcode will automatically begin resolving and downloading your dependencies in the background.\n2. If you haven't yet connected your app to your Firebase project, do so from the [Firebase console](//console.firebase.google.com/).\n3. Enable anonymous auth:\n 1. In the [Firebase console](//console.firebase.google.com/), open the **Auth** section.\n 2. On the **Sign-in Methods** page, enable the **Anonymous** sign-in method.\n 3. **Optional** : If you've upgraded your project to [Firebase Authentication with Identity Platform](/auth#identity-platform), you can enable automatic clean-up. When you enable this setting, anonymous accounts older than 30 days will be automatically deleted. In projects with automatic clean-up enabled, anonymous authentication will no longer count toward usage limits or billing quotas. See [Automatic clean-up](#auto-cleanup).\n\nAuthenticate with Firebase anonymously\n\nWhen a signed-out user uses an app feature that requires authentication with\nFirebase, sign in the user anonymously by completing the following steps:\n\n1. Import the `FirebaseCore` module in your `UIApplicationDelegate`, as well as any other [Firebase modules](/docs/ios/setup#available-pods) your app delegate uses. For example, to use Cloud Firestore and Authentication: \n\n SwiftUI \n\n ```swift\n import SwiftUI\n import FirebaseCore\n import FirebaseFirestore\n import FirebaseAuth\n // ...\n \n ```\n\n Swift \n\n ```swift\n import FirebaseCore\n import FirebaseFirestore\n import FirebaseAuth\n // ...\n \n ```\n\n Objective-C \n\n ```objective-c\n @import FirebaseCore;\n @import FirebaseFirestore;\n @import FirebaseAuth;\n // ...\n \n ```\n2. Configure a [`FirebaseApp`](/docs/reference/swift/firebasecore/api/reference/Classes/FirebaseApp) shared instance in your app delegate's `application(_:didFinishLaunchingWithOptions:)` method: \n\n SwiftUI \n\n ```swift\n // Use Firebase library to configure APIs\n FirebaseApp.configure()\n ```\n\n Swift \n\n ```swift\n // Use Firebase library to configure APIs\n FirebaseApp.configure()\n ```\n\n Objective-C \n\n ```objective-c\n // Use Firebase library to configure APIs\n [FIRApp configure];\n ```\n3. If you're using SwiftUI, you must create an application delegate and attach it to your `App` struct via `UIApplicationDelegateAdaptor` or `NSApplicationDelegateAdaptor`. You must also disable app delegate swizzling. For more information, see the [SwiftUI instructions](/docs/ios/learn-more#swiftui). \n\n SwiftUI \n\n ```swift\n @main\n struct YourApp: App {\n // register app delegate for Firebase setup\n @UIApplicationDelegateAdaptor(AppDelegate.self) var delegate\n\n var body: some Scene {\n WindowGroup {\n NavigationView {\n ContentView()\n }\n }\n }\n }\n \n ```\n4. Call the `signInAnonymouslyWithCompletion:` method: \n\n Swift \n\n ```swift\n Auth.auth().signInAnonymously { authResult, error in\n // ...\n }\n ```\n\n Objective-C \n\n ```objective-c\n [[FIRAuth auth] signInAnonymouslyWithCompletion:^(FIRAuthDataResult * _Nullable authResult,\n NSError * _Nullable error) {\n // ...\n }];\n ```\n5. If the `signInAnonymouslyWithCompletion:` method completes without error, you can get the anonymous user's account data from the `FIRAuthDataResult` object: \n\n Swift \n\n ```swift\n guard let user = authResult?.user else { return }\n let isAnonymous = user.isAnonymous // true\n let uid = user.uid\n ```\n\n Objective-C \n\n ```objective-c\n FIRUser *user = authResult.user;\n BOOL isAnonymous = user.anonymous; // YES\n NSString *uid = user.uid;\n ```\n\n| To protect your project from abuse, Firebase limits the number of new email/password and anonymous sign-ups that your application can have from the same IP address in a short period of time. You can request and schedule temporary changes to this quota from the [Firebase console](//console.firebase.google.com/project/_/authentication/providers).\n\nConvert an anonymous account to a permanent account\n\nWhen an anonymous user signs up to your app, you might want to allow them to\ncontinue their work with their new account---for example, you might want to\nmake the items the user added to their shopping cart before they signed up\navailable in their new account's shopping cart. To do so, complete the following\nsteps:\n\n1. When the user signs up, complete the sign-in flow for the user's authentication provider up to, but not including, calling one of the [`FIRAuth.signInWith`](/docs/reference/ios/firebaseauth/interface_f_i_r_auth) methods. For example, get the user's Google ID token, Facebook access token, or email address and password.\n2. Get an `FIRAuthCredential` for the new authentication provider:\n\n Google Sign-In \n\n Swift \n\n ```swift\n guard\n let authentication = user?.authentication,\n let idToken = authentication.idToken\n else {\n return\n }\n\n let credential = GoogleAuthProvider.credential(withIDToken: idToken,\n accessToken: authentication.accessToken)\n ```\n\n Objective-C \n\n ```objective-c\n FIRAuthCredential *credential =\n [FIRGoogleAuthProvider credentialWithIDToken:result.user.idToken.tokenString\n accessToken:result.user.accessToken.tokenString];\n ```\n\n Facebook Login \n\n Swift \n\n ```swift\n let credential = FacebookAuthProvider\n .credential(withAccessToken: AccessToken.current!.tokenString)\n ```\n\n Objective-C \n\n ```objective-c\n FIRAuthCredential *credential = [FIRFacebookAuthProvider\n credentialWithAccessToken:[FBSDKAccessToken currentAccessToken].tokenString];\n ```\n\n Email-password sign-in \n\n Swift \n\n ```swift\n let credential = EmailAuthProvider.credential(withEmail: email, password: password)\n ```\n\n Objective-C \n\n ```objective-c\n FIRAuthCredential *credential =\n [FIREmailAuthProvider credentialWithEmail:email\n password:password];\n ```\n3. Pass the `FIRAuthCredential` object to the sign-in user's\n `linkWithCredential:completion:` method:\n\n Swift \n\n ```swift\n user.link(with: credential) { authResult, error in\n // ...\n }\n }\n ```\n\n Objective-C \n\n ```objective-c\n [[FIRAuth auth].currentUser linkWithCredential:credential\n completion:^(FIRAuthDataResult *result, NSError *_Nullable error) {\n // ...\n }];\n ```\n\nIf the call to `linkWithCredential:completion:` succeeds, the user's new account can\naccess the anonymous account's Firebase data.\n| This technique can also be used to [link any two accounts](/docs/auth/ios/account-linking).\n\nAutomatic clean-up\n\nIf you've upgraded your project to [Firebase Authentication with Identity Platform](/docs/auth#identity-platform), you can\nenable automatic clean-up in the Firebase console. When you enable this feature you allow\nFirebase to automatically delete anonymous accounts older than 30 days. In projects with automatic\nclean-up enabled, anonymous authentication will not count toward usage limits or billing quotas.\n\n- Any anonymous accounts created after enabling automatic clean-up might be automatically deleted any time after 30 days post-creation.\n- Existing anonymous accounts will be eligible for automatic deletion 30 days after enabling automatic clean-up.\n- If you turn automatic clean-up off, any anonymous accounts scheduled to be deleted will remain scheduled to be deleted.\n- If you \"upgrade\" an anonymous account by linking it to any sign-in method, the account will not get automatically deleted.\n\nIf you want to see how many users will be affected before you enable this feature, and you've\nupgraded your project to [Firebase Authentication with Identity Platform](/docs/auth#identity-platform), you can filter by\n`is_anon` in [Cloud\nLogging](https://cloud.google.com/logging/docs).\n\nNext steps\n\nNow that users can authenticate with Firebase, you can control their access to\ndata in your Firebase database using\n[Firebase rules](/docs/database/security#section-authorization)."]]
