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 51.8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
CMake superbuild for Firestore C++ core configures and builds all external dependencies (gRPC, Abseil, BoringSSL, leveldb, nanopb, protobuf, snappy, zlib, c-ares, re2) and links the firestore_core static library and 12 unit test executables. All 12 C++ unit tests pass on Linux x86_64 with GCC 13.
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.
- GCC 13 false-positive -Werror=maybe-uninitialized on Firestore/core/src/core/query.cc:319 causing build failure at 93%11.5 minutes
- Install time
- 52 minutes
- Cold machine to finish
- 54 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- ctest in build directory exited 0, 12/12 tests passed: firestore_types_test, api_test, bundle_test, credentials_test, core_test, immutable_test, index_test, local_test (24s), model_test, nanopb_test, remote_test, util_test. Total test time 31.2s.
- Model tokens used
- 330,443
- 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.
],
'test_depth': 'tier1_real',
'notes': 'firebase-ios-sdk is an Apple-platform SDK (Swift/Obj-C). No Xcode/macOS on Linux. Used …
'verified_how': 'ctest in build directory exited 0, 12/12 tests passed: firestore_types_test, api…
'final_state': 'CMake superbuild for Firestore C++ core configures and builds all external depend…
}
print(json.dumps(result))
\"" in /work/repo
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 51.8, "errors": [{"msg": "…
tokens used
330,443Replay 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 1 error 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.
What did not, or is not known
- Took 51.8 minutes to install, slower than the median of the 58 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 59 ai projects Argusic has installed and timed, firebase-ios-sdk was the 58th fastest to reach a running state, and 45 of 59 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 52 minutes, hitting 1 error 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. One attempt is 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.18: 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?
- 51.8 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?
- 1 thing broke in the recorded run, and 1 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 59 ai projects Argusic has installed and timed, firebase-ios-sdk was the 58th fastest to reach a running state, and 45 of 59 reached one at all.
- Where is the evidence for firebase-ios-sdk?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.