FieldException: Attempt to create a field without a field_name

I had this problem after upgrading from v2 to v3, but not when installing v2 fresh.
This and another problem with views, made me realise that quite a bit of upgrade code is needed to compensate for the change of entity name from group_content to group_relationship.

I've also ran into this issue when trying to upgrade from v2.3 to v3.3. I can also confirm that upgrading from v2.2.2 to v3.3 does not run into this error.

I've also ran into this issue when trying to upgrade from v2.3 to v3.3.

I have just run into this issue when trying to upgrade my site from Group 2 to Group. I have group 2.3.0 going to group 3.3.0 (along with subgroup from 2.0.2 to 3.0.2 and ginvite from 3.0.0-rc3 to 4.0.0-rc3).

We are running into the same problem with upgrading from 2.2.2 to 3.3.2.

The website encountered an unexpected error. Try again later.
Symfony\Component\DependencyInjection\Exception\ServiceCircularReferenceException: Circular reference detected for service "router.route_provider", path: "options_request_listener -> router.route_provider -> cache_tags.invalidator -> cache.flexible_permissions_memory -> cache.backend.corefix_memory_no_serialize -> maintenance_mode_subscriber -> url_generator". in Drupal\Component\DependencyInjection\Container->get() (line 149 of core/lib/Drupal/Component/DependencyInjection/Container.php).

There was an issue with group content types that had long names. Have you tried the latest release? 3.3.3

Also #7 seems completely unrelated to this issue.

We ran into this issue when upgrading from 2.2.2 to 3.3.3. We realized that we had a drush cr before our drush updatedb.

Following the correct drush deploy sequence fixed our issue.

drush updatedb --no-cache-clear
drush cache:rebuild
drush config:import
drush cache:rebuild
drush deploy:hook

Just ran into it on 3.3.3 with grequest module.
For me it happened when I had some field storage config that is normally installed by a relationship plugin already installed, reinstalling the plugin caused this error.
Probably some existing config check missing, deleting that storage config resolved the issue.

I've encountered this issue, as I liked to install a groups config via recipe, before the group module was installed. Installing the group module upfront helped.

Encountered the same as #9 - error shows up when rebuilding the cache after updating from v2 (I have verified that the deployment identifier changed) but does not show up if updatedb is run before clearing the cache.

The first time the cache is rebuilt I saw an error:

$ drush cr

In EntityTypeManager.php line 142:
                                                             
  The "group_relationship_type" entity type does not exist. 

The second time I see this error:

$ drush cr

In FieldConfig.php line 124:
                                                   
  Attempt to create a field without a field_name.  

As #9 mentions - it looks like drush deploy does not clear the cache before running update db. Our deployment steps do - which can be changed, but curious if this could be hiding an issue. Looking at the issue for the deploy command it looks like it was removed as it wasn't necessary as updatedb runs with a null back backend, and there is no instruction to do it in the drupal update docs → either - but from a quick google I can see we probably aren't the only ones doing it - e.g Lullabot.

So perhaps my issue is a deployment order issue given the steps to reproduce are completely different to the issue and other's comments such as #10 - but it might also be highlighting something wrong here.