Roman Zavarnitsyn

probably `idleTimeout` can also be moved to AndroidOptions since it's kind of a UI-relevant thing - backend probably won't ever need it

> Any hints how to fix the CI build failure? > > ``` > FAILURE: Build failed with an exception. > Deprecated Gradle features were used in this build, making...

@vaind sorry man, I haven't got time to look at the PR, so I will leave this to @marandaneto as I'm on parental leave starting from tomorrow. Good luck!

I guess you're facing a [similar issue](https://stackoverflow.com/questions/32022842/transitive-aar-dependencies-in-maven), so you probably need to go for the same workaround as mentioned in the answer. Maven by default is looking for a `.jar`...

Oh, indeed, I just looked up and it looks like this is a [Gradle bug](https://github.com/gradle/gradle/issues/3170) actually. Dunno if we should follow the suggested workarounds there @marandaneto or just wait till...

I have a feeling that with some Gradle magic we can actually publish both .aar with proguard rules and .jar without them from a single module, avoiding any breaking changes....

I thought Volley is long dead at this point 🤣

Still not possible?

Also, we'd probably need this to correctly measure the App Startup/Screen TTID, because onResume currently doesn't give you the correct value when the composable is actually rendered. Not sure how...

We need to make sure that the JvmOverloads is enough and properly generates the overloads. Also, check if there's a possibility to lint/analyze the ctors, so we ensure this as...