| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|\ |
|
| | |
|
|\| |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |/| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Created `Firestore_FuzzTests_iOS` Xcode target as a duplicate of the target
`Firestore_Tests_iOS`.
- Added `-fsanitize-coverage=trace-pc-guard` to the compiler flags to enable
code coverage by libFuzzer fuzzing driver.
- Modified the files to compile to the fuzz testing ones.
- Added a Principal testing class.
* Modified the `Podfile` to include `LibFuzzer.podspec` as a dependency for
the target `Firestore_FuzzTests_iOS`.
* Added a skeleton for fuzz testing. Currently does not test any code but
the fuzzing works fine and calls an empty `LLVMFuzzerTestOneInput`
with different input values.
- This means that fuzzing does not finish or crash.
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
|
|
|
|
| |
* Bump version numbers for 5.1.0
* Update push pods script for releasing SDKs.
* Fix Core library version string.
|
|
|
|
|
|
| |
* Move GoogleTest.podspec out of the Tests tree
* Rename GoogleTests to CoreTests
* Move CoreTests to the top-level
* Move FSTGoogleTestTests.mm into core/test
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Avoid direct use of generated umbrella headers
These:
* don't exist in static library builds
* have different names in multi-platform builds
* Only iOS targets depend upon Firebase/Core
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
* Update travis to use CocoaPods 1.5.2
* CODE_SIGNING_ALLOWED=YES
* Remove workaround and iPhone 8
* Remove #1210 static library Podfile workaround
* Add -all_load to Firestore Example so all C++ is available for tests
|
|\| |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Remove spurious dependencies on other project targets in the integration tests
* Integration tests don't depend on OCMock
... and shouldn't
* Integration tests don't directly depend upon leveldb either
* Flatten Firestore example Podfile
Make the targets independent in Firestore/Example/Podfile and add a
workaround to deduplicate dependencies.
* Project file output from running pod update
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
| |
* Rename targets:
* Firestore_Example to Firestore_Example_iOS
* Firestore_Tests to Firestore_Tests_iOS
* Firestore_IntegrationTests to Firestore_IntegrationTests_iOS
* AllTests to AllTests_iOS
* Rename associated schemes the same way
* Update Podfile to reference the new targets
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add Firestore_SwiftTests_iOS target to Xcode
* Add FirebaseFirestoreSwift podspec
* Add Firestore_SwiftTests_iOS to the Podfile
* Add CodableGeoPoint and tests
* Version FirebaseFirestoreSwift separately
|
| |
|
| |
|
|
|
|
| |
Updated the version numbers of pods which are being released in 4.8.1
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Make all FIRLogger functions extern "C"
* Make FSTIntegrationTestCase Objective-C++
Keep external interface to FSTIntegrationTestCase Objective-C
* Add explicit dependency on Firebase/Community/Core from Tests
This fixes a linkage error on a missing _FIRSetLoggerLevel symbol
|
|
|
|
|
|
| |
* Use GoogleTest as a dependency of Firestore_Tests
* Remove top-level leveldb-library from HEADER_SEARCH_PATHS
* Add string_util_test to the project and get it to build
* Implement FSTGoogleTestTests, a bridge between GoogleTest and XCTest
|
|
Initial release of Firestore at 0.8.0
Bump FirebaseCommunity to 0.1.3
|