* Update versions for Release 5.13.0
* Revert premature api changes (#2097)
* Revert "Add warning for deprecated API to indicate that the passed in domain name's scheme will deduced as https (#2078)"
This reverts commit ceb839293e.
* Revert "Allow setting the domainURIPrefix for custom domain names/paths when creating dynamic links (#2071)"
This reverts commit d917bac047.
* Revert "Minor edits: change domain names in test app plist, fix warnings."
This reverts commit 15f5d46807.
* Revert "Fix style. Run ./scripts/style.sh"
This reverts commit 0e16e6c863.
* Revert "Allow for custom domains in the FDL iOS SDK"
This reverts commit 5e33153f70.
* Version is still 3.2.0
* Update versions for Release 5.12.0
* Add missing nanopb flag
* Isolate Firestore nanopb messages in C++ namespaces (#2046)
* Add C++ namespaces and use C++ linkage for nanopb-generated sources.
* Regenerate nanopb sources as C++
* Add generated C++ nanopb sources to the podspec
* Version bumps for Firebase 4.10.1 (#891)
* Minimal fix for b/74357976 (#890)
Fixes b/74357976 which caused unauthenticated users to be unable to reach the Firestore backend and updates the changelog.
* Copy all C++ strings to NSString where they're not obviously safe (#893)
This fixes a known instances of memory corruption where in
FSTLevelDBMutationQueue, the NSString view was retained for later, and
the incorrect user was used, causing b/74381054.
gRPC does not necessarily copy its string argumnets and if our hostname
were configured to a non-default one it's possible that we could corrupt
the host cache too.
All remaining usages of util::WrapNSStringNoCopy are obviously safe:
passed into logging or other known transient usages.
* fix lint
* Deprecate FIRAppEnvironmentUtil sharedApplication
* Remove sharedApplication private API.
This also allows us to remove an AppKit dependency.
* Disable autolink when building FirebaseCore (#606)
This prevents the dependencies of FirebaseCore's dependencies from
bleeding into its interface.
The proximate benefit of avoiding this is that FirebaseCore no longer
ends up depending on ColorSync.framework which became a top-level system
framework in 10.13. This makes it possible to build against the
resulting FirebaseCore.framework on macOS 10.12 using Xcode 9 (with the
macOS 10.13 SDK).
Ryan Wilson