Stack Wallet

This commit fixes a UI timing bug in a cryptocurrency wallet's car-research payment flow. Previously, the app could mark the payment as 'complete' and try to open the order details before the backend ticket actually existed, which could briefly show the wrong screen or a fallback. Now it waits until the real ticket ID is available before marking the flow complete. There is no direct evidence this is a security vulnerability.

This commit fixes a UI state bug in the Stack Wallet app where leftover 'OP_RETURN' data (extra information sometimes attached to a cryptocurrency transaction) could stick around when a user changed the recipient address or scanned a new QR code. The leftover data could then incorrectly block or alter sending for coins that don't support it. The patch clears that stale state in more places and disables the preview-transaction button when OP_RETURN data is present for any coin other than Firo.

This commit fixes a UI/workflow bug in Stack Wallet's ShopInBit integration. When an order is fully covered by a voucher or store credit, the payment status becomes 'no_payment_required' and the invoice has no payment addresses. Previously the app treated this as a failed payment load and blocked the user; now it shows a 'fully covered' screen and lets the user continue. It is a functional bug fix rather than a security vulnerability.

This commit makes two small code cleanups in a car-research payment flow. One change removes a manual timer cancellation and relies on the caller to cancel it, which could in theory lead to a timer continuing to run briefly if the caller doesn't always do so. The other change replaces a safe integer parser (which throws a clear error on bad input) with a stricter parser that throws a less informative error. Neither change is obviously a security fix, and the commit message frames them as routine review follow-up rather than a security issue.

This commit changes how the Stack Wallet app parses data from its ShopInBit partner service. Previously, missing or malformed fields were silently replaced with empty strings, zero, or the current date/time. Now the app throws visible errors instead. That is generally a good defensive change, but it removes some safety comments and fallback behavior for unknown ticket states, and it makes parsing stricter. The patch is small and appears aimed at surfacing bugs rather than introducing a vulnerability, but it is only a partial hardening of the parsing layer.

This commit tightens how the Stack Wallet app reads data from its ShopInBit partner service. Previously, several fields were treated as optional and replaced with safe defaults (empty strings, false, current time) when missing. Now the code requires those fields to be present and correctly typed. This is a defensive correctness fix: it makes the app fail earlier and more visibly if the server sends unexpected or malformed data, rather than silently continuing with placeholder values. There is no direct evidence this fixes an active security vulnerability, but it reduces the risk of logic errors or misleading UI state caused by missing fields.

This commit fixes a bug in the Stack Wallet app's integration with ShopinBit's car-research service. Previously, if the invoice expiration date was missing or unreadable, the app would silently replace it with the current time, making a brand-new invoice look like it had already expired. Now the app keeps the expiration date as 'unknown' instead of guessing. This is a correctness and user-experience fix, not a remote code execution or theft vulnerability.

This commit fixes a bug in the Stack Wallet app's integration with ShopInBit. Previously, if the server returned a successful HTTP response with an empty body, the app would pretend it received valid data and create fake placeholder objects (for example, a support ticket with ID 0). Now the app correctly treats an empty successful response as an error instead. This is a defensive fix that prevents the app from acting on fabricated data, which could confuse users or lead to incorrect app behavior.

This commit fixes a business-logic bug in Stack Wallet's ShopinBit ticket screen. Previously, car-research invoices that had expired but were still within a 24-hour grace period were incorrectly treated as unpayable, so users could not resume or recover them. The change extends the payable check from the original expiration time to 24 hours after expiration, matching the documented spec. There is no direct security signal in the diff itself.

This commit fixes a bug in the Stack Wallet app's integration with ShopInBit. Previously, if the app's login token expired while making a request, the app would simply fail. Now, when it receives an HTTP 401 'unauthorized' error, it automatically refreshes the token once and retries the request. This is a routine reliability fix rather than a security vulnerability patch.

This commit fixes a small integration bug in the Stack Wallet app's ShopInBit payment feature. Previously, when a user tried to refresh an expired invoice, the app called the server without the required retry=true flag. The fix adds that flag so the server regenerates the invoice instead of returning an error. There is no direct evidence this is a security vulnerability; it appears to be a normal bug fix for a broken user flow.

This is a routine code cleanup commit. It removes one unused import and fixes a Dart lint warning by replacing an unnecessary null-assertion operator with a direct property access. There is no security-relevant change.

This commit fixes a race condition in the Stack Wallet app's ShopinBit feature. Previously, the app stored one shared 'customer key' on the API client object. When refreshing multiple tickets that belonged to different customer keys, one ticket's key could overwrite another's mid-refresh, causing requests to be sent with the wrong key. The fix passes the correct customer key alongside each individual request instead of relying on shared state. The commit message notes the fix may introduce other bugs elsewhere.

This commit removes a small performance optimization in the Stack Wallet app's ShopInBit service. Previously, if multiple parts of the app tried to fetch the same ticket list or car-research invoice list at the same time, they would share one network request. After this change, each call goes straight to the API independently. There is no security fix or vulnerability here—it's a straightforward code simplification that may slightly increase API traffic.

This commit removes a fallback mechanism in Stack Wallet's ShopInBit car-research payment flow. Previously, if the server didn't immediately provide the real customer-support ticket ID, the app would try to guess it by listing all tickets associated with the customer and picking the newest one that wasn't already known. That fallback is now deleted; the app simply waits for the server to supply the real ticket ID directly. The change is described as a functional fix, not a security fix, but removing a heuristic that touches other customer tickets reduces the risk of accidentally opening or acting on the wrong ticket.

This commit is a simple code cleanup: it moves the same retry-backoff calculation used by three different screens into one shared helper inside the ShopInBit client. There is no change in behavior, no bug fix, and no security improvement or regression.

This commit updates the Stack Wallet app's 'ShopinBit car research' feature to work with a newer version of the partner API (v1.0.6). It mainly changes how the app checks whether a customer has paid the car-research fee and how it finds the resulting support ticket. The old code relied on a separate 'log payment' API call that is being removed; the new code reads the payment/ticket status directly from a status endpoint. There is no obvious security bug being fixed, but the change removes a workaround where payment confirmation was partly driven by the client calling a logging endpoint.

This commit is a small UI cleanup in a cryptocurrency wallet app. It restores a 'building transaction' loading dialog on desktop, swaps one style of address picker dialog for another, and moves two hard-coded note strings into a shared constants file. There is no obvious security fix or vulnerability being introduced; it looks like ordinary bug-fix/refactoring work.

This commit changes the post-payment navigation in the ShopInBit feature of Stack Wallet. After a user pays, the app now tries to return them to the specific purchase request they came from, instead of always sending them to the general requests list. There is no security issue visible in this change.

This change is a performance fix, not a security fix. It prevents the wallet's ShopInBit ticket screen from making duplicate API calls when several refreshes happen at the same time. The code now shares one in-flight request among callers instead of firing multiple identical requests. There is no evidence in the commit of a vulnerability being patched.