This repository contains a subset of the Firebase iOS SDK source. It currently includes FirebaseCore, FirebaseABTesting, FirebaseAuth, FirebaseDatabase, FirebaseFirestore, FirebaseFunctions, FirebaseInstanceID, FirebaseInAppMessaging, FirebaseInAppMessagingDisplay, FirebaseMessaging, FirebaseRemoteConfig, and FirebaseStorage.
The repository also includes GoogleUtilities source. The GoogleUtilities pod is a set of utilities used by Firebase and other Google products.
Firebase is an app development platform with tools to help you build, grow and monetize your app. More information about Firebase can be found at https://firebase.google.com.
See the three subsections for details about three different installation methods.
Go to https://firebase.google.com/docs/ios/setup.
For releases starting with 5.0.0, the source for each release is also deployed to CocoaPods master and available via standard CocoaPods Podfile syntax.
These instructions can be used to access the Firebase repo at other branches, tags, or commits.
See the Podfile Syntax Reference for instructions and options about overriding pod source locations.
All of the official releases are tagged in this repo and available via CocoaPods. To access a local source snapshot or unreleased branch, use Podfile directives like the following:
To access FirebaseFirestore via a branch:
pod 'FirebaseCore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'master'
pod 'FirebaseFirestore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'master'
To access FirebaseMessaging via a checked out version of the firebase-ios-sdk repo do:
pod 'FirebaseCore', :path => '/path/to/firebase-ios-sdk'
pod 'FirebaseMessaging', :path => '/path/to/firebase-ios-sdk'
Instructions for the experimental Carthage distribution are at Carthage.
Instructions for installing binary frameworks via Rome are at Rome.
To develop Firebase software in this repository, ensure that you have at least the following software:
- Xcode 10.1 (or later)
- CocoaPods 1.7.2 (or later)
- CocoaPods generate
For the pod that you want to develop:
pod gen Firebase{name here}.podspec --local-sources=./ --auto-open --platforms=ios
Note: If the CocoaPods cache is out of date, you may need to run
pod repo update before the pod gen command.
Note: Set the --platforms option to macos or tvos to develop/test for
those platforms. Since 10.2, Xcode does not properly handle multi-platform
CocoaPods workspaces.
Firestore has a self contained Xcode project. See Firestore/README.md.
pod gen {name here}.podspec --local-sources=./ --auto-open --platforms=ios- Check the Mac box in the App-iOS Build Settings
- Sign the App in the Settings Signing & Capabilities tab
- Click Pods in the Project Manager
- Add Signing to the iOS host app and unit test targets
- Select the Unit-unit scheme
- Run it to build and test
See AddNewPod.md.
To ensure that the code is formatted consistently, run the script ./scripts/style.sh before creating a PR.
Travis will verify that any code changes are done in a style compliant way. Install
clang-format and swiftformat.
These commands will get the right versions:
brew upgrade https://raw.githubusercontent.com/Homebrew/homebrew-core/e3496d9/Formula/clang-format.rb
brew upgrade https://raw.githubusercontent.com/Homebrew/homebrew-core/7963c3d/Formula/swiftformat.rb
Note: if you already have a newer version of these installed you may need to
brew switch to this version.
To update this section, find the versions of clang-format and swiftformat.rb to match the versions in the CI failure logs here.
Select a scheme and press Command-u to build a component and run its unit tests.
First, make sure that xcov is installed with gem install xcov.
After running the AllUnitTests_iOS scheme in Xcode, execute
xcov --workspace Firebase.xcworkspace --scheme AllUnitTests_iOS --output_directory xcov_output
at Example/ in the terminal. This will aggregate the coverage, and you can run open xcov_output/index.html to see the results.
In order to run the sample apps and integration tests, you'll need valid
GoogleService-Info.plist files for those samples. The Firebase Xcode project contains dummy plist
files without real values, but can be replaced with real plist files. To get your own
GoogleService-Info.plist files:
- Go to the Firebase Console
- Create a new Firebase project, if you don't already have one
- For each sample app you want to test, create a new Firebase app with the sample app's bundle
identifier (e.g.
com.google.Database-Example) - Download the resulting
GoogleService-Info.plistand replace the appropriate dummy plist file (e.g. in Example/Database/App/);
Some sample apps like Firebase Messaging (Example/Messaging/App) require special Apple capabilities, and you will have to change the sample app to use a unique bundle identifier that you can control in your own Apple Developer account.
See the sections below for any special instructions for those components.
If you're doing specific Firebase Auth development, see the Auth Sample README for instructions about building and running the FirebaseAuth pod along with various samples and tests.
To run the Database Integration tests, make your database authentication rules public.
To run the Storage Integration tests, follow the instructions in FIRStorageIntegrationTests.m.
Push notifications can only be delivered to specially provisioned App IDs in the developer portal. In order to actually test receiving push notifications, you will need to:
- Change the bundle identifier of the sample app to something you own in your Apple Developer account, and enable that App ID for push notifications.
- You'll also need to upload your APNs Provider Authentication Key or certificate to the Firebase Console at Project Settings > Cloud Messaging > [Your Firebase App].
- Ensure your iOS device is added to your Apple Developer portal as a test device.
The iOS Simulator cannot register for remote notifications, and will not receive push notifications. In order to receive push notifications, you'll have to follow the steps above and run the app on a physical device.
We've seen an amazing amount of interest and contributions to improve the Firebase SDKs, and we are very grateful! We'd like to empower as many developers as we can to be able to use Firebase and participate in the Firebase community.
Thanks to contributions from the community, FirebaseABTesting, FirebaseAuth, FirebaseCore, FirebaseDatabase, FirebaseMessaging, FirebaseFirestore, FirebaseFunctions, FirebaseRemoteConfig, and FirebaseStorage now compile, run unit tests, and work on tvOS, macOS, and Catalyst.
For tvOS, checkout the Sample.
Keep in mind that macOS, Catalyst and tvOS are not officially supported by Firebase, and this repository is actively developed primarily for iOS. While we can catch basic unit test issues with Travis, there may be some changes where the SDK no longer works as expected on macOS or tvOS. If you encounter this, please file an issue.
To install, add a subset of the following to the Podfile:
pod 'Firebase/ABTesting'
pod 'Firebase/Auth'
pod 'Firebase/Database'
pod 'Firebase/Firestore'
pod 'Firebase/Functions'
pod 'Firebase/Messaging'
pod 'Firebase/RemoteConfig'
pod 'Firebase/Storage'
- FirebaseAuth and FirebaseMessaging require adding
Keychain Sharing Capabilityto Build Settings. - FirebaseFirestore requires signing the gRPC Resource target.
See Roadmap for more about the Firebase iOS SDK Open Source plans and directions.
See Contributing for more information on contributing to the Firebase iOS SDK.
The contents of this repository is licensed under the Apache License, version 2.0.
Your use of Firebase is governed by the Terms of Service for Firebase Services.