Missing beatmaps and skins after update

[Tyfaspo]

Type

Game behaviour

Bug description

After new update I have no maps nor skins in-game, however all my settings such as gameplay cursor scale are still being used correctly except binds and scroll speed. All files are still intact in the folder.

I have tried redownloading AppImage file and manually select the folder but still has this issue.

System:
Arch Linux
Using official AppImage to launch the game. Never used custom installation folder.

Screenshots or videos

In-game:

Inside one of files subfolder

find ./ | fzf

returns 109k files inside /osu/files folder

Version

2025.118.0

Logs

compressed-logs.zip

[cjwrecks]

Having the same issue here on Arch Linux with the AppImage. Another thing I noticed is that my "files" folder in lazer is still the same size as it was pre-update meaning the files for these skins and maps are still there but I guess aren't being read? I tried seeing if maybe downgrading and running the update before this (which worked for me before) would read those files and still have my maps and skins but still nothing.

[peppy]

2025-01-19 15:47:45 [error]: Realm startup failed with unrecoverable error; starting with a fresh database. A backup of your database has been made.
2025-01-19 15:47:45 [error]: Realms.Exceptions.RealmFileAccessErrorException: History schema version not consistent
2025-01-19 15:47:45 [error]: at Realms.NativeException.ThrowIfNecessary()
2025-01-19 15:47:45 [error]: at Realms.SharedRealmHandle.Open(Configuration configuration)
2025-01-19 15:47:45 [error]: at Realms.RealmConfiguration.CreateHandle(Configuration& configuration)
2025-01-19 15:47:45 [error]: at Realms.RealmConfigurationBase.CreateRealm()
2025-01-19 15:47:45 [error]: at Realms.Realm.GetInstance(RealmConfigurationBase config)
2025-01-19 15:47:45 [error]: at osu.Game.Database.RealmAccess.getRealmInstance()
2025-01-19 15:47:45 [error]: at osu.Game.Database.RealmAccess.prepareFirstRealmAccess()

2025-01-19 15:47:45 [verbose]: Creating full realm database backup at client_1737301665_corrupt.realm

Dunno, maybe a realm side error?

Can you try copying the backup database back to client.realm and see if it does the same thing a second time?

[cjwrecks]

I renamed the client.v23.backup.realm to client.realm and backed up the one created after the update and now my maps, skins, etc are all back. I'm just wondering now if this is an isolated issue or if it's somehow an issue with the newest release maybe specific to the AppImage?

[Tyfaspo]

Same as with @cjwrecks, renamed backup into cleint.realm and maps, skins, etc are back. Thanks for that solution. But why that happened in the first place?

[Tabisch]

Had same issue.
Restoring client.realm worked.

[SHOESKE-H]

On LTS Kubuntu 24.04, same issue. Renaming to client.realm solved this

[ticotaco72]

also happens with 2025.118.2-lazer on Fedora 40, renaming the backup seems to resolve the issue

[peppy]

See realm/realm-swift#8731, realm/realm-swift#8703, I don't know what the solution here is and I'd say it's very unlikely to get a fix from realm's end. That said, it does look to be limited in scope (and only happened to linux users).

Does anyone happen to have a copy of their database which can trigger this issue 100%?

[cjwrecks]

If you are asking for the realm.client file that was causing the bug I did end up backing it up. [https://drive.google.com/file/d/1xGkmxdZxyYYFwGahxcq3tIp9ge7M5cJp/view?usp=sharing]

[ticotaco72]

I believe everyone has a backup as realm created at least two identical backups for me. One named client.v23.backup.realm and client_1737326229_corrupt.realm. After the operation with renaming the db and getting beatmaps back, client.v23.backup.realm file was recreated with the same content as before (MD5 match between all three backups).

[ticotaco72]

Putting the original 'bad' db back into the game doesn't recreate the issue.

[peppy]

@nirinchev excuse me for pulling you in here, but we've had at least five users have realm report an issue on realm version migration (Realms.Exceptions.RealmFileAccessErrorException: History schema version not consistent). All users have been on linux. This follows a recent package bump from 12.0.0 to 20.1.0.

On a second attempt to migrate using a backed-up copy of the realm database (we make automatic backups in the case of a startup failure), the user has no issue. I'm not sure how this can happen.

I found (realm/realm-swift#8731, realm/realm-swift#8703) which both look similar, but this looks like a relative high effort investigation/fix which I presume the realm/mongo team won't have bandwidth to fix. If you have any quick hints or recommendations that would be appreciated, else I guess we just have affected users restore their database and carry on with life.