* FIS: Throw exception on incomplete Firebase config.
* API docs updated.
* FirebaseInstallations bump minor version: 1.1.0
* Fix tests
* Text fixed
* Make exception message more informative
* Fix Remote Config tests.
* Tests updated to use GCMSenderID if projectID is not available.
* Use `GCMSenderID` when `projectID` is not available.
* ./scripts/style.sh
* Comments
* GCMSenderID and projectID validation updated.
* Comment
* FirebaseInstallations: version bump to 1.0.1.
* FIS changelog
* FirebaseInstallations: version bump to 1.1.0
* FIS and Core changelogs.
* Changelogs remove GCMSenderID
* Typo
* Typo
* fix link
* Revert Core changelog
* FIS changelog fix.
* InstanceID integration tests
* ./scripts/style.sh
* Travis: run install_prereqs.sh for IID
* install_prereqs.sh: run `install_secrets` for IID
* Flag to disable IID integration tests
* Travis: IID disable integration tests for forks.
* ./scripts/style.sh
* Temporary disable IID test due to b/147102327
* Travis: IID integration tests enabled for all IID builds.
* Firebase Installations: Instance ID now uses FIS under the hood. (#3398)
* Fix merge errors
* Use modular import for FIRInstanceID_Private.h
* Use modular imports for FirebaseInstanceID.h (#3509)
* Changes missing during the fix.
* Changes missing during merge.
* Fix header import.
* ./scripts/style.sh
* Fix FCM tests. (#3888)
* Fix IID FCM token check.
* FirebaseInstallation: merge master into FIS integration branch (#4076)
* Fix IID FCM token check.
* Unused constant deleted.
* FCM tests: fix bad merge.
* Remote Config test app: use local IID and FIS. (#4089)
* token request should pass through if token is not fresh (#4104)
* Merge errors fix.
* IID with FIS: send FIS auth token with IID token request (#4152)
* FIRInstanceIDTokenOperation: add FIS auth token to the IID token request.
* IID tests: don't use FIS private headers.
* IID: indication of compatibility with FIS (#4262)
* FIS: IID incompatible version exception.
* FirebaseInstallations.podspec: set preprocessor flags based on env vars.
* FIS Travis: set required env vars
* /scripts/style.sh
* IID: method to indicate FIS usege added.
* FIS: FIRInstantiationTimingEagerInDefaultApp
* FIS: FIRInstantiationTimingAlwaysEager
* IID: make compatibility method static.
* Make -[FIRInstanceID appInstanceID:] safe to be called from any thread (#4482)
* IID: use a cached value of FID for -[FIRInstanceID appInstanceID:]
* TODO comment
* TODO updated
* FirebaseInstallations: prepare IID with FIS dependency for release (#4522)
* Bump FIrebaseInstallations to 1.0.0
* Travis: remove mm/fis-integration-master branch
* Travis: if_changed script updated to reflect IID dependency on FIS.
* Revert "Travis: remove mm/fis-integration-master branch"
This reverts commit 534dff990a.
* Travis: remove mm/fis-integration-master branch (#4526)
* Formatting and spelling.
* Firebase example proj: pod deintegrate
Co-authored-by: Chen Liang <chliang@google.com>
* Add "swift-runtime/true" to user agent when Swift detected.
* Use "swift" instead of "swift-runtime"
* ./scripts/style.sh
* Add comment with the Swift check clarification
* Fix bridging header path
* Fix SwiftObject class name for old Siwft versions.
* Add swift runtime flag with value true or false (to be able to distinguish from a no-value-provided case).
* Allow multiple `configure` calls in an extension.
Some extensions have an entry point that gets called multiple times.
Instead of having to check if a default app has already been configured,
allow multiple `configure` calls if and only if it's in an extension and
the FIROptions contents are identical.
* Review comments.
* Updated comment.
Add +[FIRServerValues increment:]
* Definition is currently in an "unreleased" extension to FIRServerValues
* Functions that resolve server values now need access to any existing snapshot; please help ensure that this is not done wastefully.
* Tests are added to FData.m
* Setting increment values
* Setting increment priorities
* Type coercion
* Overflows
* Some tests are renamed to make it clear that ServerValues != timestamps
* Fix container instantiation timing, IID startup.
The container instantiation could happen at the wrong time, before all
components have been added to the container. This fixes it, and also
moves IID to use the proper instantiation timing instead of relying on
the `configureWithApp:` call. This is part continuation of #3147, where
I'll be fixing the rest of the SDKs in follow up PRs.
* Typo
* Further work on instantiation timing.
This moves the instantiation of components to after the FirebaseApp is
completely configured and assigned, as it should be. This also exposed
a recursive issue with IID calling the Messaging singleton, which in
turn called IID and instantiated multiple instances.
A change was made to break the cycle: the Messaging `isAutoInitEnabled`
call was changed to a static method vs an instance method, allowing IID
to call it during initialization without instantiating the Messaging
instance (since it doesn't have a direct dependency on it).
* Revert unintentional formatting of entire FIRMessaging file.
* Fix tests.
* Format InstanceID.m
* Remove unused import.
* Fix ComponentContainer test.
* Minor PR feedback.
* Update versions for Release 6.10.0
* Cherrypick #3983 and include Database in release. (#3986)
* Remove log argument that causes SocketRocket crash (#3983)
* Add FirebaseDatabase to release.
* Update CHANGELOG with version.
* Cherrypick for #3984 along with CHANGELOG update. (#3988)
* Fix race condition in FIRComponentContainer instance creation (#3984)
* Fix race condition in FIRComponentContainer instance creation
Reported in #3967. Users sometimes seeing a crash when multiple threads
concurrently try to create Firestore instances. By inspection I found
that there's a race here where two threads can check for presence in the
cache, see nothing, proceed to creation, both store a value in the cache,
and both return their copies. This would lead to two Firestores being
created for a single App.
This replaces `dispatch_sync` on a serial queue with good old
`@synchronized` blocks. `dispatch_sync` will self-deadlock if called
from a thread already on the queue while `@synchronized` allows
recursion.
No new tests are added because several tests like
`testDependencyDoesntBlock` already cover this case.
* format
* Update Core CHANGELOG
* Update Core CHANGELOG again
* Fix merge from CHANGELOG
Chen Liang