Issues

We have noticed that the newest version of the Expanse theme, Expanse 6, includes significant changes to the HTML structure of pricing elements on the page. This leads to display glitches, as our app's code is not aware of this new structure. It's important to note that every Shopify theme is different, and every version of each theme can vary significantly. In Shopify, there isn't a unified way to update on-page prices, which means we have to develop dedicated integrations for every theme. When these themes release a new version with major structural changes, it can lead to issues like what you're experiencing. We will need to update our app to support Expanse 6, but we are currently managing multiple priorities and requests, so this will take some time. If you're encountering this issue, please upvote and comment on this thread.

We have received reports of incorrect discount percentage calculations when customers select certain currencies in our app. Specifically, the configured discount rule of 40% is accurate for the United Kingdom; however, when switching to other currencies like Australia and Canada, the displayed discounts are incorrect, showing 26% and 28%, respectively. We suspect that this issue may be related to currency conversions. Our app relies on the window.Shopify.currency.rate provided by Shopify to determine currency rates. It is possible that the rates being provided are either incorrect or inaccurate, causing the discount percentages to display incorrectly.

When editing texts in the Discount Title field of the Apply Discount modal, cursor makes random jumps to the end / middle of the text. How to reproduce: Type "Special Customer Discount" as the discount title in a apply discount modal. Move around the app's user interface. Return to the field, select and delete the word "customer" to replace with "Merchant". Observe the cursor jump to the end of the word "Discount". Here's a recording of the issue : https://www.loom.com/share/0bcd2f25a06e4cc5a8f6bcd85a3e84ac?sid=c26b3a46-0725-4f8a-bfad-b71aa8b402aa

Shipping discount fails to apply on subscription orders. The shipping discount applies just fine when the order is a one-time purchase. It however fails on subscription orders even when the order threshold is reached.

When using the "Select all" checkbox in the Discounts module, it appears to count the selected items correctly but does not visually check the boxes for the individual discounts. As a result, users can still check or uncheck discounts individually, even after using the "Select all" option. This behavior could lead to confusion and might cause unintended selections during bulk actions such as activating or deactivating discounts. Steps to reproduce: Navigate to the app home page. Click the "Select all" checkbox. Observe that although the system counts the discounts as selected, the checkboxes for individual discounts are not checked. Users can still manually select or deselect individual discounts. Expected behavior: The "Select all" checkbox should visually check all individual discount boxes and prevent further individual selection unless "Select all" is unchecked.

I tested the "zweiterplatz50" discount with "Only apply the discount once per order" checked and "Advanced options (Fixed amount discount)" set to 0 Expected Result: €60,98 -> € 10,98 -> 50€ off Test Result: €60,98 € -39,02 -> Success €100,00 off; 163.99% off Checkout Result: as expected When I set the quantity of "Advanced options (Fixed amount discount)" to 1 the test result is as expected but in the checkout the discount works only for the first item

When a product has multiple options (ex. Size AND Color), selecting a combination of those options results in the app not recognizing which variant is actively selected. The cause: our app was written under the assumption that each "variant selector" item on a page corresponded to a single variant. This is not always the cause. The possible fix: We've noticed that at least 1 affected theme has a "product form" on its product pages, with a hidden input that corresponds to the ID of the actively-selected variant. By detecting this element, and listening for changes to its value, we may be able to detect variant changes most reliably.

When the code for the shipping discount runs, it requests some data from Shopify. What's important here is that it requests: The list of "delivery groups." Each delivery group is a group of products that were in the cart, as well as a list of "delivery options." For example, one of the delivery groups in this case contained the "Cat's Menu" product, and 2 delivery options - "Ermäßigter Versand" and "Versand von Tiefkühlware" But for some reason that is currently unknown to me, this order actually contained 2 delivery groups The 2nd delivery group contained the "Cat's Menu" product, and just the "Ermäßigter Versand" delivery option. Since delivery options can often have the same name, Shopify gives each one a "handle" (it's like an ID) to distinguish from others. In this case, there were 2 total "Ermäßigter Versand" delivery options, each with a different handle. The way our app's shipping discounts work is that it goes through eevery delivery option within each delivery group, and figures out which discounts can be applied to that delivery option. Because both of the "Ermäßigter Versand" delivery options were eligible, and had different handles, our app calculated a discount for each "Ermäßigter Versand" delivery option. It's not clear why this leads to the discount applying twice, though, because the handles are unique, and only 1 delivery option can be chosen by the user at the time. This is something I'm probably going to try to reach out to Shopify support about, because it's not documented anywhere and I've never seen this before

The app is currently always displaying the discount title of the volume discount itself, ignoring the title the user has set on an individual quantity break

Completion status shows as 0 of 5 completed despite activating all five steps in the theme editor. Note: as long as all the app blocks are correctly placed in your theme, the functionality should still work as expected.