Available in the 2018 R2 SP release.

Available in the 2018 R2 SP release.

The expected behavior when updating the text on a button click, for example,  is to expand the editor.

Currently the editor is expanded when the user starts typing inside it.

 Nullable int property is validated against range when no data is input.

This prevents content below the control to be visible.

Available in the R2 2018 release.

Available in the R2 2018 release.

There is an empty group title view above the editors even if there are no groups.
The red area on the attached screenshot.

On UWP, the IntegerEditor has a default max value of 100. This is not present on other platforms.

Current Workaround

The workaround is to explicitly set the max value via a NumericalRangeValidator

E.G.

[NumericalRangeValidator(int.MinValue, int.MaxValue)]
public int PropertyName { get; set; }

Built the SDKBrowser project for iOS, using VS 2017 and latest stable Xamarin.Forms.
When editing a field, the OS keyboard appears and above it are "Prev" and "Next" buttons for moving between form fields.  Those buttons behave erratically.  Attached 2 images.

01: the 1st field is focused.
02: after pressing Next, the 3rd field is focused ("Age").

Pressing Next again does not change which field is focused, and Prev becomes active.  Pushing either Prev or Next does nothing at all.

Available in minor release 2018.1.202. It will also be available in the R1 2018 SP release.

When DisplayValueFormat is set to an Integer property, Zero value is not applied.

 When a field is of type Integer and is configured to use IntegerEditor, currently it is shown with a decimal point

The maximum value that the DecimalEditor can set seems to be 100. If the underlying property is more than 100 it automatically sets it and you cannot increase it through the UI.

If an editor does not have positive/negative feedback, an empty text view still appears after validation and shifts the editors.

Available in the 2017 R2 SP release.

Users cannot  input decimal separator both "." and "," in the decimal editor. 

Available in minor release 2017.2.0523. It will also be available in the R2 2017 SP release.