Magento 2.3.4 swatch-renderer.js assumes all attributes are swatches

[theloveofcode]

Preconditions (*)

1. Magento 2.3.4

Steps to reproduce (*)

1. Create a Configurable product with at least one swatch type attribute, and one non-swatch type attribute as the product's super attributes.
2. Go to the new Configurable product's page on the front-end.
3. Configure the product by clicking attribute options until you click on an option from a non-swatch attribute.
4. Note the JS error: "Uncaught TypeError: Cannot read property 'additional_data' of undefined"

Expected result (*)

1. No JS error is thrown when clicking on options for non-swatch attributes

Actual result (*)

1. A JS error is thrown.

This appears to have been caused by the new line 729 in Magento 2.3.4 It should not assume that all attributes it encounters are swatch-type attributes.

[m2-assistant]

Hi @theloveofcode. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@theloveofcode do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. 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!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hello @theloveofcode

Thank you for your report.

What is the non-swatch attrubute you are using?
Because we are rechecking with Dropdown, for example, and no JS error appears.

Can you please confirm that you are facing this issue on 2.4-develop?

Thank you

[engcom-Bravo]

@theloveofcode

We are closing this issue due to inactivity.
Please feel free to comment, reopen or create new ticket according to the Issue reporting guidelines

Thank you for your collaboration

[heavyrahul]

Any update on this Issue I am getting same issue

[engcom-Bravo]

Hello @heavyrahul

Thank you for your comment.

Which version of Magento are you facing the issue with? (2.2, 2.3...)

Thank you in advance

[heavyrahul]

I am Using 2.3.4 version when I select watch option in product detail page getting this error
TypeError: this.options.jsonSwatchConfig[attributeId] is undefined in magento 2.3.4