googledeveloper: unclaimed Ultra credit (null remaining amount) fails with "unrecognized response" instead of "Not applied"
Los mantenedores suelen responder en 1 día
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 28/100
Línea de trabajo
Read the googledeveloper provider source together with docs/googledeveloper.md, then follow the benefit-19 parsing path where the "Not applied" branch checks only offer[6] before money(billing[1]) reaches the array(null)/invalid() helpers. The failing state is [["USD",100], null, "", 5, 2], so the fix treats a null or missing billing[1] as unapplied alongside a null offer[6], and updates the misleading docs sentence about credits having no money fields. Done means a refresh on an unclaimed Ultra account shows Status: Not applied instead of "fetch failed". Note the linked pull request already covers this, so check it before starting.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
The Google Developer Program provider shows "fetch failed" (parse failure, "Google Developer Program returned an unrecognized response") for a Google AI Ultra account whose monthly Gen AI & Cloud credit is granted but not yet claimed, because no Google Cloud billing account exists yet. The documented behavior for an unapplied credit is Status: Not applied, which is not an error.
Steps to reproduce
- Sign in to a Google AI Ultra account that has the $100 monthly Gen AI & Cloud credit but no Google Cloud billing account (https://me.developers.google.com/benefits shows "To activate and claim your credit, first set up a Google Cloud billing account" and "Billing account: No billing accounts available").
- Enable the Google Developer Program provider with automatic browser cookie import (or a manual cookie header).
- Refresh the provider.
Expected behavior
The menu card shows Status: Not applied with the pointer to me.developers.google.com/benefits, as documented in docs/googledeveloper.md.
Actual behavior
The refresh fails with a parse failure ("unrecognized response") and the menu shows "fetch failed".
Cause, from the response shape (values reduced to types, nothing account-specific): the benefit-19 offer array has a non-null offer[6], so the existing "Not applied" branch (which only checks offer[6] null or undefined) is skipped. That billing array is [["USD",100], null, "", 5, 2]: the granted amount is present, the remaining amount (billing[1]) is null, and the billing account (billing[2]) is an empty string. money(billing[1]) then calls array(null), which calls invalid() and throws. The cookies and the RPC are fine: the page GET and the Ro0AYc POST both succeeded before the throw.
The docs sentence "A credit that is not applied ... has no money fields" and the matching code comment are wrong for this state: the granted amount is present.
A fix is in the linked pull request: treat a null or missing billing[1] as unapplied, like a null offer[6].
Environment
- CodexBar 0.85.0, built from main at c94b855 on a fork
- macOS
- Google AI Ultra account with the monthly credit unclaimed (no Cloud billing account)
- Provider
googledeveloper, browser cookie session
Prior art
Searched steipete/CodexBar issues and PRs (open and closed) for: googledeveloper, Google Developer Program, Not applied, unrecognized response, billing account credit, Gen AI Cloud credit, Google AI Ultra, Cloud credits. Nearest threads, none covering this:
- #5033 (closed) Show Google Developer Program monthly Cloud credits from Google AI Pro and Ultra
- #5035 (merged) feat(providers): add Google Developer Program credits
- #5106 (closed, not merged) fix(googledeveloper): fall through signed-in profiles without Cloud credits (a different case: profiles with no credit at all)
- No open issue or PR for the googledeveloper provider.
Observation only: a bad shape on the first account stops the account walk through return invalid(), so authuser=1 and later are never tried.
- Lenguaje dominante
- Swift
- Estrellas
- 23.3k
- Forks
- 2.2k
- Merge medio
- 1 d 18 h
- PR fusionados (30 d)
- 231
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de steipete/CodexBar
-
clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr impact:other issue-rating: 🦪 silver shellfish P2
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
steipete/CodexBar#5147 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr impact:other issue-rating: 🦪 silver shellfish P2
Dificultad 3/5 1-2 días Aptitud para principiantes 50/100
steipete/CodexBar#5144 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Claude CLI source drops "Current week (all models)" when /usage redraws over earlier screen contentAbiertoclawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Dificultad 4/5 3-5 días Aptitud para principiantes 30/100
steipete/CodexBar#5143 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
clawsweeper:needs-info clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr impact:ux-friction issue-rating: 🦐 gold shrimp P2
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
steipete/CodexBar#5132 · 5 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
issue-rating: 🌊 off-meta tidepool
Dificultad 1/5 Menos de una hora Aptitud para principiantes 1/100
steipete/CodexBar#5131 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
Todos los issues de steipete/CodexBar
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nwverse/persona#12800 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug documentation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
ajithrnayak/xpunge#7 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
DuarteSantos8/openGym#1469 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
Los mantenedores suelen responder en 1 día