|
|
%!s(int64=6) %!d(string=hai) anos | |
|---|---|---|
| .. | ||
| Example | 77f92cd2c6 Stop using built-in CMake Framework support (#5316) | %!s(int64=6) %!d(string=hai) anos |
| Protos | a568a96f7e Add iOS build support to the CMake build (#5052) | %!s(int64=6) %!d(string=hai) anos |
| Source | 77f92cd2c6 Stop using built-in CMake Framework support (#5316) | %!s(int64=6) %!d(string=hai) anos |
| Swift | b90ddf1339 Limit Swift line lengths to 100 (#5315) | %!s(int64=6) %!d(string=hai) anos |
| core | c056540052 Replace a hard assert with a call to UpdateTrackedLimboDocuments. (#5363) | %!s(int64=6) %!d(string=hai) anos |
| fuzzing | 2e7122cadd Fix fuzz build (#5069) | %!s(int64=6) %!d(string=hai) anos |
| third_party | b90ddf1339 Limit Swift line lengths to 100 (#5315) | %!s(int64=6) %!d(string=hai) anos |
| CHANGELOG.md | 4f01818bb3 Update Firestore changelog for M68 (#5281) | %!s(int64=6) %!d(string=hai) anos |
| CMakeLists.txt | 2a8d069b77 Run integration tests from CMake on mac (#4276) | %!s(int64=6) %!d(string=hai) anos |
| README.md | 62ef244cde C++ migration: remove the dependency on Objective-C `Protobuf` library (#4189) | %!s(int64=6) %!d(string=hai) anos |
| test.sh | 5930ad2fee Factor out a universal build script (#884) | %!s(int64=8) %!d(string=hai) anos |
Set up a workspace via CocoaPods
$ cd Firestore/Example
$ pod update
$ open Firestore.xcworkspace
Select the Firestore_Tests_iOS scheme
⌘-u to build and run the unit tests
GoogleServices-Info.plist
file in Firestore/Example/App.Note: this does not give full coverage, but is much faster than above. b/hotlists/1578399 tracks outstanding issues.
GoogleServices-Info.plist is back in its default state (git
checkout Firestore/Example/App/GoogleServices-Info.plist).Install the Firebase CLI. Essentially:
npm install -g firebase-tools
Install the Firestore emulator. Essentially:
firebase setup:emulators:firestore
Run the emulator
firebase serve --only firestore
In Xcode select the Firestore_IntegrationTests_iOS scheme
⌘-u to build and run the integration tests
Typically you should not need to worrying about regenerating the C++ files from the .proto files. If you do, see instructions at Protos/README.md.