Mega Bundle SALE is ON! Get ALL of our amazing iOS app codebases at 95% OFF discount 🔥

Firebase is having great momentum these days. It has gained a lot of traction among mobile developers, who are truly embracing this backend-as-a-service concept. We are using it for all of our iOS app templates. In this Firebase Swift tutorial, you’ll learn how to build the login and registration screens that you can find in most of our apps. This is one of the first tutorials on this topic (Firebase Swift tutorials), and we’re super excited to make this a wonderful course series. At the end of this Swift Firebase tutorial, we’re going to finish these beautiful functional onboarding screens:

swift boilerplate

As an iOS programmer, every time you start developing a new app idea you find yourself in the situation of building a user onboarding flow – landing screen, log in, registration, etc. Firebase takes care of everything you need to handle on the server side (user management, OAuth, security, password storage, etc.), so it really abstracts away the hardest part of getting an app started. Let’s try to abstract away the Swift code part of the equation so that you don’t need to reinvent the wheel every time you start a new mobile app. This is also a great introduction to Firebase for Swift developers who like to learn by getting their hands dirty with some code right from the start.

For this tutorial, we’re going to assume you have some basic understanding of Swift and you’re already familiar with Xcode. We are going to use the latest Firebase Pods, so make sure you have CocoaPods installed on your machine. If you want to jump straight into the code, check out this commit diff which includes all the coded changes described below. Also, the final project can be downloaded with our Swift Boilerplate starter kit.

Getting Started

To get started, download our starter Xcode Project, and open FirebaseStarterApp.xcworkspace in Xcode. Build and run the app in any simulator or device. Let’s take a look at the high-level structure of the starter kit app:

  • View Controllers – in this folder you can find the code for the three main screens (landing, login, sign up), along with their corresponding .xib files.
    xib filesAs general guidelines, this is how I decoupled responsibilities from Interface Builder and programmatic land:

    • The layout logic lives in the .xib file (e.g. this button should be horizontally aligned and its top spacing should be 20px)
    • The UI customizations happen programmatically, in the .swift file (e.g. colors, fonts, borders, strings, etc)
    • The navigation happens programmatically (so I’m not using storyboards, due to their limitation)
  • AppDelegate – just like any other iOS App, this class represents the runtime entry point to your code. Notice how we set the root view controller of the current window to be the landing screen view controller. This basically makes our custom landing screen the first screen of the app.
  • LaunchScreen.storyboard – this is the iOS Launch Screen, which I customized to have a background color and centered icon, directly in Interface Builder
  • Assets.xcassets – this folder  contains the images used in the app
  • Controls – this folder contains extensions of common UIKit components, decorating them with extra utility methods (e.g. such as instantiating a UIColor from a hex string). We won’t focus on these categories in this tutorial.

The screens are currently static, so you can only navigate to them. Nothing really happens if you tap the buttons or type into the text fields. Now that we have a better understanding of the anatomy of our Xcode starter kit, let’s dive into adding Firebase support.

Setting up Your Firebase Account

Head over to Firebase Console and create a new project (name it as you wish). Once you’ve created a new Firebase project, go to its Firebase Dashboard, by simply clicking on it in Firebase. You should be landing on this screen:

swift firebase authBelow the centered title, press on the “Add app” button and add a new iOS app to your project. For the bundle ID, you can use “io.instamobile.FirebaseStarterApp“, which is the Bundle ID of our starter project. If you’d prefer to use your own bundle ID, make sure you update the Bundle Identifier in Xcode (“General” tab of the FirebaseStarterApp build target)

ios project firebase

Once registered, Firebase will generate a GoogleService-Info.plist file, which you need to download and add to your project in Xcode.

ios firebase

That’s it – you now have a Firebase iOS project that can be used from within the Swift code. Let’s see how.

Adding Firebase Pods Dependencies to Your App

In order to query the Firebase project from within your iOS app, we need to use the Firebase iOS SDKs, which are a set of libraries provided by Google, to make it easy for iOS developer to use Firebase in their app. These Swift SDKs are basically bridging the communication of your iOS app with the Firebase backend.

To add the Firebase SDKs to your app, just add cocoapods dependencies to the Podfile. Getting started with Cocoapods is out of scope for this tutorial, so if you’re not familiar with it, check out

Open the Podfile file, and add the following lines:

pod 'Firebase/Core'
pod 'Firebase/Auth'
pod 'Firebase/Firestore'

Once you do this, you need to run “pod update” in your terminal which will download the SDKs for you. A successful result will look like this in the terminal:

pods firebase

To check whether this was successful, let’s see if we can use Firebase dependencies in the code now. Open up AppDelegate.swift and add this import:

import Firebase

Then, add this line as the first line of the application:didFinishLaunchingWithOptions: method:


This builds and runs successfully in Xcode. We’re done here and ready to jump into action.

Firebase Swift User Registration

