[Bug]: Dropping currency widget on to list widget causes app to crash

[ramsaptami]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Drag and drop a currency widget onto a list widget and observe the app crash and be unable to load the app if the widget is on the home page

Steps To Reproduce

Environment

Production

Version

Cloud

[somangshu]

@sbalaji1192 could you take a look at this?

[sbalaji1192]

Widgets with derived property/meta property won't work well inside the list widget, hence We are going to restrict those widgets from being added in the List widget canvas. List of widgets that are allowed -

"AUDIO_WIDGET",
"BUTTON_GROUP_WIDGET",
"BUTTON_WIDGET",
"CHART_WIDGET",
"CHECKBOX_WIDGET",
"CHECKBOX_GROUP_WIDGET",
"CIRCULAR_PROGRESS_WIDGET",
"DIVIDER_WIDGET",
"ICON_BUTTON_WIDGET",
"IFRAME_WIDGET",
"IMAGE_WIDGET",
"INPUT_WIDGET_V2",
"MAP_CHART_WIDGET",
"MAP_WIDGET",
"MENU_BUTTON_WIDGET",
"PROGRESSBAR_WIDGET",
"STATBOX_WIDGET",
"SWITCH_WIDGET",
"SWITCH_GROUP_WIDGET",
"TEXT_WIDGET",
"VIDEO_WIDGET",

[sbalaji1192]

RCA of the original issue: The currency widget and Phone input widget updates meta property(countryCode) when it gets mounted. List widget changes its children's id to list-widget-child-id-${itemIndex}-${widgetName}. when updating the meta property we're sending this id instead of the original Id and this id is supposed to be only used by the list widget, hence the platform is not recognizing this and we end up with an invalid canvas widget state, as a result, App crashes. The above solution to restrict widgets with meta property from being dropped inside the list widget should solve this issue.

[sbalaji1192]

fixed as part of #10928

[dilippitchika]

@sbalaji1192 reopening this issue, but with a lower priority. We can still drop blacklisted widgets by dragging them into the canvas first and then dropping them into the list

loom -

CC @somangshu

[sbalaji1192]

@dilippitchika I did discuss this with @riodeuno . There is an open story to address this issue - #10659 . Lets close this and track this over there

[dilippitchika]

Got it, could you please add a note/update the issue #10659, it's not very understandable for non-developers

[riodeuno]

@dilippitchika I have updated the task details in #10659 However, it is still quite technical in the description.