Can't add customizable options to product

[mikelevy300]

Preconditions

1. PHP 7.0.16
2. MySQL 5.7
3. Apache 2.4
4. Magento 2.1.9 (I was able to recreate this w/ both the sample data and the data from my store)

Steps to reproduce

1. Go into the admin panel and navigate to Stores->Attribute Set
2. Edit the default attribute set, add a new group named 'Options', add a few attributes to the new group, and save the group
3. Navigate toe Products->Catalog and choose any product with the default attribute set to edit
4. Expand the Customizable Options section and click the 'Add Option' button

Expected result

1. A new customizable option form should appear

Actual result

1. Nothing happens on the page
2. A 'Uncaught TypeError: Cannot read property 'apply' of undefined' error is thrown in the console

The full stack trace for the console error is:

Uncaught TypeError: Cannot read property 'apply' of undefined
at registry.js:54
at Registry._resolveRequest (registry.js:413)
at Registry._addRequest (registry.js:380)
at Registry.get (registry.js:224)
at async (registry.js:53)
at UiClass.applyAction (button.js:72)
at Array.forEach ()
at UiClass.action (button.js:50)
at HTMLButtonElement. (knockout.js:3863)
at HTMLButtonElement.dispatch (jquery.js:5226)

I traced it out and what is happening is there are two UIClass objects on the page with the same 'ns'=>'product_form' and 'index'=>'options' properties. This is occurring because the 'Options' attribute group we just created was given the attribute group code 'options' and that attribute group code appears to be the value that's used for the 'index' key in the resulting UIClass object. If we go back and delete the 'Options' group out of the attribute set, the button goes back to working like it should. I also tested out just renaming the group; however, it appears that the attribute group code is only set when the group is created. So changing the name later won't update the attribute group code.

[magento-engcom-team]

@mikelevy300, thank you for your report.
We've created internal ticket(s) MAGETWO-82893 to track progress on the issue.

[okorshenko]

The issue has been fixed and delivered to the 2.2-develop branch. Will be available with upcoming patch release

[magento-engcom-team]

Hi @mikelevy300. Thank you for your report.
The issue has been fixed in magento-engcom/magento2ce#1359 by @magento-engcom-team in 2.3-develop branch
Related commit(s):

• 1db3f8f
• 412d228
• 02620b0
• 57c5d8a
• 94a3f03
• 0d557dc
• 48baf59
• dc3bb78
• 0ab4533
• 00f64b0
• 440a1b5
• 4ed8f5b
• 656eeb5
• fd2f731
• 2c1a23f
• f7ff71a
• ac9bcfa
• 55debe0
• 3495086
• d678f15
• bf8ee30
• 335c91c
• c5a823f
• 696a5a5

The fix will be available with the upcoming 2.3.0 release.