bejibx

I'm trying to communicate with [Cypress FX3 chip](http://www.cypress.com/products/ez-usb-fx3-superspeed-usb-30-peripheral-controller) using your library but with no luck for now. Don't know what kind of serial device they use though.

[Here](https://developer.android.com/studio/build/dependencies#dependency_configurations) is Android documentation about dependency configurations. So if add PaperParcel dependency like this: ``` implementation "nz.bradcampbell:paperparcel:2.0.7" kapt "nz.bradcampbell:paperparcel-compiler:2.0.7" ``` I cant build my project because classes from ```paperparcel-api``` module...

So I create sample project to check this is not some weird issue with my main project and still got same behavior. ```build.gradle``` file is pretty standard: ```groovy apply plugin:...

Could this be related to how this library is packaged? Maybe we should update some gradle plugin to properly support new dependency configurations?

Maybe [this](https://discuss.gradle.org/t/maven-publish-plugin-does-not-include-dependencies-in-generated-pom-xml-file/10113) will be helpful? Or probably we should update [android-maven-gradle-plugin](https://github.com/dcendents/android-maven-gradle-plugin)?

Can you please specify reproduction steps a bit more clearly? I can't quite understand how exactly should I "remove all fragments and add another" to reproduce this issue.

Thank you for clarification! I'll look at this issue soon.

So yeah, it is definitely a problem. I kinda want to stop using those hacky solutions but it seems there is no official way to check if fragment is removing...

So it seems for me we have 3 options to fix this: 1. Reset `isStateSaved` flag for fragments in backstack. It seems like when you hide and show application no...

So we had some internal discussion about this issue and also I've done some research which led to creating [new issue](https://issuetracker.google.com/issues/172905771) in androidx.fragment library. Basically android fragments using `mBackStackNesting` field...