Repository navigation
[Bug]: App Store iOS 1.3.0 Usage shows zero instead of expected usage #14357
Description
Activity
Triage
This is a mismatch between the client's and the server's usage schema. App Store 1.3.0 still has the decoder from before the fix, so it rejects a current server's usage payload and the screen shows zeros.
The 1.3.0 binary is the Sep 21 build (
76cc9b08f). That client decodesserver.getUsageSummaryas contract v5, which only allows theclaude,codex, andgrokproviders and uses strictsourcesandbucketsarrays. A single unknown entry fails the whole response.Servers since merged PR #10409 (Sep 25, included in v0.0.44) report contract v6 and always send OpenCode and Antigravity sources, even when those directories are missing. The 1.3.0 app fails the request before it can read
contractVersion, so mobile merges nothing. The page shows$0.00,0tokens, and "No activity in this window" instead of staying on "Scanning provider transcripts…". The only sign of failure is the environment-menu subtitle, "Usage unavailable", so the zeros are easy to mistake for real usage.Merged PR #10076 skips unknown provider entries, but the fix has to ship in the client. Production over-the-air updates are gated by the native fingerprint. 1.3.0's runtime is
7572588241cbdd0aa67c03a44be31e7e7c628185, and the last update published for that runtime was on Sep 23, still on contract v5. The fingerprint then changed with 1.3.1 and later native changes, so #10076 never reached this binary, and checking for updates inside 1.3.0 won't pick it up. A newer 1.3.1 build that includes the fix was submitted on Sep 29 (d2c9281b8), and current production updates target that runtime (34c86f12…), not 1.3.0.Closed issue #9329 was the same failure, caused by a
groksource at the time, and #10076 fixed it. This report is the store build that never received that client fix. Open PR #14283 is separate: it explains contract-version mismatches in responses that did decode, and 1.3.0 never gets that far.On the phone, the environment menu on the Usage screen should say "Usage unavailable" for the connected machine. Desktop or web on the same server and period should still show the real totals. A server still on contract v5 wouldn't hit this.
Area
apps/mobile
Summary
In the official T3 Code iOS app from the App Store, version 1.3.0, Usage does not show the expected usage and instead displays 0. The screen is not stuck loading and does not loop. Observed after a recent app update.
Steps to reproduce
These steps describe the user-reported behavior; an independent device reproduction has not been performed.
Expected behavior
Show available usage for the selected period. If usage cannot be retrieved, distinguish that failure from genuine zero activity.
Actual behavior
The user reports that usage always displays zero. The supplied IMG_4138.png screenshot confirms the following visible state:
The screenshot confirms the displayed zero result, not why it occurs or the correct nonzero amount. The user reports this as incorrect; a same-period desktop comparison is still outstanding.
Version or commit
Official App Store iOS app 1.3.0. Exact build number, iOS version, host/server version, provider, connection type have not been captured. The supplied screenshot uses the 30-day period, Sep 1 to Sep 30. A same-period desktop comparison has not yet been performed.
Related report
#9329 reports a similar zero-usage symptom on older iOS builds and was closed as fixed by #10076. This report records the symptom on App Store 1.3.0; it does not assume the older root cause has returned. No exact open match was found in the issue search.
Workaround and evidence
No workaround established. The user supplied IMG_4138.png in the originating T3 Code conversation, and its visible contents were reviewed for this update. The image itself has not been uploaded to this GitHub issue. No logs supplied yet.