Stack Wallet

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 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 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 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.

This commit simply corrects an error message text. When a part of the app called ShopInBitService is used before being set up, the thrown error now tells the user to call ensureInitialized() instead of the outdated init(). There is no security change.

This commit is a routine user-interface refactor. It replaces a one-shot list of gift-card vendors with an 'infinite scroll' list that loads more cards as the user scrolls, and updates the backend client to return paginated results. There is no security-relevant change visible in the diff.