Call to a member function getFieldStorageDefinition() on null

@logicbus I encountered the exact same problem you are describing. Except that I don't know if the site used to have Workbench Moderation, but it's possible.

I deleted the moderation_state field using:
drush config-delete "core.base_field_override.block_content.custom_block.moderation_state"

That solved the problem for me.

Note that your block type might be called something else. You can see all the config names in the "config" database table.

I'm having a similar issue importing the config to the database after upgrading to Drupal 10.2. The command $ drush cimterminates with the following error message when it reaches any config related to moderation.state.

Error: Call to a member function getSettings() on null in Drupal\Core\Field\FieldConfigBase->getSettings() (line 372 of /docroot/core/lib/Drupal/Core/Field/FieldConfigBase.php).

When deleting these config files, the import completes successfully.

System Info:

• Drupal 10.2.
• PHP 8.1 & MySQL 8
• Drush 12.4.3.0

I have the same problem and I delete all files related to the 'Moderation state' After I finish importing the config sync I back the files to the config and I run config import again it is working fine.

Same error here after updating from drupal 10.1.8 to 10.2.3 and making a drush si.
After deleting al configs related to moderation state, the error is gone.
We will try to provide more info.

This is an example of file that we removed:
config/default/core.base_field_override.node.article.moderation_state.yml

-uuid: 7eec08fd-0047-4a46-82c7-332e22dad1f6
-langcode: en
-status: true
-dependencies:
-  config:
-    - node.type.article
-id: node.article.moderation_state
-field_name: moderation_state
-entity_type: node
-bundle: article
-label: 'Moderation state'
-description: 'The moderation state of this piece of content.'
-required: false
-translatable: true
-default_value: {  }
-default_value_callback: ''
-settings: {  }
-field_type: string

Deleting the

core.base_field_override.*.*.moderation_state.yml

worked for me. They were created by saving the content translation form and just like in comment #12 they did not change anything from the defaults so there was no need for an override.

After exporting the config, trying to install the site from that config leads to the error from the IS.