Repository navigation

fix(fcm): Preserve unmapped `TopicManagementResponse` error reasons - #1073

Merged

jonathanedey merged 5 commits into

firebase:masterfrom

JosRoseboom:issue-1072

Nov 19, 2025

Merged

fix(fcm): Preserve unmapped `TopicManagementResponse` error reasons#1073
jonathanedey merged 5 commits into
firebase:masterfrom
JosRoseboom:issue-1072

Commits on Feb 5, 2025
- RESOURCE_EXHAUSTED is a possible error code as well, given https://developers.google.com/instance-id/reference/server
  JosRoseboom
  committed
  e390198
- If the reason is not in the predefined ERROR_CODES it would be more helpful to use the reason String that came in as an parameter than UNKNOWN_ERROR. UNKNOWN_ERROR could be used for null or empty S…
  JosRoseboom
  committed
  814bc6d
Commits on Jun 3, 2025
- Merge branch 'master' into issue-1072
  JosRoseboom
  authored
  5c0b348
Commits on Nov 11, 2025
- Merge branch 'master' into issue-1072
  JosRoseboom
  authored
  eae314f
Commits on Nov 19, 2025
- For consistency with the current format of the error reasons, logic is added to map them from UPPER_SNAKE_CASE to lower-kebab-case. Entries from the ERROR_CODES that can be computed this way are re…
  JosRoseboom
  committed
  869b553