View Issue Details

IDProjectCategoryView StatusLast Update
0008740Talerwallet-corepublic2026-09-19 14:45
Reportersebasjm Assigned ToFlorian Dold Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionwon't fix 
Product Versiongit (master) 
Target Version1.6Fixed in Version1.6 
Summary0008740: wallet core should return more specific error codes for failed HTTP requests [scope-unclear]
Descriptioninstead of returning [1] WALLET_UNEXPECTED_REQUEST_ERROR with an errorResponse from MERCHANT error codes, wallet-core should return a specific error.

In this example [1] the error was produce calling `WalletApiOperation.PreparePayForTemplate`
In this case we need a new TalerErrorCode WALLET_TEMPLATE_NOT_FOUND and it should be returned for example when the http request returns 404 or 502.

But this may be the case of many wallet operations and we should also document the list of error codes (by operation) so the UI can handle them without a generic handler.

With this, UI can create custom and internationalized UI on error.

[1] {
  "code": 7005,
  "when": {
    "t_ms": 1713179479173
  },
  "hint": "Unexpected HTTP status 404 in response",
  "requestUrl": "https://backend.e.netzbon-basel.ch/instances/test/templates/default",
  "requestMethod": "POST",
  "httpStatusCode": 404,
  "errorResponse": {
    "code": 2000,
    "hint": "The backend could not find the merchant instance specified in the request.",
    "detail": "default"
  }
}
Tagsux

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

related to 0008544 closedavalos better error handling for iOS wallet 

Activities

Florian Dold

2024-07-31 23:22

manager   ~0022895

Not really clear where this is applicable.

If would of course be nice to have more accurate error codes for some situations, but we can't have one wallet-core EC for every server-side EC.

Florian Dold

2026-07-28 18:03

manager   ~0029272

Closing this as unactionable. For many requests, wallet-core does return more specific errors. If there are any that don't return a specific error that needs to be handle by the UI, we should open a separate issue.

Issue History

Date ModifiedUsernameFieldChange
2024-04-15 17:46sebasjmNew Issue
2024-04-15 17:46sebasjmStatusnew => assigned
2024-04-15 17:46sebasjmAssigned To => Florian Dold
2024-04-15 17:55sebasjmSummarywallet core should return more meaningful error codes => wallet core should return more meaningful error codes for every operation
2024-04-15 17:55sebasjmDescription Updated
2024-04-15 19:53MarcSRelationship addedrelated to 0008544
2024-07-31 23:22Florian DoldSummarywallet core should return more meaningful error codes for every operation => wallet core should return more meaningful error codes for every operation [scope-unclear]
2024-07-31 23:22Florian DoldNote Added: 0022895
2024-07-31 23:23Florian DoldSummarywallet core should return more meaningful error codes for every operation [scope-unclear] => wallet core should return more specific error codes for failed HTTP requests [scope-unclear]
2024-07-31 23:23Florian DoldTarget Version0.14 => 1.0 stretch goals
2024-09-16 22:07Christian GrothoffTarget Version1.0 stretch goals => 1.6
2025-04-17 20:43Christian GrothoffTag Attached: ux
2025-04-17 20:43Christian GrothoffTarget Version1.6 => post-1.0
2025-04-17 22:15Christian GrothoffAssigned ToFlorian Dold =>
2025-04-17 22:15Christian GrothoffStatusassigned => acknowledged
2026-07-28 18:03Florian DoldAssigned To => Florian Dold
2026-07-28 18:03Florian DoldStatusacknowledged => closed
2026-07-28 18:03Florian DoldResolutionopen => won't fix
2026-07-28 18:03Florian DoldNote Added: 0029272
2026-09-19 14:45Christian GrothoffFixed in Version => 1.6
2026-09-19 14:45Christian GrothoffTarget Versionpost-1.0 => 1.6