* Update versions for Release 6.23.0
* Add FIAM to release manifest (#5383)
* Don't leak upload packages or deadlock on lifecycle events (#5382) (#5384)
* Don't leak upload packages or deadlock on lifecycle events
GDTCORUploadPackages would call targetToStorage in -initWithTarget. When this method was running during app terminate, this would cause a deadlock because calling targetToStorage is re-entrant while GDTCORRegistrar is sending lifecycle events to all the instances it's tracking.
NSTimer's invalidate method is also called whenever a package is completed, retried, or expired, without regard to the presence of a package handler.
A unit test is added to ensure that GDTCORUploadPackage's are not leaked by a retain
TSAN caught no issues
* Don't mark GDTCORUploadPackage -init as unavailable
Co-authored-by: Michael Haney <mikehaney24@users.noreply.github.com>
* FIAM bump podspec version to 0.19.3 (#5386)
* M69: add FIS. (#5412)
* M69: add FIS.
* Bump FIS version to 1.2.0
Co-authored-by: Michael Haney <mikehaney24@users.noreply.github.com>
* Update versions for Release 6.21.0
* Libraries should save state if a completion block is requested (#5147) (#5148)
* Libraries should save state if a completion block is requested
Currently, the onComplete block of sendXEvent:onComplete: is invoked when the event bytes are written to disk. However, if the app crashes before a lifecycle event occurs (trigger GDTCORStorage to serialize to disk), that event if effectively lost because the metadata has all been lost. This change triggers the saving of state of GDTCORStorage and prioritizers (if they implement it) if an onComplete block has been given.
* Remove RC from M67 (#5157)
* Revert "Migrate from using IID SDK for Remote Config to the new FIS SDK (#5096)" (#5156) (#5159)
This reverts commit 887ff82494.
* Only delete events when package was successfully delivered (#5172) (#5173)
* Only delete events when package was successfully delivered
* Add unit test to check that retrying a package delivery doesn't delete an event file
Co-authored-by: Michael Haney <mikehaney24@users.noreply.github.com>
Co-authored-by: Maksym Malyhin <mmaksym@google.com>
* Update versions for Release 6.18.0
* Forward declare class to fix linting. (#4935)
* Revert "Forward declare class to fix linting. (#4935)" (#4937)
This reverts commit 64bbf378bb.
* Update versions for Release 6.15.0
* Update podspec dependencies for M62 (#4640)
* Cherry-picks for M62. (#4650)
* Include GoogleUtilities in the release manifest.
* Crashlytics fix header import ordering issue (#4649)
Co-authored-by: Sam Edson <samedson@google.com>
Co-authored-by: Ryan Wilson <wilsonryan@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).
* 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
* Update versions for Release 6.9.0
* Fix unbalanced background task creation in GDTCCTUploader (#3838) (#3839)
* Add Manifest
* dependency version update
* Cherry picks for 6.9.0 (#3871)
* fixed "expiclitlySet" typo. (#3853)
* Mark unused variables (#3854)
* Mute FCM deprecated warnings with Xcode 11 and min iOS >= 10 (#3857)
* Add a third slash to make sure generated docs include these comments.b/13812238 (#3846)
* Update versions for Release 6.8.0
* RemoteConfig fix pod spec lint (#3715) (#3716)
* ABTesting: add protos to private headers.
* RemoteConfig: #import <FirebaseABTesting/ExperimentPayload.pbobjc.h>
* ./scripts/style.sh
* Remote Config `pod spec lint` fixes (#3717) (#3718)
* Fix ExperimentPayload.pbobjc.h imports
* RemoteConfig tests: add missing headers to spec.
* Revert ExperimentPayload.pbobjc.h import for ABTesting sources.
* Add FDL to M55 (#3724)
* Remove references to UIWebView from DynamicLinks to comply with Apple "ITMS-90809: Deprecated API Usage" (#3723)
* Add FDL to M55
* Fix accessing a destroyed object (#3721) (#3725)
This was caused by running under Asan with XCode 11. Apparently, previous versions of XCode cannot catch it (which is why Travis is passing, apparently).
Also:
* enable "Detect use of stack after return" option for Asan. AFAIU, it can only be enabled in the scheme. It's already enabled for unit tests, this PR additionally enables it for integration tests;
* make Asan failures fail Travis build. They were originally not considered blocking due to some sporadic failures. I haven't seen those for some time, and worst case scenario, we can revert this change.
* Cherry pick GDT changes for 6.8.0 and increment versions (#3770)
* Release 6.8.0: cherry pick of #3764 and #3766 (#3772)
* Gate access to cached instances. (#3766)
* Gate access to cached instances.
This is causing an issue in #3728. Hopefully this will fix it, but no
repro is available yet to test. There's still an underlying race
condition where a `creationBlock` could be called twice for a component
that is supposed to cache the instance returned, but that should be
addressed in a follow up PR.
* Review feedback.
* Iterate from array copy in `latestExperimentStartTimestampBetweenTimestamp:` (#3764)
* Release 6.8.0 cherry pick: conflicting Dynamic Links changelog changes. (#3790)
* Update FDL CHANGELOG (#3781)
* Issue number, not PR number (#3785)
* Implement CoreDiagnostics interop
For use by FirebaseCore.
Please pay special attention to the changes in FIRApp, I've replaced passing FIRApp in the notification with a data object that will eventually replace the same information that FIRDiagnostics extracted.
* Add CoreDiagnosticsInterop to the Example Podfile
* Style and xcodeproj updates
* Update Podfiles that dep on FirebaseCore
So that they also have a dep on FirebaseCoreDiagnosticsInterop
* ran pod deintegrate to remove unintended xcodeproj changes
* Fix Podfile paths
* Add FCD to if_changed and travis.yml
* Fix building with Firestore
* Style
* Whitespace
* Fix a changed internal API
* Make pod paths consistent
* Restore connectivity_monitor_noop.cc style
* Remove logging prior to [FIRApp configure]
Also remove sendLogsWithServiceName:version:
* style
* Remove nil checks from diagnostics data
* Put back some deleted symbols
* Restore the sendLogsWithServiceName:version: method, but as a no-op
* Restore the original version of sendLogs...
* Allow an unused parameter
* Remove obsolete nsnotificationcenter related stuff
* Whoops, missed the header change.
* Final changes to support FIRCoreDiagnostics
These changes are necessary because FIRCore has a hard dep on FIRCoreDiagnostics (FIRCD) and FIRCoreDiagnosticsInterop.
Components can't be used because FIRCD would need to have a hard dep on FIRCore to get access to FIRLibrary, FIRComponent, FIRComponentContainer, and FIRComponentCreationBlock and this would create a dep cycle. So, an extern has been put into the interop lib and the variable is implemented in the connector class inside of FIRCore, but it's unset. FIRCD actually sets that variable in +load, allowing use of FIRCD.
FIRCD can also be removed as a dependency with no ill effect by end users setting the environment variable DISABLE_FIREBASE_DIAGNOSTICS=1
* Add nanopb and project generation infrastructure
* Convert FIRCoreDiagnostics to canonical nanopb, and move to OSS.
* Remove custom build steps for CoreDiagnostics
* Addressing review comments
* Update versions, tags, and port the relevant unit tests for FIRCD
* Version and platform fixes
* Fix podspec expected tags
* A hack to solve a chicken-and-egg problem with pod lib linting.
* Heartbeat implementation
* FIRDiagnosticsDateFileStorageTests
* Fix tests for non-iOS platforms
* Heartbeat tests
* Fix initialization.
* Cleanup Installation ID.
* Fix testProtoPopulation.
* Merge conflict fix
* Typo fix.
* Remove FIRCore dep from FIRCD unit tests and move symbols to interop
* Run ./scripts/style.sh
* Typo
* #ifdef comment
* File license header.
* Import FIRDiagnosticsDateFileStorage.h using relative path.
* FIRDiagnostics -> FIRCoreDiagnostics
* Docs syntax
* Docs
* Docs typo
* Add shared variables to the interop lib
I know this goes against the convention, but it's actually the only way to resolve this very unique problem.
* Fix comment
* Style
* Removed lib version passing.
* Remove env checking for conditional deps
* Style
* Address whitespace issues
* Add copyright notice
* Add new deps to Podfiles
* Fix trailing space
* Some changes to fix working in an extension.
* Fix type in Podfile
* GDT: begin/end background task only for iOS and TVOS applications.
* Fix typo
* Style
* Stop sharing kFIRService strings across pods
* Travis test
* Change all TARGET_OS_TVOS macros to TARGET_OS_TV
TARGET_OS_TVOS doesn't exist.
Also macro out a UIApplication reference.
* style
* Update all Podfiles with deps on FIRCore
* Fix trailing whitespace
* Update Firestore cmake
* Fix FIAM build break (#3254)
* Additional cmake changes
* Fix linker issue with deprecated CoreDiagnostics (#3257)
* Adding more deps to cmake
* Fix linker error (#3266)
* Rerun only IAM tests
* whitespace
* No xcpretty or frameworks run
* Fix typo
* Revert "No xcpretty or frameworks run"
This reverts commit afc1abba37.
* Revert "whitespace"
This reverts commit fd06955a56.
* Revert "Rerun only IAM tests"
This reverts commit 98ce07600f.
* Run travis on this branch
* Add support for expanding PODS_TARGET_SRCROOT in CMake (#3267)
* Fix a few things that should have been splatted but weren't
* Define PODS_TARGET_SRCROOT in CMake for compatibility with CocoaPods
* Compile pods we depend upon with looser settings
* Rename the nanopb dependency to match what CMake actually has
* Make #include <nanopb/pb.h> work
Remove the old way of #include <pb.h> once we change the Firestore
nanopb generator to match.
* Fix warnings that fail the build
* Remove typed enum and fix a comment.
* Fix an import
* Change a line so it's not altered by Copybara
* More changes to stop copybara from altering the wrong sources
* Remove trailing whitespace
* Fix copybara modifying python.
* Add additional field in firebasecore.proto (#3273)
* Remove the dependency on interop to populate a shared variable.
* style
* Create travis jobs for FirebaseCoreDiagnostics (#3245)
* Create travis jobs for FirebaseCoreDiagnostics
And update the pod lib lints for GDT.
Remove the mph-master branch before merging to master.
* Add support for FIRCD to if_changed.sh
* Adjust tests
* Unavailable init methods should not be nullable (#3276)
* Allow firestore api to work with Codable objects + ExplicitNull + Integration tests (#3261)
* Convinience api for codables
* Integration Tests
* ExplicitNull implementation
* Update to CocoaPods 1.7.3 (#3280)
* Import GULLoggerLevel.h via public framework header (#3277)
* Put the need to include Firestore/Source/Public in the podspec (#3288)
This removes the need to munge the pods project after the fact and makes
it so that customers can click through to our headers too.
* Ensure Storage initializer doesn't get called (#3294)
* FIROptions.appGroupID introduced (#3293)
* Use a consistent set of dependencies on all platforms (#3289)
* Use a consistent set of dependencies on all platforms
* pod install for uniform dependencies
* Store the coerced base value in the BaseMutation (#3292)
* In card message: set the text color on the body text view (#3286)
* In card message: set the text color on the body text view
* Fix bug where card messages in test app were showing up with two of the same buttons
* Revert change to text color
* [docs] add missing semicolon (#3305)
Add missing semicolon to code example
* Add explicit Foundation import. (#3309)
This is causing issues when building an XCFramework.
* Pass the correct compiler flag for CoreDiagnostics. (#3312)
* Pass the correct compiler flag for CoreDiagnostics.
When CoreDiagnostics is open sourced, we'll need to ensure that the
right compiler flag is passed. This doesn't add support for Carthage yet
but allows the frameworkbuilder to pass the flag for carthage as well.
An update to the zipbuilder to allow for carthage will follow shortly.
* Remove accidental change.
* Fix and rewrite sync_project.rb (#3296)
* Fix and rewrite sync_project.rb
Ever since we added multiple platforms, removing a file has been broken.
This fixes that issue.
Also, rewrite target synchronization to make more sense. Essentially now
there's one diff between the filesystem and the groups and then an
explicit diff is done between project files and target contents.
* Run sync_project.rb on post-install
* pod lib linting should output something every minute while running
* DEBUG: This commit should be reverted
* DEBUG: This commit should be reverted
* DEBUG: This commit should be reverted
* Remove mph-master from travis
* Fix constant name conflic between old and new diagnostics (#3329)
* Rename kFIRDiagnosticsHeartbeatDateFileName -> kFIRCoreDiagnosticsHeartbeatDateFileName to avoid conflicts with FIRDiagnostics.
* Travis: temporary add `mph-master` to run tests.
* Rempve mph-master again
* Fix imports in FIRCDConnector
* Fix another import
* Fix yet another import
* Attempt to read crashing test logs from disk
* Implement printing of failed/crashed test logs.
* Print only crashed tests, rmdir between runs
* Revert reading crashing log changes
* Write CHANGELOG for all new FIRCD associated libraries
* Change all GUL deps to >= 6.2
* Revert ZipBuilder changes and do some last bits of cleanup
* Remove an assertion and populate an error instead
* Update versions for Release 6.3.0
* Revert "Raise exception when log into Facebook using OAuth. (#3138)" (#3208) (#3209)
This reverts commit 393d060710.
