Core patch for views grouped filters results geolocation config error

After having some problems with grouped filters in views I applied a core patch to fix it. This patch is working fine in general but if I save a view, which contains a geolocation field filter, I get an error:

The configuration property display.default.display_options.filters.field_geo_location_proximity.value.min doesn't exist.

This error also occurs on configuration import of the view. This is the filter part:

      field_geo_location_proximity:
          id: field_geo_location_proximity
          table: node__field_geo_location_proximity
          field: field_geo_location_proximity
          relationship: none
          group_type: group
          admin_label: ''
          operator: '<='
          value:
            min: ''
            max: ''
            value: '35'
            lat: '52.520015'
            lng: '13.404954'
            units: km
          group: 1
          exposed: true
          expose:
            operator_id: ''
            label: 'Distance (in kilometers)'
            description: 'Lat:52.5234146 Long:13.3702304 '
            use_operator: false
            operator: ''
            identifier: POI
            required: false
            remember: false
            multiple: false
            remember_roles:
              anonymous: anonymous
              authenticated: authenticated
              admin: '0'
          is_grouped: false
          group_info:
            label: ''
            description: ''
            identifier: ''
            optional: true
            widget: select
            multiple: false
            remember: false
            default_group: All
            default_group_multiple: {  }
            group_items: {  }
          expose_units: 0
          plugin_id: geolocation_filter_proximity

I'm only able to import the view configuration successfully, if I remove display.default.display_options.filters.field_geo_location_proximity.value from the configuration file.

If I only set display.default.display_options.filters.field_geo_location_proximity.value.max or some different value property I also get the appropriate error:

The configuration property display.default.display_options.filters.field_geo_location_proximity.value.max doesn't exist.

Experts said that this is a geolocation issue and gave some tipps to solve it.

Steps to reproduce:

1. Install current version of geolocation (dev or latest stable)
2. Apply patch grouped_filters-2369119-73.patch
3. Add proximity filter with default values to an existing view and try to save it

The related grouped filter patch will be included in upcoming releases for 8.1 and 8.2, so it will become an major issue sooner or later.