Promote: staging -> develop#697
Merged
Merged
Conversation
…rm (#696) ## Problem The **Wallet-Adresse** screen rendered the receive address in **lowercase** (`0x127d4a7e…ae8aa2`) in both the QR code and the address text. `SettingsWalletAddressPage` used `AppStore.primaryAddress`, which returns the lowercase `.hex` form. The canonical, verifiable representation of an Ethereum address is its **EIP-55 checksummed** form (mixed case). Showing lowercase is incorrect for a receive address users are meant to verify. ## Fix - In `settings_wallet_address_page.dart`, convert the address to its checksummed form via `EthereumAddress.fromHex(...).hexEip55` before passing it to the QR code and the displayed text. - **Scoped to this screen only** — `AppStore.primaryAddress` and all other consumers are untouched (per request: wallet-address screen fix only). ## Tests - Added a page test asserting the rendered `QRAddressWidget` receives the **checksummed** address in both its `subtitle` (text) and `uri` (QR), given a lowercase mock. - `flutter analyze` clean; page + QR-widget tests green. - Golden `settings_wallet_address_page_default` regenerated via `golden-regenerate.yaml` (address text now mixed-case). ## Test plan - [ ] Open Wallet-Adresse screen → address shown checksummed, QR encodes checksummed, copy copies checksummed. - [ ] Visual Regression green against the regenerated baseline. --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
… price chart (#695) ## Problem The public price view ("RealUnit Aktienkurs") shows an **empty chart** and `CHF --.--` whenever the RealUnit quote is temporarily unavailable. Confirmed against the live API: - `GET /v1/realunit/price` → `{"timestamp":"2026-06-04T22:28:16.539Z"}` — **no `chf`/`eur`**. - `GET /v1/realunit/price/history?timeFrame=ALL` → **1514 points, 1513 valid**, only the latest (2026-06-04) has no `chf`/`eur`. `DFXPriceService.getPriceChart` did `BigInt.from(entry['chf'] * 100)` for every entry, so the single null point threw (`null * 100`), the whole method threw, and `priceChart` stayed `[]` → the entire history (1513 valid points) was discarded and the chart rendered empty. `getPriceOfAsset` threw on the same null. This is the same defect class as the portfolio-chart fix in #694, but in the **price** code path (`dfx_price_service.dart`), which #694 does not touch. It is more visible because it affects the wallet-less public price view. ## Fix - `getPriceChart`: skip entries whose selected-currency price is `null` instead of throwing — the chart renders the full history minus the unpriced tail point. - `getPriceOfAsset`: return `BigInt.zero` when the price is missing, so the UI renders `--.--` instead of throwing. - `getChfToEurRate`: treat a missing `chf`/`eur` as `0` (already guards `chf > 0`). ## Tests - `getPriceChart` skips a trailing null point and keeps earlier valued points. - `getPriceOfAsset` returns zero on a missing price. - `getChfToEurRate` returns `0.0` on a missing price. - `flutter analyze` clean; price-service + price-chart-cubit suites green (22 tests). ## Test plan - [ ] Open the app with no wallet while the quote endpoint omits `chf`/`eur` → price chart renders full history, header `--.--`, no empty chart. - [ ] Normal case (all prices present) → unchanged. - [ ] Current price endpoint without `chf`/`eur` → header `--.--`, no crash. ## Related - Sibling fix for the portfolio chart: #694 (same null-handling defect, account endpoint).
#694) ## Problem When the REALU quote is temporarily unavailable, the dashboard showed a corrupt portfolio chart: the line crashed to **0** at the most recent point and the performance box reported **-921.27 CHF | -100.00%**, even though the header correctly rendered the total as `--.--`. Root cause: the API returns `valueChf` / `valueEur` as `null` for points it cannot price. `RealUnitAccountService.getPortfolioHistory` mapped that `null` to `0` (`value ?? 0`). The latest history point (balance still held, price `null`) was therefore plotted as a zero-value point, dragging the chart to the x-axis and making the `last - first` performance calc read `-100%`. ## Fix - Skip history points whose value is `null` in the selected currency instead of mapping them to `0`. The chart now ends at the last **known** value and the change is computed against it; the header keeps showing `--.--` (already handled). - A genuine `0.0` value (balance held but worth zero) is preserved and stays distinct from `null` (unknown). Single change at the API boundary — no chart/cubit/widget changes needed, since the false `0` originated in the service mapping. ## Tests - Rewrote the obsolete `treats a null value as 0` test → `skips a point whose value is null` (point is dropped). - Added `keeps a genuine 0.0 value (distinct from null)`. - Added `drops a trailing null point but keeps earlier valued points`. - `flutter analyze` clean; dashboard + dfx service suites green (516 tests). ## Test plan - [ ] Wallet with holdings while the quote endpoint returns `null` for the latest point → chart stays at last known value, header `--.--`, no `-100%`. - [ ] Normal case with all values present → unchanged. - [ ] Holding genuinely worth 0 → still renders 0, not dropped.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automatic Staging PR
This PR was automatically created after changes were pushed to staging.
Commits: 1 new commit(s)
Checklist