URL alias (Translation is not supported)

I have this same problem in Drupal 10.1. Actually, my custom paths no not work, and I think it is a translation problem.

I had other problems that might be related, but I don't know where to go to look. When I looks at custom fields in entities, there were errors saying that they could not be translated because there was a language mismatch between the field and the underlying storage. Basically, when I started setting things up I had "la" as the language, but when I added some fields I was using the "en" interface, so the fields got "en", even though I had created them earlier "la" storage (I was reusing them in other content types).

The solution was to use drush to fix the field language:

drush cset field.field.node.dates.field_type langcode la

Is there a way to check for a language mismatch in the path settings and to fix it with drush?

This looks perhaps like a bug report. Can someone verify this on a "fresh" install of latest Drupal version?

@cilefen, just checked, and am seeing the same message as reported in IS.

I'm seeing this on D10.3.

I noticed that if I enable translation on URL aliases, they do work. I can create a French alias for an English URL, for example.

So it seems maybe the only issue (at least in my case) is that /admin/config/regional/content-language incorrectly shows "URL alias (Translation is not supported)." ... when it apparently *is* supported.