Paul Woitaschek

We always use named arguments for almost everything so that changing the position doesn't break existing code. When developers add a dependency to a class, they usually add it at...

That case could still be covered with a secondary constructor if that really ever comes up, right?

That sounds like a good plan! We should also provide good error messages on this and explain the importance of the ordering. I really like how you take care of...

We can borrow what assertion libraries do. Expected,,, but did not have, ... Different order... That code already exists and is open sourced.

Note: it looks for the okio dependency on my machine (`/Users/...`)

I can no longer reproduce this.

Was just shadowed by another issue. Still happening.

Still happening.

It does not exist. But wait; we're not using sentry-android-ndk. It seems the plugin adds that, where we add the 6.0.0 core dependency. Maybe this is related to the plugin...

Yes, confirmed. Setting the version in the autoInstallation block fixes it. I think this is a dependency issue: In a gradle module we have a dependency on sentry-core using 6.0.0....