Function name must be a string

Problem/Motivation

We recently updated to the latest 7.89 Drupal Core update and have started seeing errors:

Uncaught exception 'Error' with message 'Function name must be a string' in drupal/sites/all/modules/contrib/geofield/geofield.module:294.

in geofield_field_presave called at /drupal/modules/field/field.attach.inc (209)
in _field_invoke called at /drupal/modules/field/field.attach.inc (914)
in field_attach_presave called at /drupal/sites/all/modules/contrib/entity/includes/entity.controller.inc (342)
in EntityAPIController::invoke called at /drupal/sites/all/modules/contrib/entity/includes/entity.controller.inc (450)
in EntityAPIController::save called at /drupal/sites/all/modules/contrib/field_collection/field_collection.entity.inc (479)
in FieldCollectionItemEntity::save called at /drupal/sites/all/modules/contrib/field_collection/field_collection.module (619)
in field_collection_field_update called at /drupal/modules/field/field.attach.inc (209)
in _field_invoke called at /drupal/modules/field/field.attach.inc (991)
in field_attach_update called at /drupal/modules/node/node.module (1178)
in node_save called at /drupal/sites/all/modules/contrib/i18n/i18n_node/i18n_node.module (489)
in i18n_node_form_submit called at /drupal/includes/form.inc (1531)
in form_execute_handlers called at /drupal/includes/form.inc (906)
in drupal_process_form called at /drupal/includes/form.inc (386)
in drupal_build_form called at /drupal/includes/form.inc (131)
in drupal_get_form called at /drupal/modules/node/node.pages.inc (14)
in node_page_edit called at /drupal/sites/all/modules/contrib/entity_translation/entity_translation.module (722)
in _entity_translation_callback called at /drupal/sites/all/modules/contrib/entity_translation/entity_translation.module (567)
in entity_translation_edit_page called at /drupal/includes/menu.inc (527)
in menu_execute_active_handler called at /drupal/index.php (21)

Occurs when we try to resave a field that has prepopulated data. If the field is brand new, the error does not appear.

We think its not related to the update or module itself. Just wondering if someone has been through this error before? We're finding it quite difficult to debug and find a fix for.