| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012143 | Taler | wallet (iOS App) | public | 2026-11-15 16:00 | 2026-11-15 20:03 |
| Reporter | bot-cg [agent] | ||||
| Implementer | MarcS | ||||
| Priority | normal | Severity | minor | ||
| Status | implementing | ||||
| Target Version | 1.7 | ||||
| Summary | 0012143: Alias Registration says "valid for 0 days" right after registering an alias for a year: confirmButton sets a literal zero duration (patch attached) | ||||
| Description | Right after an alias has been registered for one year and confirmed with the code from the mail, the Alias Registration screen says "This alias, valid for 0 days, is already registered to the mailbox on this phone." (alias-valid-for-0-days.jpg). A user reads that as "it has already expired". Steps (iOS 27.2 simulator): Settings -> Taler Directory -> create a mailbox -> Alias Registration -> enter an e-mail alias -> Lookup Alias -> Register Alias -> type the code from the mail -> Confirm. The registration itself is fine; the app asked for a year: registerAlias{"alias":"talerfuzz+58266@...","duration":{"d_us":31536000000000}, ...} Cause (AliasView.swift, confirmButton): on success the state is set with a literal zero duration, and the text prints it: try await model.completeRegisterAlias(register) lookupState = targetUri.isEmpty ? .unregistered : .confirmed(targetUri, Duration.microseconds(0)) ... Text("This alias, valid for \(validFor.toDays()) days, is already registered ...") Leaving the screen and looking the alias up again shows the real value, because LookupButton takes validFor from the lookupAlias response. Patch attached (alias-valid-for-0-days.diff, not build-verified): pass the validity the view already stores from the registerAlias response (`validFor`) instead of zero. Two things the patch does not cover and which may be worth a look while there: - registerButton sets `.registered(targetUri, Duration.microseconds(0))` in the same way, and AddContactView does it in two places; - when no validity is known at all, the sentence should not print a number of days rather than print 0. Found by the UI fuzz harness, scenario p2p-send-via-mailbox, 2026-11-15. | ||||
| Tags | No tags attached. | ||||
| Correction: the patch first attached (12143-alias-valid-for-0-days.diff) does NOT fix this. I built it and ran the flow: the screen still said "valid for 0 days". It reused the view's `validFor`, which is set from the registerAlias response -- and that response carries no validity here (the directory answers 202 Accepted), so the value is nil. Please ignore that file; I cannot delete it. 12143-alias-valid-for-0-days-v2.diff is the one to look at. It remembers the duration the app itself asked for in registerAlias and uses it when the response has none. Built (BUILD SUCCEEDED, Debug, iOS simulator) and run through the same flow on 2026-11-15: the screen now reads "This alias, valid for 365 days, is already registered to the mailbox on this phone." (alias-valid-365-days-patched.jpg). 12143-alias-valid-for-0-days-v2.diff (1,677 bytes) alias-valid-365-days-patched.jpg (37,548 bytes) | |