Multiple select dropdown not populating when options are resolved after model.

[jox]

This is the same issue as described in #133, except it's with multiple select dropdowns.

I've forked the plunker from #133 and changed it to a multiple select using ui-select 0.8.0.

It will wait 5 seconds before the choices are resolved. Clicking the "Change Model" button within this time will trigger the bug. What happens is, that the values are changed to 'null' after they are set in the model.

When "Change Model" is clicked after the 5 seconds, it works as expected.

[dimirc]

One way to avoid the errors will be define an empty array before the async load:

Currently is :

$scope.people = {};

Change to :

$scope.people = {devs: []};

Check updated plunker

[jox]

Thanks, this does indeed fix it in the isolated plunker example. In our more complex application it does not seem to help though. I'll try to set up another plunker to reproduce it.

[ivanblazevic]

@jox I had similar issue, when data is resolved all selected values becomes rewritten to null, this fix was working for me #349

[Noemi-]

＋1
I got the repeat data from server, and when I set the ng-model to an array which contains repeated properties. The dropdown won't updated, and it still contain the selected values

[wesleycho]

This needs an up to date Plunker based on the latest release.