* Adds passing state and continue URL in OOBCodes actions. (#82) * Adds actionCodeSettings class (#83) * Adds FIRActionCodeSettings class * Removes iOSAppStoreId to reflect update spec. * Adds “reset password in app” to sample app (#84) * Adds “reset password in app” to sample app * Addresses comments * Addresses comments * Adds @param documentation for actionCodeSettings (#85) Adds @param documentation for actionCodeSettings in FIRGetOOBConfirmationCodeRequest. * Adds request configuration class Adds a class that will comprise of all configurations needed to make a request to the Firebase Auth backend; including APIKey and Language code in the future. * Addresses comments. * Adds Setting Language Add Setting Language Feature to Firebase Auth. - Only adds support for two languages (English and Spanish) in this change. (Also supports two languages in test), more to come after this change is accepted. - For now sample app tests language setting only when using “reset password in app” option, the email sent will be in the current app language. Additional tests to come after change is accepted. * Amends code for unit tests Will add more comprehensive testing when code accepted. * Ecodes strings files in UTF-8 * Addresses comments * Addresses comments * Remove comments in .strings * Adds remaining TC languages to Firebase Auth. * Add line break to .strings files * remove language code english fallback Remove the fallback that sends “en” as the language code to the backend if no language code is specified. * addresses comment * Fixes FIRSecureToken Crash Integrates FIRSecureTokenService and FIRSecureTokenRequest with FIRAuthRequestConfiguration. * Addresses comment * Add auth language input Adds Auth language input to the Sample App in preparation for manual testing. * removes unnecessary comment * address comments * Add app language option Allow user to set the current app language code as the auth language code. This is in preparation for manual testing before release. * Addresses Comment * Adds missing continue URI Adds missing continue URL to Firebear error handling. * Remove unused line Removes unused line from FIRPhoneAuthProvider.m * Moves the new public header to the right place. * Fixes broken macOS build. * Removes trailing spaces. * Addresses review comments.
3.8 KiB
Firebase Auth Development
This directory contains a set of samples and tests that integrate with FirebaseAuth.
The Podfile specifies the dependencies and is used to construct an Xcode workspace consisting of the samples, modifiable FirebaseAuth library, and its dependencies.
Running Sample Application
In order to run this application, you'll need to follow the following steps!
GoogleService-Info.plist files
You'll need valid GoogleService-Info.plist files for those samples. 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.FirebaseExperimental1.dev) - Download the resulting
GoogleService-Info.plistand place it in Sample/GoogleService-Info.plist
GoogleService-Info_multi.plist files
This feature is for advanced testing.
- The developer would need to get a GoogleService-Info.plist from a different iOS client (which can be in a different Firebase project)
- Save this plist file as GoogleService-Info_multi.plist in Sample/GoogleService-Info_multi.plist. This enables testing that FirebaseAuth continues to work after switching the Firebase App in the runtime.
Application.plist file
Please follow the instructions in Sample/ApplicationTemplate.plist to generate the right Application.plist file
Sample.entitlements file
In order to test the "Reset Password In App" feature you will need to create a dynamic link for your Firebase project in the Dynamic Links section of the Firebase Console. Once the link is created, please copy the contents of Sample/SampleTemplate.entitlements into a file named Sample/Sample.entitlements and replace $KAPP_LINKS_DOMAIN with your own relevant appLinks domain. Your appLinks domains are domains that your app will handle as universal links, in this particular case you can obtain this domain from the aforementioned Dynamic Links section of the Firebase Console.
Getting your own Credential files
Please follow the instructions in Sample/AuthCredentialsTemplate.h to generate the AuthCredentials.h file.
Running SwiftSample Application
In order to run this application, you'll need to follow the following steps!
GoogleService-Info.plist files
You'll need valid GoogleService-Info.plist files for those samples. 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.FirebaseExperimental2.dev) - Download the resulting
GoogleService-Info.plistand place it in SwiftSample/GoogleService-Info.plist
Info.plist file
Please follow the instructions in SwiftSample/InfoTemplate.plist to generate the right Info.plist file
Getting your own Credential files
Please follow the instructions in SwiftSample/AuthCredentialsTemplate.swift to generate the AuthCredentials.swift file.
Running API tests
In order to run the API tests, you'll need to follow the following steps!
Getting your own Credential files
Please follow the instructions in ApiTests/AuthCredentialsTemplate.h to generate the AuthCredentials.h file.
Usage
$ pod update
$ open Samples.xcworkspace
Then select a scheme and run.