Configurable product price is not changed when option is selected

[github-jira-sync-bot]

Steps to reproduce:

1. Create dropdown type product attribute:

• Default Label: my size
• Catalog Input Type for Store Owner: Dropdown
• Values Required: No
• 3 options: my small, my medium, my large
• Scope: Global
• Unique Value: No
• Input Validation for Store Owner: None
• Add to Column Options: No
• Use in Filter Options: No
• Use in Search: Yes
• Search Weight: 1
• Visible in Advanced Search: Yes
• Comparable on Storefront: No
• Use in Layered Navigation: Filterable (with results)
• Use in Search Results Layered Navigation: Yes
• Position: 0
• Use for Promo Rule Conditions: No
• Allow HTML Tags on Storefront: No
• Visible on Catalog Pages on Storefront: Yes
• Used in Product Listing: No
• Used for Sorting in Product Listing: No

2. Create text swatch type product attribute:

• Default Label: color text swatch
• Catalog Input Type for Store Owner: Text Swatch
• Values Required: No
• Update Product Preview Image: No
• 3 options: black, white
• Scope: Global
• Unique Value: No
• Input Validation for Store Owner: None
• Add to Column Options: No
• Use in Filter Options: No
• Use in Search: Yes
• Search Weight: 1
• Visible in Advanced Search: Yes
• Comparable on Storefront: No
• Use in Layered Navigation: Filterable (with results)
• Use in Search Results Layered Navigation: Yes
• Position: 0
• Use for Promo Rule Conditions: No
• Visible on Catalog Pages on Storefront: Yes
• Used in Product Listing: Yes
• Used for Sorting in Product Listing: No

3. Create configurable product with 1 attribute:

• Attribute Set: Default & My Size
• Name: Conf 1
• Category: Bug
• Product configuration:
  -- attribute: my size
  -- attribute values of my size: my small, my large
• As a result this product has 2 variations: Conf 1-my small & Conf 1-my large
  -  Set custom different prices for product variants & and set quantity for that variations

4. Create configurable product with 2 attributes:

• Attribute Set: Default & My Size + Color Text Swatch
• Name: Conf 2
• Category: Bug
• Product configuration:
  -- attributes: color text swatch & my size
  -- attribute values of color text swatch: black, white
  -- attribute values of my size: my small, my large
• As a result this product has 4 variations: Conf 2-black-my small, Conf 2-black-my large, Conf 2-white-my small, Conf 2-white-my large
• Set custom prices & quantity for that variations

5. Create Catalog Products List widget:

• Type: Catalog Products List
• Widget Title: Catalog Products List
• Assign to Store Views: All Store Views
• Display On: Configurable Product
• Products: Specific Products: Select product Conf 1 from the list
• Container: Main Content Area
• Title: Catalog Products List
• Display Page Control: Yes
• Number of Products per Page: 1
• Number of Products to Display: 1

6. Open Conf 1 product page

Expected behavior:

1. There are not console errors
2. When user selects other product option, final product price is changed and there is not console error

Actual behavior:

1. There is configurable.js console error when Conf 1 product page is loaded:

Uncaught TypeError: Cannot read properties of undefined (reading '0') {code}
2. When user selects other product option, final product price is NOT changed and there is configurable.js console error:
{code:java}
Uncaught TypeError: Cannot read properties of undefined (reading 'length')```

[github-jira-sync-bot]

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-1764

[m2-assistant]

Hi @github-jira-sync-bot. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[chittima]

Internal team is working on this issue

[njecom]

Hi,
how can I take part in solving issues?
I want to become community member

Thank you
Nishant Kumar

[njecom]

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-1764

can I take part in solving issues?

[o-iegorov]

@njecom the ticket in active development phase by internal team, probaly will be resolved soon so no sense to work on it, but if you have some suggestions you're always welcome to share them

[m2-assistant]

Hi @o-iegorov. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 2. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[o-iegorov]

INternal team works on this issue

[hostep]

Seems like it got fixed by 3545221