Undefined array key in prepareUpdateData

TLDR:

1. I was also able to make these errors go away by clicking on "Check manually".
2. This might be a problem with how Drupal provides dev versions of modules via Composer

I just saw this when checking /admin/reports/translations. Six modules threw this warning. In four cases, we required a dev version in composer.json. In one case it was a module that had not been in the codebase for months. I don't know how to explain that.

For the four cases where we were pulling dev versions of modules, the .info.yml files did not have a project, for instance:

name: Admin Toolbar
description: Provides an improved drop-down menu interface to the site Toolbar.
package: Administration
type: module
configure: admin_toolbar.settings
core_version_requirement: ^9.2 || ^10
dependencies:
  - drupal:toolbar

In other cases, the project was added when pulling the module from Drupal, like so:

name: 'Block Class'
type: module
description: 'Allows assigning the classes to Blocks.'
package: User interface
configure: block_class.settings
core: 8.x
core_version_requirement: ^8 || ^9 || ^10
dependencies:
  - drupal:block

# Information added by Drupal.org packaging script on 2022-12-26
version: '2.0.11'
project: 'block_class'
datestamp: 1672065315

The last case was CTools, which was surprising. It looks like our composer.lock file still thought that CTools was required by Pathauto, even though that is no longer the case, and we did not have CTools enabled.

Please get this committed to core

It works and the error comes with every core update after fixing it

@RoloDMonkey i have install Drupal 11.x version on DDEV v1.22.6 and php 8.3.0 and reproduce the same criteria, but i didn't get this error on that version.

Solved the issue for my on core 10.2.5

Confirming that the patch in #7 worked to solve this issue for me.

Additionally, I believe both https://www.drupal.org/project/drupal/issues/3310058 → and https://www.drupal.org/project/drupal/issues/3422047 📌 Handle malformed module info in the translation status form Active are trying to solve the same issue seen here.

@Arun.k I believe this is an error that occurs during upgrades rather than on fresh installs.

When i open "Available translation updates" page i get this error.
Drupal 9.3.8

Just noticed this after upgrading to 9.4.10

It works and the error comes with every core update after fixing it

Solved the issue for my on core 10.2.5

In our case seems like the "locale.translation_status" has modules that were removed from the project but not from the key:

 
$status = \Drupal::keyValue('locale.translation_status')->getAll();
 
$module_handler = \Drupal::service('module_handler');
$module_handler->loadInclude('locale', 'inc', 'locale.compare');
$modules = \Drupal::service('extension.list.module')->getList();
$themes = \Drupal::service('extension.list.theme')->getList();
$project_list = array_merge($modules, $themes);
print_r(array_diff(array_keys($status), array_keys($project_list)));

Those modules were already removed from Drupal:

Array
(
    [0] => acquia_connector
    [1] => acquia_search
    [3] => addtoany
    [5] => advagg
    [9] => blazy
    [12] => colorbox
    [13] => colorbox_media_video
    [15] => config_filter
    [18] => config_update
    [19] => consumers
    [27] => email_registration
    [56] => jquery_ui_datepicker
    [58] => jsonapi_earlyrendering_workaround
    [59] => jsonapi_extras
    [64] => maillog
    [69] => memcache
    [74] => migrate_plus
    [107] => simple_oauth
    [115] => transliterate_filenames
)