This repository contains a subset of the Firebase iOS SDK source. It currently includes FirebaseCore, FirebaseAuth, FirebaseDatabase, FirebaseMessaging, and FirebaseStorage.
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.
This repo contains a fully functional development environment for FirebaseCore, FirebaseAuth, FirebaseDatabase, FirebaseMessaging, and FirebaseStorage. By following the usage instructions below, they can be developed and debugged with unit tests, integration tests, and reference samples.
Note, however, that the resulting FirebaseCommunity pod is NOT interoperable with the official Firebase release pods because of different pod dependency definitions.
Instructions and a script to build replaceable static library frameworks at BuildFrameworks. The resulting frameworks can be used to replace frameworks delivered by CocoaPods or the zip distribution for development.
$ git clone git@github.com:firebase/firebase-ios-sdk.git
$ cd firebase-ios-sdk/Example
$ pod update
$ open Firebase.xcworkspace
Select a scheme and press Command-u to build a component and run its unit tests.
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 AuthSamples/README.md 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.
Note that if you are using CocoaPods and using the FirebaseCommunity podspec (the one in this repo), you cannot bring in Pods from the official Firebase podspec, because of duplicated symbol conflicts. If you're not using one of the open-source SDKs in this repo for development purposes, we recommend using the regular Firebase pods for the best experience.
To get started using the FirebaseCommunity SDKs, here is a typical Podfile:
use_frameworks!
target 'MyAppTarget' do
platform :ios, '8.0'
pod 'FirebaseCommunity/Database'
end
- Replace
MyAppTargetwith the name of the target in your Xcode project. - Specify the subspec in the pod specification for each Firebase component wanted. Database is used in the example above. Storage, Auth, and Messaging are other options.
FirebaseAuth, FirebaseCore, FirebaseDatabase and FirebaseStorage now compile, run unit tests, and work on macOS, thanks to contributions from the community. There are a few tweaks needed, like ensuring iOS-only or macOS-only code is correctly guarded with checks for TARGET_OS_IOS and TARGET_OS_OSX.
Keep in mind that macOS is 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. If you encounter this, please file an issue for it.
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.