Now, we use the re-worked nanopb deserializer (that mallocs). This also
had the advantage of moving the C++ serialization code closer to the
other platforms.
Still TODO:
- Reorder the methods within the files to resemble the other platforms.
* Update versions for Release 5.15.0
* Create 5.15.0.json
* Update CHANGELOG for Firestore v0.16.1 (#2164)
* Update the name of certificates bundle (#2171)
To accommodate for release 5.14.0.
* Fix format string in FSTRemoteStore error logging (#2172)
* Update CHANGELOG.md
* Update 5.15.0.json
gRPC-C++ versions up to and including 0.0.3, and also 0.0.5, don't bundle `roots.pem` in the podspec. gRPC-C++ 0.0.4 and, presumably, the currently not-yet-released 0.0.6 do. Firestore currently also bundles this file under the same bundle name, which leads to build errors when both Firestore and gRPC-C++ try to add the file into the build (only shows during archiving).
For transition, this PR:
* renames the Firestore bundle to avoid naming clash;
* changes the loading code so that it first tries to load certificates bundled with gRPC-C++ (versions 0.0.4 and 0.0.6+), but falls back to those bundled with Firestore if necessary.
At a later point, Firestore should be changed to not bundle the certificates altogether.
* 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
* Revert "Revert "gRPC: replace Objective-C implementation with the new C++ implementation (#1968)" (#2030)"
This reverts commit ea567dca47.
* gRPC: fix bugs found during testing (#2039)
All in `GrpcStream`:
* make sure there are no pending completions when "finish" operation is enqueued;
* always finish gRPC calls;
* when connectivity changes, reset not just the calls, but the underlying channel as well.
* Revert "Partially revert "Update CHANGELOG for Firestore v0.14.0 (#2025)" (#2031)"
This reverts commit b2437b80f6.
* Update changelog for v0.15.0.
* gRPC: add gRPC wrapper classes to CMake build (#2015)
* add a C++ equivalent of `FIRFirestoreVersionString`. This eliminates the only Objective-C dependency of `grpc_connection.mm` and allows making it a pure C++ file;
* open-source `binary_to_array.py` script and use it in the build to embed `roots.pem` certificate file from gRPC into the Firestore binary. The embedded char array is then used to load certificate at runtime.
* Revert local change -- do not enable sanitizers by default
* Update abseil-cpp to a new upstream
Update to 7990fd459e9339467814ddb95000c87cb1e4d945 master@{2018-11-06}
* Re-apply -Wcomma fix
* Update add_subdirectory for Abseil
* Remove references to Firestore/Port (which longer exists)
* Fix ABSL_HAVE_THREAD_LOCAL when targeting iOS 8 in Xcode 10
* Clean up abseil warnings
* Clean up a Firestore format string warning.
* Exclude third_party/abseil-cpp from whitespace checks
* 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
* Add C++ namespaces and use C++ linkage for nanopb-generated sources.
* Regenerate nanopb sources as C++
* Add generated C++ nanopb sources to the podspec
* add support for SSL disabled to `GrpcConnection` (unfortunately, there
currently is no way to verify this change actually works);
* make gRPC calls using the C++ implementation:
* make `FSTRemoteStore` create C++ streams instead of their Objective-C
counterparts;
* port https://github.com/firebase/firebase-js-sdk/pull/1041: streams
are now never recreated, only restarted;
* make `FSTDatastore` delegate server calls to the C++ implementation;
* port `MockWatchStream` and `MockWriteStream` to C++ (`FSTMockDatastore` is
still in place, because `Datastore` is not fully ported yet);
* no longer generate Objective-C gRPC service definitions from protos;
* remove all references to Objective-C gRPC client;
* check in gRPC root certificates file and load it at runtime (the check-in part
is temporary until gRPC-C++.podspec provides the certificate). This makes SSL
work.
The reachability state is not (yet) used to determine whether it's possible to reconnect; rather, the its only use is to quickly end any existing connections. The benefit is potentially quicker reaction to network being disconnected than it would take for the connection to time out.
These pods depend on FirebaseCore's interop APIs that were introduced
in FirebaseCore version 5.1. This wasn't picked up before since
CocoaPods automatically matched the largest minor version available but
the podspec should accurately represent the version requirements.
Add a dependency on GRPC to XCode build, and add a simple helper class that is intended to help GrpcStream (forthcoming) to avoid issuing several write operations in a row (which would crash GRPC due to a failed assertion).
* Add a POSIX filesystem implementation
* Add a Win32 filesystem implementation
* Reimplement RecursivelyDelete with IsDirectory returning Status
* Remove the Apple-specific filesystem
Making this consistent with POSIX and Win32 is gratuitously difficult
and just not worth it, when the POSIX code runs perfectly well on Apple
platforms.
* Move Firestore to Auth interop library.
* Fixed TODO with no name.
* Extract interop into separate class.
* Further Firestore interop changes.
* Move auth instance to constructor of CredentialsProvider.
* Resolved travis failures.
* Create separate queue for FIRApp instances, remove dead test code.
* Add missing <string> import.
Also "fixed" BadFieldValueTagWithOtherValidTagsPresent test by changing
'false' to 'true'. Details: Depending on the version of nanopb, nanopb
would explicitly encode 'false', which shouldn't be done in proto3. When
it's explicitly encoded, the test worked properly. But when it was
(properly) dropped, the invalid tag is the only field that's actually
encoded, thus violating the assumptions of the test, leading to a test
failure. s/false/true fixes it, as now the boolean_value field is
(properly) encoded regardless of version.
This involves:
- building c++ libprotobuf (rather than just the obj-c version).
- adding c++ libprotobuf, c++ built protos (previously created) to the
*test suite* only (not to the main build).
- modifying existing nanopb CFLAGS to match those that are indirectly
pulled in.
rsgowman