Peter Leibiger

Maybe skip all `RenderProxyBox` objects and straight visit the child?

We have removed `DioError` in the `6.0.0` branch - see https://github.com/cfug/dio/pull/1825 So at some point in the future `sentry_dio` needs a breaking change as well.

I noticed that 0.5.13 raises the min iOS version to 15 - maybe that is related.

This only works if the background isolate is started in the same VM. Something might have changed in the workmanager library.

Edit: Meant to post in the dio issue.

I am getting this as well. According to the tags, v0.4.9 is from Nov. 2015? I am currently using the code from master.

The error above comes from the `SQLite.swift` pod, so yea, that is probably the cause of the problem. No idea how to fix it.

Drift can use sqlite3, depending on your development targets you can use https://pub.dev/packages/sqlite3_flutter_libs Here are the docs https://drift.simonbinder.eu/docs/platforms/ they also explain why certain things are faster.

My bad, actually `drift` always uses `sqlite3` under the hood these days. So `drift` is the wrapper that you are trying to build. `sqflite_common_ffi` also just wraps `sqlite3`. `sqlite3` should...

From what I remember, there are no useful exceptions in a lot of cases. Wonder if we could add some sanity checks for common problems and provide suggestions.