UI-Select not updating currently selected entry when list changes

[hubnerd]

Bug description:

When refreshing the choice list, to a new list with new entries. UI-Select does update the list with the new entries but changing to the current selected entry using ngModel does not select the entry therefore it does not update what is currently selected.

Link to minimally-working plunker that reproduces the issue:

https://embed.plnkr.co/Xa40ujT5qnl8JVz44ch1/

Select Adam from the list and then click the button. Clicking on the list will show the new entries but the current selected entry is old and stale.

Version of Angular, UI-Select

Angular: 1.6.3

UI-Select: Latest from Mar 20, 2017 and 0.9.5

[Jefiozie]

Had a look at your example and cannot yet point where the problem is.
When I removed item.idfrom the repeat and just useitemand select the first item in the array with$scope.people[0]` it is refreshing the model.

Maybe this will be a workaround for now? Still i believe this needs some extra investigation.

[hubnerd]

I found away around the issue. I believe it is because I am changing the ref of the contents on the list. I am guessing there is some $watch'ing involved and once these refs are replaced with different ref's it cannot longer be watched for changes.

If I use object.assign to merge the lists together so I don't change the references of the contents it works fine. I don't know if there is a way around this on your end. Maybe watching the list itself and try to map the contents again?

Technically I would not also call this a bug but maybe a possible improvement. I shall leave it open for the team to close depending how they feel.

[Klinton90]

Hi guys, I'm facing almost same issue. In my case ngModel is set before options are retrieved from backend. After some investigation, it seems like this piece of code uiSelectSingle.L40 breaks proper option rendering. Just removing

if ($select.selected && checkFnSingle($select.selected)) {
    return $select.selected;
}

shouldn't break things too much, but code may run a bit slowly. Considering, that list of options, usually doesn't update too often, what do you think about that fix?

It has been added in this commit: 785c6a4 which is also a workaround for another/?similar? problem...