[kiril_bhd]

Here is my workaround which is ridiculous but it works.

private boolean firstChange = false;
item.addChangedHandler(new ChangedHandler() {

            @Override
            public void onChanged(ChangedEvent event) {
                // BUG: workaround
                if(!firstChange) {
                    firstChange = true;
                    item.setValue(2);
                    item.fireEvent(new ChangedEvent(item.getJsObj()));
                }
            }
        });

Best Regards

[Isomorphic]

As we already said: yes, we see this behavior, and it is the call to setAutoFetchData(true) that causes it - your quickest fix is to remove that call.

The underlying issue is queued to be looked into more deeply, behind issues from customers with support contracts.

When we've fixed the problem, we'll update here.

[kiril_bhd]

Thank you, Isomorphic.

[Isomorphic]

We've made a framework change to address this issue - you should see your sample working as you expect in builds dated July 7 and later.

[kiril_bhd]

Thank you, @Isomorphic.
It seems fixed in build July 7.