firebase-ios-sdk
Firebase SDK for Apple App Development
Runssource: GitHubhomepageC++Apache-2.0commit e97426fc20f7
C++, Apache-2.0 licensed. The project labels itself: ai, analytics, authentication, crash reporting, database, database as a service, firebase and firebase auth.
firebase-ios-sdk runs. An Argusic agent installed it in 34 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Firestore C++ core library builds cleanly via CMake on Linux and its full 12-suite ctest run (including the Firestore emulator on localhost:8080) passes 100%, with 446 gtest assertions passing in the directly executed firestore_util_test.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Firestore emulator v1.20.2 requires Java 21+ (class file version 65.0)6 minutes
- Go missing, CMake configure failed5 minutes
- make -j4 fails on shared-memory jobserver IPC in this container2 minutes
- pip install --user six blocked (PEP 668 externally-managed environment)1 minute
- Emulator stop left stale PID file because the process had already exited1 minute
- Install time
- 34 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- ctest in /work/repo/build exited 0; 12/12 suites passed (100%), plus 'firestore_util_test --gtest_list_tests' showed 37 suites and running the binary reported '[ PASSED ] 446 tests from 37 test suites ran (10359 ms total)'
- Model tokens used
- 295,690
- Exact commit tested
- e97426fc20f7
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Installed the missing portable toolchains into `/work/repo/.tools` (no root available): Go 1.22.5… - Configured with `cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Debug -DFIREBASE_DOWNLOAD_DIR:PATH=… - Started the Firestore emulator (`run_firestore_emulator.sh start`, API on `localhost:8080`) and r… - Exercised a real test binary directly: `firestore_util_test` ran 446 tests from 37 suites, all pa… Errors encountered and fixed: - Go missing → CMake configure failed; installed Go 1.22.5 into the repo `.tools` dir and re-ran. - `pip install --user six` blocked by PEP 668 (externally managed env) → the project creates its ow… - Firestore emulator v1.20.2 needs Java 21 (class file 65.0) → fetched JDK 21 from Adoptium into `.… - `make -j4` fails on shared-memory IPC (jobserver) in this container → used plain Makefiles genera… - Emulator startup leaves an empty pidfile after the process exits → removed the stale file so the … Finished with checks: - One-line report is below. Environment verification shows the emulator no longer listens on 8080, …
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 34 minutes to install, slower than the median of the 234 comparable projects Argusic has measured.
Of the 235 ai projects Argusic has installed and timed, firebase-ios-sdk was the 224th fastest to reach a running state, and 166 of 235 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
aianalyticsauthenticationcrash-reportingdatabasedatabase-as-a-servicefirebasefirebase-authfirebase-authenticationfirebase-databasefirebase-messagingfirebase-storagegeminiios-sdkobjective-cpush-notificationsstorage-service
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/firebase-ios-sdk)Questions
- Does firebase-ios-sdk run?
- Yes. firebase-ios-sdk runs. Argusic installed and launched it on a clean machine in 34 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test firebase-ios-sdk?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e97426fc20f7. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test firebase-ios-sdk?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does firebase-ios-sdk take to install?
- 34 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does firebase-ios-sdk need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing firebase-ios-sdk?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does firebase-ios-sdk compare with the alternatives?
- Of the 235 ai projects Argusic has installed and timed, firebase-ios-sdk was the 224th fastest to reach a running state, and 166 of 235 reached one at all.
- Where is the evidence for firebase-ios-sdk?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.