Copy request-id and device-id to clipboard from error screenSupport needs these ids read out or pasted from the error screen; tapping
the support-info line now copies both and confirms with a toast. Also adds
a debug-only "Fejlskærm (debug)" entry under More so the error screen and
copy action can be exercised on a device or emulator without a real
backend failure.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Add device info screen and support-email device infoAdds an "Enhedsoplysninger" entry to the Support screen showing device
id/model/language and app/OS version, and prefills the "Kontakt
support" mailto with a greeting plus the same device info so users
don't have to copy it in manually.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Simplify pregnancy warning to a single nullable fieldThe backend only ever sends one warning today, and the domain model
should mirror that. Stacking multiple warnings is already handled
generically at the UI layer (OverviewScreen's alertBanners list), so
wrapping the domain field in a List added indirection with no benefit.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Show pregnancy warnings via stacked Figma AlertBoxReplace the hardcoded implausible-due-date banner with a generic,
stackable warning mechanism backed by the new backend `warning` field
on the pregnancy overview response, positioned per the Figma AlertBox
component above the tab bar.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
FGM-2896 send personal request parameters as POST form datadueDate, lastDayInLastMenstrualPeriod, birthDate, pregnancy week and the
article search term were sent as URL query parameters, which leaks personal
health data into access logs, proxies and telemetry breadcrumbs. Switch the
nine BFF endpoints that now offer POST variants (FGM-2895) to @FormUrlEncoded
POST with @Field parameters. Method signatures are unchanged, so no data
source, repository or...
Show request-id and device-id on the last two error states (FGM-2694)Two error states did not let the user read the request ids out to support.
The consent dialog rendered the error row, but accepted the consent and
dismissed itself in the same when branch, so the ids were only visible for a
frame. It now stays on the failure.
Article details rendered an empty state with a generic message and no ids at
all, because its failure state carried no throwable. Failu...
Nicolai Harbo
David Buhauer