entity_reference_autocomplete widget generates error when autocreating entities

The patch could not be applied. And if I manually apply changes from the patch in public function massageFormValues,
I get an error because

$entity = \Drupal::entityTypeManager()->getStorage($entity_type)->load($value['target_id']);

is null. So

$entity->getRevisionId()

doesn't work.

Also, if I inspect, the value of

$value['target_id']

it is the string 'previous revision' so it is not a paragraph id or something.

My entire $values array does not seem to have any usable information:
Array ( [0] => Array ( [target_id] => previous revision [_weight] => 0 [_original_delta] => 0 ) [1] => Array ( [target_id] => [_weight] => 1 [_original_delta] => 1 ) )

Applied patch #4 is the code from previous patch #2 for the function massageFormValues, but this one applies to latest dev version of entity_reference_revisions module, with an added

if (!is_null($entity))

check, because that was causing errors on my project. I would urge anyone to create a better patch and test this further as my patch is missing the newly added test from #2

Claude Code says:

Minor nits

- Extra blank line before the closing } (line between the } blocks) — cosmetic, not worth blocking over.
- The patch is from 2020 — given the age, it's worth verifying it still applies cleanly to 8.x-1.x. Looking at the current file, the code at lines 37–47 matches the patch's "before" context exactly, so it should apply.

Assessment: Good fix, recommend applying. It corrects a real logic-order bug and adds a proper null guard. Both changes are defensive and correct.

I'll make a MR!

@benstallings: Thanks for the MR, that *is* the reason this old issue is now merged, so I granted credits for that, but please do not post "Claude Code says" comments. If I'm interested in the output of an LLM, I can run it myself. See the new AGENTS.md in drupal core.