FirebaseUI for iOS — UI Bindings for Firebase

FirebaseUI supports iOS 10.0+ and Xcode 11+. We recommend using CocoaPods, add the following to your Podfile:

pod 'FirebaseUI', '~> 8.0'       # Pull in all Firebase UI features

If you don't want to use all of FirebaseUI, there are multiple subspecs which can selectively install subsets of the full feature set:

# Only pull in Firestore features
pod 'FirebaseUI/Firestore'

# Only pull in Database features
pod 'FirebaseUI/Database'

# Only pull in Storage features
pod 'FirebaseUI/Storage'

# Only pull in Auth features
pod 'FirebaseUI/Auth'

# Only pull in Facebook login features
pod 'FirebaseUI/Facebook'

# Only pull in Google login features
pod 'FirebaseUI/Google'

# Only pull in Phone Auth login features
pod 'FirebaseUI/Phone'

If you're including FirebaseUI in a Swift project, make sure you also have:

platform :ios, '13.0'
use_frameworks!

Otherwise, you can include the FirebaseUI Xcode project from this repo in your project. You also need to add the Firebase framework to your project.

The READMEs for components of FirebaseUI can be found in their respective project folders.

• Auth
• PhoneAuth
• Database
• Firestore
• Storage

If you'd like to contribute to FirebaseUI for iOS, you'll need to run the following commands to get your environment set up:

$ git clone https://github.com/firebase/FirebaseUI-iOS.git
$ cd FirebaseUI-iOS
$ cd Auth # or PhoneAuth, Database, etc
$ pod install

Alternatively you can use pod try FirebaseUI to install the Objective-C or Swift sample projects.

You'll have to configure your Xcode project in order to run the samples.

1. Your Xcode project should contain a GoogleService-Info.plist, downloaded from Firebase console when you add your app to a Firebase project.
   Copy the GoogleService-Info.plist into the sample project folder (samples/obj-c/GoogleService-Info.plist or samples/swift/GoogleService-Info.plist).

2. Update URL Types.
   Go to Project Settings -> Info tab -> Url Types and update values for:

   • REVERSED_CLIENT_ID (get value from GoogleService-Info.plist)
   • fb{your-app-id} (put Facebook App Id)

3. Update Info.plist with Facebook configuration values

   • FacebookAppID -> {your-app-id} (put Facebook App Id)

4. Enable Keychain Sharing.
   Facebook SDK requires keychain sharing.
   This can be done here: Project Settings -> Capabilities -> KeyChain Sharing -> ON

5. Don't forget to configure your Firebase App Database using Firebase console.
   Database should contain appropriate read/write permissions and folders (objc_demo-chat and swift_demo-chat respectively)

6. In Order to use Phone Auth provider you should Configure Push Notifications

Configure Apple Push Notifications

Enable silent push notifications in Xcode

• Push Notification - Under Capabilities tab in your app target choose Push Notifications and put the switch to the On position.
• Background Mode - Under Capabilities tab in your app target choose Background Modes put the switch to the On position. In the list of available modes select Background fetch and Remote notifications (If available).

Upload APNS Certificate to Firebase

1. Create your Provisioning APNS SSL Certificates by following the steps on the following link. https://firebase.google.com/docs/cloud-messaging/ios/certs

2. Upload your APNS Certificate to Firebase:

   • Inside your project in the Firebase console, select the gear icon, select Project Settings, and then select the Cloud Messaging tab.
   • Select the Upload Certificate button for your development certificate, your production certificate, or both. At least one is required.
   • For each certificate, select the .p12 file, and provide the password, if any. Make sure the bundle ID for this certificate matches the bundle ID of your app. Select Save.

Contributor License Agreements

We'd love to accept your sample apps and patches! Before we can take them, we have to jump a couple of legal hurdles.

Please fill out either the individual or corporate Contributor License Agreement (CLA).

• If you are an individual writing original source code and you're sure you own the intellectual property, then you'll need to sign an [individual CLA] (https://developers.google.com/open-source/cla/individual).
• If you work for a company that wants to allow you to contribute your work, then you'll need to sign a [corporate CLA] (https://developers.google.com/open-source/cla/corporate).

Follow either of the two links above to access the appropriate CLA and instructions for how to sign and return it. Once we receive it, we'll be able to accept your pull requests.

Contribution Process

1. Submit an issue describing your proposed change to the repo in question.
2. The repo owner will respond to your issue promptly.
3. If your proposed change is accepted, and you haven't already done so, sign a Contributor License Agreement (see details above).
4. Fork the desired repo, develop and test your code changes.
5. Ensure that your code adheres to the existing style of the library to which you are contributing.
6. Ensure that your code has an appropriate set of unit tests which all pass.
7. Submit a pull request