[Bug]: Migrate Akavache 10 → 11

[dmitriypetrukk]

Describe the bug 🐞

Hi, I’m upgrading my MAUI application from .NET 8 → .NET 9 and Akavache 10 → 11.

According to the documentation, Akavache v11 should automatically migrate
the legacy v10 SQLite database the first time it is accessed:

https://github.com/reactiveui/Akavache/blob/main/docs/migration-v10-to-v11.md

However, the migration does not happen — Akavache always creates a brand new
empty database. As a result, all users get logged out after the update because
the cached authentication token is lost.

I tested both:

• iOS Simulator
• real iOS device via TestFlight

In both cases the v11 app does not detect or migrate the existing SQLite DB.

I attach:

• my old Akavache v10 CacheManager (working)
• my new Akavache v11 CacheManager

Files:

• cacheManager-OLD.rtf
• cacheManager.rtf

I want to understand:

• Is my migration code correct?
• Is auto-migration supported when using WithAkavacheCacheDatabase?
• Is there an additional step required to enable migration?
• Or is this possibly a bug in v11?

Thank you!

Step to reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Reproduction repository

https://github.com/reactiveui/ReactiveUI

Expected behavior

When upgrading from Akavache v10 to v11, the new version should automatically
detect and migrate the existing legacy SQLite cache database created by v10,
as described in the migration guide.

After launching the app with Akavache v11 for the first time, all previously
stored data (including authentication tokens) should remain available, and
users should stay logged in without needing to re-authenticate.

Screenshots 🖼️

No response

IDE

Rider macOS

Operating system

Mac OS

Version

No response

Device

iPhone

ReactiveUI Version

No response

Additional information ℹ️

No response

[WilliamWatterson86]

@dmitriypetrukk - were you able to access your old data? Having same issue here and was hoping you had a workaround or steps you followed?

[dmitriypetrukk]

@WilliamWatterson86 Hi! Unfortunately, we weren’t able to migrate Akavache SQLite data directly from v10 to v11.

As a workaround, we temporarily extracted the critical data from the v10 cache and stored it in SecureStorage, then restored it into Akavache after initializing v11.

It’s not ideal, but this was the only reliable way we found to preserve user data during the upgrade. We couldn’t get the built-in migration to work without data loss.