Modrinth won't work after updating

[BrunoGC13]

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?

I can't find the version because I can't open modrinth.

What operating systems are you seeing the problem on?

Windows

Describe the bug

I used modrinth normally until I closed it and reopened it, then it asked my with a UAC prompt to update, I hit yes and afetr launching the app it gives me the following error:

Error while applying migrations: migration 20240711194701 was previously applied but has been modified

Steps to reproduce

1. Update modrinth
2. Open modrinth and then tere should be the error

Expected behavior

Modrinth should normally start up and everything should work like always

Additional context

I got the same error yesterday and I had to completely delete die application data and add all my profiles without a .mrpack back in.

[MiguVT]

I can confirm this issue, I have my own fork and got the same error, for a temp-fix delete C:\Users\MiguVT\AppData\Roaming\ModRinth\app.db

[ThisIsIPat]

Same here

[brianorca]

I saw this error when upgrading from 9.x to 10.0, and I had to dump the app.db and start from scratch. Then I got the same error when upgrading from 10.0 to 10.1 just two days later.

[AlexTMjugador]

I can confirm this issue, I have my own fork and got the same error [...]

Forked or modified app versions may have been built with different database migration scripts, or different checksums for those scripts (see #3899). Therefore, database compatibility between official release builds and any other sort of build is not and can not be guaranteed in the general case. Users of non-official release builds should not expect such compatibility, neither report instances of incompatibility where a Modrinth App build of different provenance has been involved at any point, because they are not actionable. When dealing with different kinds of builds, it is the responsibility of the user to backup such database, consider it as potentially volatile when upgrading, or take any other action to prevent undesired data loss.

The cause of the migration error when upgrading from databases created by ≤0.9.x to 0.10.0 and by 0.10.0 to 0.10.1 has been identified, and a fix released. This issue should not happen when upgrading from official ≤0.9.x databases to ≥0.10.1.

[AlexTMjugador]

@BrunoGC13, have you tried downloading and installing the latest version from the website again? If you've only used official release builds and did not let version 0.10.1 initialize a new database file, that should fix your issue.

[MiguVT]

I can confirm this issue, I have my own fork and got the same error [...]

Forked or modified app versions may have been built with different database migration scripts, or different checksums for those scripts (see #3899). Therefore, database compatibility between official release builds and any other sort of build is not and can not be guaranteed in the general case. Users of non-official release builds should not expect such compatibility, neither report instances of incompatibility where a Modrinth App build of different provenance has been involved at any point, because they are not actionable. When dealing with different kinds of builds, it is the responsibility of the user to backup such database, consider it as potentially volatile when upgrading, or take any other action to prevent undesired data loss.

The cause of the migration error when upgrading from databases created by ≤0.9.x to 0.10.0 and by 0.10.0 to 0.10.1 has been identified, and a fix released. This issue should not happen when upgrading from official ≤0.9.x databases to ≥0.10.1.

Nope, i know what im doing and my fork use the same build process as modrinth, my fork just try to have all the same as modrinth but for my personal use, the issue is with modrinth (i tested modrinth too and still failing)

[MiguVT]

Maybe 0.10.3 fix it, i will sync my fork.