Self-updating mods prevent game from launching

[ThatExplo]

Please confirm the following.

• I checked the existing issues for duplicate problems
• I have tried resolving the issue using the support portal
• I have ensured my Modrinth App installation is up to date

What version of the Modrinth App are you using?

0.21.2

What operating systems are you seeing the problem on?

Linux

Describe the bug

Auto-updating mods break Modrinth's instance manifest and cause a soft-lock in the launcher itself.

For example, if you let Distant Horizons auto update;
v
it will cause this error
Invalid input: mods/DistantHorizons-3.2.0-b-1.21.1-fabric-neoforge.jar needs repair or re-import before launching this instance
which cannot be resolved by simply re-downgrading the mod because that gets blocked on account of that mod "already being installed" as far as Modrinth is concerned.
(Repairing the instance also doesn't fix it.)

The only way to un-break this as a user is by uninstalling DistantHorizons entirely and then reinstalling the initial version manually.

Steps to reproduce

1. Download Distant Horizons 3.2.0-b
2. Launch minecraft, and let Distant Horizons auto-update
3. close minecraft by alt+f4ing
4. the instance will now refuse to launch until you manually uninstall the new version AND reinstall the missing version

Expected behavior

The mod should simply be ignored, or the user should be offered to remove it from the manifest without changing the actually installed mods.

Additional context

No response

[penguinencounter]

try updating Modrinth App to 0.21.4, a bunch of the content store stuff was removed / relaxed

[SalmonSnaked]

0.21.4 will let you launch the instance even when the database has marked the file "missing" because you didn't use the native UI but removed it externally. Just bear in mind that if you execute Verify and Repair, that old version will reappear in your instance.
I think they should only manage modpack-managed files and leave local mods alone.

Your issue is actually a duplicate