0010404: make easier to report error to service provider - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0010404	Taler	specification	public	2025-09-15 15:37	2025-09-15 15:37

Reporter	sebasjm	Assigned To
Priority	normal	Severity	minor	Reproducibility	sometimes
Status	new	Resolution	open
Target Version	post-2.0

Summary	0010404: make easier to report error to service provider
Description	now when wallet or spa have an error it should the information to the user and user need to manually interpret, copy and send the info. this is not for every user, slow and maybe information is lost. in the industry you have tools like sentry that let's you automatically send all the stack anytime a user has an error, making it easier to know how many errors the user are getting (on the client side) but this is too intrusive on the user privacy nevertheless, an easier way to report bugs will improve greatly the UX I suggest that: a) for wallets: 1) they should discriminate between own error (http 400, or bugs in own code) and service provider errors (in principle, only http 500) 2) a button to report own errors to the developer contact based on the platform distribution (google, apple, firefox, chrome, fdroid) 3) a button to report SP errors directly to the SP (we should expose an contact email in the SP /config) b) for spa: basically the same, but all errors should be reported to the same contact email in /config since the SPA is distributed with the backend. upon error, the user should see a description with a "report this problem" button. Before sending the user should have a way to check what information is being sent. Regarding information being gathered: * in case of own errors, stacktrace should be enough. * in case of SP errors, the details of the http request may have private information but it is information that was already being sent to the SP
Tags	No tags attached.

Date Modified	Username	Field	Change
2025-09-15 15:37	sebasjm	New Issue