Stack Wallet

This commit is a UI/UX fix for the Stack Wallet app's ShopinBit integration. It makes sure the delivery country shown during shipping matches the country that was used to price the order. It does not appear to be a security fix and does not introduce obvious security risks.

This commit fixes a bug in Stack Wallet's ShopInBit payment screen. Previously, if the user tapped 'PAY NOW' before the payment address had loaded, the app would abruptly close the entire navigation stack (effectively kicking the user out of the checkout). Now it shows a warning message, attempts to recover the missing payment details from the server, and continues polling instead of popping screens.

This commit is a user-interface refactor for the ShopInBit checkout flow. It moves the loading of payment information earlier in the process so the payment screen appears already filled in, rather than showing a spinner after the page opens. There is no direct security fix here, but the change touches code that handles invoice creation, polling, and route arguments for a third-party payment integration.

This commit fixes a timing bug in the Stack Wallet app's ShopInBit payment flow. Previously, the code that launches the in-wallet send screen was called without waiting for it to finish, and the app could continue running logic on a screen that had already been closed. The change makes the navigation awaitable and adds a check to stop further work if the widget is no longer visible. This is a correctness and stability fix that could prevent UI glitches or inconsistent order state, but it is not a clear-cut security vulnerability.

This commit only swaps out some on-screen icons in the Stack Wallet app. It replaces standard Flutter icons with custom SVG-based icons in a few payment and order history screens. There is no security change here—just a visual consistency update.

This commit fixes a bug in Stack Wallet's ShopInBit payment feature. Previously, when a user chose to pay with USDT, the app assumed every USDT payment address was on the Ethereum network. If the merchant actually provided a Tron (TRC-20) USDT address, the app could still try to route the payment through an Ethereum wallet, which would send funds to the wrong kind of address and likely cause the user to lose money. The fix checks whether the payment URI is genuinely Ethereum-based before allowing an in-app Ethereum/USDT wallet payment; otherwise it forces the user to pay externally.

This commit simply swaps a generic copy icon for a custom project-specific copy icon widget in one screen of the Stack Wallet app. There is no visible security change.

This commit is a routine code cleanup: it moves duplicated payment-handling logic from two ShopInBit screens into a single shared helper file. There is no security-relevant change visible in the diff—no new permissions, no altered validation, no changed cryptography, and no new network behavior. The shipping screen also gets a small UI tweak to allow country selection only when the order did not already arrive with a country.

This commit is a build-script portability cleanup. It replaces macOS-specific and Linux-specific ways of running the `sed` text-editing tool with a single cross-platform approach that works on both systems. There is no security-relevant change here.

This commit is a build-script cleanup. It makes the pre-built crypto plugin download scripts aware of which app is being built (stack_wallet, stack_duo, or campfire) so that only the plugins needed for that app are downloaded. It also updates the frostdart plugin submodule to a newer version. There is no user-facing app change and no obvious security vulnerability introduced by the diff itself.

This commit is a purely cosmetic user-interface tweak. It changes how a 'Review offer' button and product text are arranged on the screen depending on whether the app is running on desktop or mobile. There is no security relevance.

This commit is a routine user-interface cleanup for a shopping feature inside the Stack Wallet app. It swaps some dialog widgets, adjusts button layouts, and makes desktop and mobile navigation behave the same way. There is no indication it fixes a security problem.

This commit fixes a minor user-interface bug in a mobile dialog. When a user opens a text field inside a dialog on a phone, the on-screen keyboard can slide up and cover the field. The change adds padding equal to the keyboard's height so the dialog shifts out of the way. There is no security relevance in the diff itself.

This commit adjusts the height of two buttons (Cancel and Confirm) in a settings dialog so that on mobile devices the buttons use a default height instead of a fixed large height. It is purely a user-interface layout fix with no security relevance.

This commit only adds error logging to a car-fee invoice creation screen. It does not change how user data is handled, how money moves, or how the app protects itself. It simply records more details when something goes wrong, so developers can diagnose issues later. There is no security problem here.

This commit updates the Stack Wallet app's integration with the ShopinBit service. It changes how a payment invoice is created: previously the app used a GET request (which could accidentally create invoices), and now it uses a PUT request after the user clicks 'PAY NOW'. This is a normal API migration to match a new ShopinBit specification version 1.0.4. There is no direct evidence in the commit of a security vulnerability being fixed or introduced.

This commit changes how Stack Wallet's ShopInBit payment screen fetches an invoice. Previously it always created or regenerated a payment invoice with a PUT request. Now it first checks with a GET request and only creates a new invoice if no live one exists. This is a defensive fix to avoid overwriting or regenerating an existing valid invoice, which could disrupt a payment in progress or cause funds to be sent to a stale address.

This commit fixes a bug in the Stack Wallet app's integration with ShopInBit, a third-party shopping service. When users sent text containing non-English characters (like ± or emoji), the app encoded them incorrectly before sending over the internet. This could corrupt order details, shipping names, or item descriptions, potentially causing orders to fail or be processed with wrong information. The fix forces all special characters to be sent as safe ASCII escape sequences.

This commit simply removes a GitHub Actions workflow job that automatically packaged and published release files when a new version tag was created. It is a routine revert of a previous merge-conflict resolution and does not change any wallet code, cryptography, or user-facing security behavior.

This commit undoes a recent feature that copied remote customer support tickets into the app's local database during refresh. The revert removes the backfill step, so tickets created on another device or the web dashboard will no longer automatically appear in the local database. The change is described as a routine revert, not a security fix, and no public references explain why it was reverted.

This is a small user-interface navigation fix. The developer removed an unused wrapper widget and now directly calls the close action when a desktop user clicks a button. There is no indication this change affects security, user data, or wallet funds.

This commit fixes a small data-recovery bug in Stack Wallet's integration with the ShopInBit shopping service. When a user restored their wallet or reopened an existing support ticket, the app had been storing an empty description and could not tell whether the ticket was for travel or the general concierge service. The patch recovers the original request text from the first message and uses a simple text pattern to detect travel bookings. There is no sign this exposes user funds, private keys, or allows remote attacks; it is a correctness improvement for how existing ticket data is displayed and categorized.

This commit adds a feature that downloads a user's complete order/ticket list from a remote service and saves any missing entries into the local database when the app refreshes. It is a routine data-synchronization improvement, not a security fix.

This commit finishes a previously stubbed-out feature that downloads a customer's support/order tickets from an external service (ShopinBit) and stores them locally in the wallet's database. It is a normal feature implementation. There is no direct evidence in the commit that it fixes a security vulnerability, but it touches sensitive data (customer key, ticket messages) and makes network calls, so a defensive review checks for obvious safety issues.

This commit adds a placeholder (stub) function for a future feature. It does not contain any working code, does not change how the app currently behaves, and introduces no security issue. The new function immediately throws an error if called, which is normal for unfinished development.