[Bug]: After upgrade, App token login name does not match

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

After upgrading to the latest AIO, we get a "App token login name does not match" error. We also disabled talk while doing the upgrade, which had been previously enabled.

Steps to reproduce

1.Upgrade to latest AIO
2.
3.

Expected behavior

Previous app passwords would work

Installation method

Official All-in-One appliance

Nextcloud Server version

27

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

The report concerns app-token authentication after an All-in-One upgrade, with Talk disabled; no source file or test is named. Start by reproducing the upgrade scenario described in the issue and tracing the app-token login error. Done means existing app passwords authenticate successfully afterward.