IssueTracker

Jetpack Compose release version: 1.0.0-beta02

Developers not using AppCompat version 1.3+ nor Fragment 1.3+ can hit this ComposeView error (i.e. the need of manually setting owners for ViewTreeLifecycleOwner and ViewTreeSavedStateRegistryOwner) when using ComposeView in a XML file even though ComposeView's setContent method hasn't been called.

These checks seem too aggressive and are done way earlier they're expected. I'd expect these checks to be called when setContent is called, not before.

The workaround seen in the community is creating a ComposeViewStub that they use in XML and replace with a ComposeView at runtime. Then, LayoutParams and id are reassigned, the right owners are set, and setContent is called.