Post

Thanks for sharing, I hadn't heard of that issue before. Is that specific to GRDB, or can it happen with Core Data/SQLite storage in app group containers too?

This is possible now as I am removing the legacy Intents that read/write from these DBs. The new AppIntents are run in the main app process and widgets use a readonly JSON file that is reactively updated.

Interesting! So you maintain a copy of some data for widgets only? And refresh the data arbitrarily? What about widget writes?

Yes. I don't refresh arbitrarily, it's updated reactively from DB changes in the main app process. For interactive widgets, use ForegroundContinuableIntent: stackoverflow.com/a/76673642/1...

Great move 👏 The best advice to anyone who wants to share an SQLite db is DON'T. The operating system will make your life so very difficult 😅

It's the first time I read someone advocating against using an app group to share a database between multiple processes. It could be a good topic for a technical blog post Ryan 🤩

I plan to! Release is going out as we speak. Want to make sure that goes smoothly before writing about it.

I understand why it happens (more or less) but this has to be one of the most frustrating iOS dev things. I just want to read from my db from all the extensions we now need!

I wholeheartedly agree. I think Apple recognized this when they designed App Intents to be allowed to run in the main app process. What extensions are you maintaining that still need a DB connection?