0011965: Developer console: consecutive log lines overlap by up to 69%, so the request log is unreadable

ID	Project	Category	View Status	Date Submitted	Last Update
0011965	Taler	wallet (iOS App)	public	2026-11-08 17:11	2026-11-08 17:11

Reporter	bot-cg [agent]	Assigned To		Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator	CM_7
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	new	Resolution	open

Summary	0011965: Developer console: consecutive log lines overlap by up to 69%, so the request log is unreadable
Description	On the Developer screen's request log the lines are laid out closer together than they are tall, so each line overlaps its neighbours and the log cannot be read. Measured by UI automation on iPhone 17 (402x874 pt), iOS 27.2, GNU_Taler debug build, on a settled screen (the accessibility tree had stopped changing, so nothing was animating). Every `textView` in the log is 10.35 pt tall, and consecutive ones are placed 3.2 pt apart: y= 48.45 textView "request-start" y= 55.60 textView "8 Nov 2026 at 14:24" y= 58.80 textView "8 Nov 2026 at 14:24" y= 65.95 textView "- - -" y= 69.16 textView "- - -" y= 76.31 textView "request-start" y= 79.51 textView "request-finish-success" y= 86.66 textView "8 Nov 2026 at 14:24" The gaps alternate between about 7.15 pt and about 3.2 pt, and with a line height of 10.35 pt that gives overlaps of 31% and 69% of the smaller element in turn -- seven overlapping pairs on one screen. Severity is low and the audience is narrow: this screen is behind the developer-mode preference and no end user sees it. It is filed because it is a genuine layout defect that the harness reports on every campaign reaching that screen, and because an unreadable request log is precisely the thing a developer needs when diagnosing something else. Suggested place to look: whatever sets the row spacing or line limit for the log rows -- a fixed row height smaller than the text's own line height, or a negative spacing, would produce exactly this.
Steps To Reproduce	1. Install the GNU_Taler debug build on an iOS 27.2 simulator. 2. Settings -> More Settings -> enable Developer mode. 3. Settings -> Developer, and open the request log. 4. Perform any wallet action so several lines are logged. Observed: consecutive lines overlap; with more than a couple of entries the log is not readable. Expected: one line per row, no overlap.
Additional Information	Found by the fuzzing harness's layout analyzer, which reports two text elements whose frames intersect when neither contains the other and both are in the same branch of the accessibility tree (so a sheet drawn over a view is excluded). Campaign c2h-2c, episode c2h-2c-e00013, strategy `dark-debug-settings`.
Tags	No tags attached.

View Issue Details

Required notifications

Activities

Issue History