Geocoder field can break creating of the content translation.

The issue is caused by 'data' value
Dumper returns value with 'data' property and it saves in the field.
But when we try to create a new translation and the address isn't changed, then 'data' property of the field value will be empty and EntityUntranslatableFieldsConstraintValidator determines this case as changing the field and returns an error.

We need to unset 'data' property to prevent such cases.

I tried to reproduce this issue / use case (with the Geofield instead of Geolocation) and was never able to do that.
I never intercepted the 'data' value,
I was correctly able to Translate the content (according to the described use case) and rather the added code always breaks the Geocoder workflow (and the application) because most of the times the unset is applied to a string (rather than an array), such the following:

$result = ["POINT(XX.XXX YY.YYYY)"]

I am closing this, as Cannot Reproduce.
Please reopen but ONLY providing a better use case description and much more solid and defensive code.

itamair → closed merge request !43