Let’s focus now on writing the code that will make user registration with Firebase work properly. The downloaded Swift starter kit only has the UI part done, so we need to hook up the registration screen to Firebase.

Ideally, we decouple the code of interacting with Firebase from our view layer (view controllers), so that our code is properly modularized. To this point, let’s create a new class named FirebaseAuthManager which will deal with all the interactions we need with our Firebase backend.

import FirebaseAuth
import UIKit

class FirebaseAuthManager {

    func createUser(email: String, password: String, completionBlock: @escaping (_ success: Bool) -> Void) {
        Auth.auth().createUser(withEmail: email, password: password) {(authResult, error) in
            if let user = authResult?.user {
            } else {


We added a method that’s responsible for creating a new user account in Firebase and call the completionBlock when the operation finishes. It passes back to the caller a boolean flag, indicating whether the registration was successful or not. We are also printing out the newly created user information to the console.

To create the user, we solely rely on the FirebaseAuth SDK,  by calling Auth.auth().createUser method. This will do everything from us – secure authentication to Firebase, user creation, error handling, networking, etc. Easy, right?

We have the code interacting with Firebase. Now we need to trigger it from within the app. The registration needs to happen on the signup screen, once a user presses the sign up button. Open ATCClassicSignUpViewController.swift, and locate didTapSignUpButton method. Let’s add the following code in it:

@objc func didTapSignUpButton() {
    let signUpManager = FirebaseAuthManager()
    if let email = emailTextField.text, let password = passwordTextField.text {
        signUpManager.createUser(email: email, password: password) {[weak self] (success) in
            guard let `self` = self else { return }
            var message: String = ""
            if (success) {
                message = "User was sucessfully created."
            } else {
                message = "There was an error."
            let alertController = UIAlertController(title: nil, message: message, preferredStyle: .alert)
            alertController.addAction(UIAlertAction(title: "OK", style: .cancel, handler: nil))
            self.display(alertController: alertController)

So what happens here? The methods get triggered when users click the registration button. We check whether we have both e-mail and password fields filled out, and we ask the Firebase Manager to create an account. Once the manager gets back to us with the response (success or error), we show a message to communicate the result to the user. Now run the project again and add a new user in the registration flow. You should get in this state:

firebase registration swift

Boom! You have just created the first user of your brand new app. Congratulations!

You can go to Firebase Console -> Authentication, and the new user information will be listed there.

firebase auth users

Implementing User Login in Firebase

Now that we have a mechanism to create new users, we need to implement a flow that will allow them to sign into the app with their credentials. Let’s go back to FirebaseAuthManager class and add the login function:

func signIn(email: String, pass: String, completionBlock: @escaping (_ success: Bool) -> Void) {
    Auth.auth().signIn(withEmail: email, password: pass) { (result, error) in
        if let error = error, let _ = AuthErrorCode(rawValue: error._code) {
        } else {

Again, we are leveraging Firebase SDK to communicate with the Firebase instance and make a login request. The completion block of the Auth.auth().signIn call returns a result, which contains all the logged-in credentials necessary for further requests or the error, describing in details why the authentication failed (e.g. user not found).

Let’s now hook up this new API to our existing Login Screen UI. The login screen is managed by ATCClassicLoginScreenViewController.swift, which is what you’ll open now. Locate the didTapLoginButton method and add the following lines of Swift code:

@objc func didTapLoginButton() {
    let loginManager = FirebaseAuthManager()
    guard let email = contactPointTextField.text, let password = passwordTextField.text else { return }
    loginManager.signIn(email: email, pass: password) {[weak self] (success) in
        guard let `self` = self else { return }
        var message: String = ""
        if (success) {
            message = "User was sucessfully logged in."
        } else {
            message = "There was an error."
        let alertController = UIAlertController(title: nil, message: message, preferredStyle: .alert)
        alertController.addAction(UIAlertAction(title: "OK", style: .cancel, handler: nil))
        self.display(alertController: alertController)

Similarly to what we did for account creation, here we are calling the sign in API and handle the result of the login request within the completion block. For our simple tutorial, we only show a success or error message. Run the code again in Xcode and you should be able to get a successful message when trying to log in with the credentials of a valid user that you’ve created in advance.

On the Firebase Console (Authentication dashboard), you’ll also notice that the last “Sign In” Timestamp will change for the specific user. Here’s how the final project will look like when you complete this tutorial:

firebase auth swift

Conclusion and Next Steps

In this Swift Firebase tutorial, we showed step by step how to integrated Firebase Auth into a Swift project, using Xcode. By leveraging the Firebase SDKs, integrated using Cocoapods, we can simply retrieve and store user data from Firebase with a couple of trivial API calls. We’re leaving the parsing of the auth result (username information, credential token, etc) as an exercise to the reader.

The Firebase integration in this tutorial is basic, so many more features will be needed for an awesome app. While we’re going to write down tutorials for many of these features, here’s a few things you can try on your own:

  • Storing more user information (username, full name, address, etc) using Firebase Firestore
  • Uploading profile photos using Firebase Storage
  • Persisting user credentials, so that users stay logged-in across different app sessions
  • Adding Facebook Login with Firebase

We also decoupled the concerns of server interactions into its own class (FirebaseAuthManager), so that the view layer doesn’t interact with Firebase directly. This is great architecture and a principle that you need to follow every time you write iOS code. Ideally, we’d go a step further and introduce an extra layer of abstraction, such as a protocol that will describe the interface of an Auth Manager in general. In this way, plugging in a different type of backend (Parse, WooCommerce, Shopify, Magento, REST API, etc) won’t involve any changes at all in the view layer, since the views would only deal with a protocol named “LoginManager“.

I’m going to leave all these nice to have as exercises for the reader. Please let me know if there’s anything else you want me to cover in the next tutorials or whether you need more help figuring out the implementation details of this Firebase Swift Tutorial. #shipit

For those looking how to build this in SwiftUI, I recommend checking out this SwiftUI Firebase Auth tutorial on Devbrite.


Categories: Swift programming


ben · March 7, 2019 at 11:26 pm

Hello, I git cloned the project to my desktop, went to open FirebaseStarterApp.xcworkspace and it’s full of build errors.

Showing Recent Messages
:-1: /Users/core/Desktop/FirebaseStarterApp/Pods/Target Support Files/Pods-FirebaseStarterApp/Pods-FirebaseStarterApp.debug.xcconfig: unable to open file (in target “FirebaseStarterApp” in project “FirebaseStarterApp”) (in target ‘FirebaseStarterApp’)

Showing Recent Messages
:-1: /Users/core/Desktop/FirebaseStarterApp/Pods/Target Support Files/Pods-FirebaseStarterApp/Pods-FirebaseStarterApp.debug.xcconfig: unable to open file (in target “FirebaseStarterApp” in project “FirebaseStarterApp”) (in target ‘FirebaseStarterApp’)

Showing Recent Messages
:-1: /Users/core/Desktop/FirebaseStarterApp/Pods/Target Support Files/Pods-FirebaseStarterApp/Pods-FirebaseStarterApp.debug.xcconfig: unable to open file (in target “FirebaseStarterApp” in project “FirebaseStarterApp”) (in target ‘FirebaseStarterApp’)

Showing Recent Messages
:-1: /Users/core/Desktop/FirebaseStarterApp/Pods/Target Support Files/Pods-FirebaseStarterApp/Pods-FirebaseStarterApp.debug.xcconfig: unable to open file (in target “FirebaseStarterApp” in project “FirebaseStarterApp”) (in target ‘FirebaseStarterApp’)

    florian · March 8, 2019 at 4:33 am

    Can you confirm that you ran “pod update” before you opened the project in Xcode? From the errors, it seems you haven’t installed the pods

Brandon · May 9, 2019 at 4:11 pm

Found an error in your code (messed me up for a few hours)! In your createUser() method your else statement currently says “completionBlock(true)”, but it should say “completionBlock(false)” to return an error when the login didn’t work.

    florian · May 10, 2019 at 3:15 am

    Nice catch! Thanks for calling that out. I’ve updated the tutorial.

Bhanuka · May 18, 2019 at 2:16 am

Why dont you use storyboard?

    florian · May 18, 2019 at 6:56 pm

    We use .xibs with manual navigation. Storyboards are a bad pattern from an architecture perspective (e.g. separation of concerns), and they don’t scale in large teams or apps (e.g. merge conflicts). Plus, the only advantage they have over .xibs is that they handle navigation, which is actually just one line of code (navigationController.push(vc)), so there’s no real benefit for storyboards, unless you are a non-coder.

Daniel · July 1, 2019 at 3:25 pm

Hi, do you have any idea why Facebook Login is not working since iOS 13 ? It always returns cancel state ..
Thanks for any help !

Mario · September 14, 2019 at 8:00 pm

After updating the PodFile, when I’m launching the application, the Build Succeed and appears on my iPhone but immediately the App show a blank window with the message in class AppDelegate: ” Thread1:signal SIGABRT”.

    florian · September 17, 2019 at 12:36 am

    How did you update the Podfile? Is there any more information about the crash in the console?

      Tess · September 26, 2019 at 2:27 am

      I get the same error and this is what is displayed in the console:
      “libc++abi.dylib: terminating with uncaught exception of type NSException”

    Mario · October 2, 2019 at 8:16 pm

    OK, now the FirebaseStarterApp is working alone. Now I started my own App, I add to my project the FirebaseStarterApp using the command “Add Files”, I run in the terminal the Podfile with all the dependencies and now I would like to add to my Main.Storyboard the . xib files of the FirebaseStarterApp. Could you suggest me the better path how to embed the .xib file to my Main.Storyboard?

Leave a Reply

Your email address will not be published. Required fields are marked *

Shopping Cart