HxListLayout - When a chip is removed, chip generated by descendant of HxAutosuggest is also removed

[StanleyCZ]

On the page where I use HxListLayout, I use the LoginAccountPicker component (a descendant of HxAutosuggest) in the FilterTemplate.

The purpose of LoginAccountPicker is to call the api for prompting users as shown bellow:

After applying the filter, a list of Chips is generated. However, as soon as I remove any chip other than the one generated from the LoginAccountPicker from the list, this chip is also removed from the list, although the value in the filter still remains.

I tried modifying the ResolveAutosuggestItemFromValue function so that I didn't retrieve the data asynchronously and didn't use await (I just read it from the mocked list memory), but the result was the same.

While debugging this issue, I also discovered that the HxListLayout lifecycle is repeatedly creating new LoginAccountPicker components. Maybe this could be the problem?