Stack Wallet

This commit is a routine user-interface cleanup. It replaces several copies of the same 'Are you sure you want to open this external link?' warning dialog with one shared version. The behavior shown to the user—asking permission before opening a web link in the device's browser—does not change. There is no indication this fixes a security bug.

This commit is a purely cosmetic UI cleanup for a ticket detail screen in the Stack Wallet app. It swaps some text widgets for selectable text, adjusts padding and borders, and replaces a custom container with a reusable rounded container. There is no security-relevant change.

This is a small UI bug fix in a Flutter settings screen. It moves an asynchronous key-loading call so it only happens while the screen widget is still active, preventing a harmless 'provider accessed after widget disposed' warning. There is no direct evidence this is a security vulnerability.

This commit is a user-interface cleanup for the CakePay gift-card flow on desktop. It replaces separate mobile/desktop navigation paths with a single nested navigator inside a dialog, swaps some loading indicators, and changes how order details receive their data (passing the whole order object instead of just an order ID). There is no clear security bug being fixed, and nothing in the diff suggests attackers could exploit it.

This commit is a purely cosmetic UI fix. It narrows three buttons on a desktop shopping page so they no longer overflow the window at the application's minimum width. There is no security relevance.

This commit changes a single screen in the Stack Wallet app so that timestamps are shown in the user's local time instead of UTC. It is a minor user-interface improvement with no security relevance.

This commit only changes the colors used for chat message bubbles in a customer-support ticket screen. It swaps hard-coded or theme-mismatched colors for theme-consistent primary/secondary button colors so the chat looks correct in light and dark modes. There is no security relevance.

This commit is a user-interface cleanup for the ShopInBit ticket and request screens. It swaps some dialog and container widgets, extracts repeated list-row code into helper widgets, and changes how a loading spinner is shown during ticket sync. There is no indication of a security fix or vulnerability being addressed.

This commit is a routine internal refactor that moves the app's shared database code from one location to another and switches some ShopInBit ticket data from the Isar database to a Drift/SQLite database. It is not described as a security fix, and the visible changes do not introduce obvious ways for an attacker to steal funds or data. The main risk is that any database migration could accidentally lose or corrupt user data, but nothing in the supplied diff proves that happened.

A one-line UI fix changes a safety check from 'if the widget is still in the tree' to 'if the Flutter BuildContext is still valid' before showing a temporary info banner. This is a routine Flutter correctness fix that prevents a possible crash when a screen is closed while the banner is being prepared. There is no direct evidence in the commit that this is a security issue.

This commit only adjusts the spacing between buttons on a settings screen, making gaps slightly wider on desktop and in a couple of places on mobile. It is a visual user-interface tweak with no security relevance.

This commit is a routine UI cleanup in the Stack Wallet app's ShopInBit settings screen. It removes an extra 'verify your key' dialog that was managed inside the same screen and turns it into a separate, self-contained dialog widget. The visible behavior—asking the user to re-enter their saved customer key before continuing—appears unchanged. There is no clear security fix or vulnerability here; it looks like a code-quality refactor.

This commit adds human-readable toString() methods and helper toMap() methods to three data classes that describe shopping tickets. It only changes how objects look when printed or logged; it does not alter how data is stored, transmitted, validated, or protected. There is no security issue visible in the change.

This commit is a routine refactor of the ShopinBit feature in Stack Wallet. It moves settings like whether the user accepted guidelines, completed setup, and their display name from the previous storage mechanism into a Drift/SQLite database, and switches UI code to use Riverpod providers for that database and the ShopInBit service. The diff shows no obvious malicious intent, no new network calls, no weakening of encryption, and no exposed secrets. It is primarily a code-quality and architecture change.

This commit fixes a small but real bug in the automated build pipeline for Android. Previously, the build script used `echo` to write the signing keystore from a base64-encoded secret. If the secret was empty or missing, `echo` would still create an empty file and the build would continue, potentially producing an unsigned or broken APK. The fix uses `printf '%s'` to avoid adding a trailing newline, and adds a check that aborts the build if the keystore secret is empty. This is a reliability and correctness improvement rather than a direct security vulnerability in the app itself.

This commit changes the GitHub Actions build workflow for the Stack Wallet Android app. It adds a step that converts the uploaded Android signing keystore from its original format into the PKCS12 format before building the APK. This is a CI/build pipeline fix and does not, on its own, introduce a vulnerability. It does mean the CI job now handles the app's private signing keystore and its password, so the security of the build pipeline remains important.

This commit removes a special workaround that previously skipped status and message updates for car-research tickets in a shopping feature. Now those tickets will call the same backend endpoints as other tickets. The change appears to be a functional bug fix rather than a security fix, but it slightly increases the amount of data exchanged with the backend for car-research tickets.

This commit changes how the Stack Wallet app handles unexpected status values from its ShopInBit partner service. Previously, if the server sent an unknown status string, the app silently replaced it with a default value (e.g., treating an unknown ticket state as a brand-new ticket). Now the app throws an exception instead. The commit also moves some UI label/color code into the enum definitions and removes duplicate code. The change is a defensive fix that prevents the app from misrepresenting order or webhook states, but it could also cause crashes if the server ever introduces new status values that older app versions don't recognize.

A developer commented out a special-case skip that prevented 'car research' support tickets from having their status checked. The change makes the app try to fetch status for those tickets too, fixing a UI hang where the request appeared to stay pending forever. There is no clear security problem in the diff itself; it is a functional bug fix.

This commit is a large code cleanup that splits one big ShopinBit order form file into smaller, easier-to-maintain pieces. It does not appear to change what the app does or how user data is handled; it mostly moves existing UI code around. There is no clear security problem visible in the diff, but because the change is so large and was labeled as 'testing AI refactoring,' it could accidentally introduce subtle bugs that would need normal testing to catch.

This commit fixes a typo in the build instructions: it removes an unnecessary backslash before the PowerShell script name so the command works correctly. There is no security issue here.

This commit swaps out an older, simpler method for choosing which coins to spend in Bitcoin-like wallets for a newer algorithm provided by an external library called coinlib. It also changes which fork of coinlib the app uses, from one maintained by a Stack Wallet contributor to one maintained by a community contributor. The change is described as a feature, not a security fix, and there is no disclosed vulnerability or incident tied to it. The main things to watch are whether the new coin-selection logic handles unusual transaction types correctly and whether the new coinlib fork is trustworthy and maintained.

This commit is a user-interface refactor for the desktop ShopinBit (crypto concierge shopping) flow. It replaces a brittle pattern of opening and closing separate dialogs for each step with a single dialog that contains its own nested navigator. There is no clear security bug being fixed; the changes are about navigation consistency and code maintainability. The only security-relevant observation is that the new route generator validates that navigation arguments are the expected order model, which slightly hardens type handling, but this is a normal defensive coding practice rather than a fix for a known vulnerability.

This commit only updates the Windows build instructions in the project's documentation file (docs/building.md). It changes software version numbers, adds steps for installing tools like CMake, NuGet, and CppWinRT, and clarifies how to run build scripts. There is no change to application code, no bug fix, and no security-related content.

This commit is a routine GitHub Actions CI maintenance change. It adds the 'staging' branch to automated build triggers and fixes a Windows build problem where the CI runner could not create symbolic links (shortcuts) for app assets, so the workflow now copies those asset folders instead. There is no indication this affects user security or wallet safety.