"There are no content items matching" when trying to add a second value in a multivalued field

I think this happens since alpha2 at least.

Well, it as much simpler. The fields are in different order when loaded from AJAX.

So only thing needed is to add a #weight to have always the same order and avoid confusing the user, like my case.

Automatically closed - issue fixed for 2 weeks with no activity.