Does AndroidViewRendering / AndroidScreen break Compose integration?

[rjrjr]

The swizzle in ViewRegistry.mapFactories seems to have assumed assume that it was downstream of the AndroidViewRendering swizzle. It isn't.

Compose sample choked on AsIs with this, and spookily works just fine when I delete the check. So...is this transformation actually necessary? Has AndroidViewRendering been broken all along? Will have to check.

Originally posted by @rjrjr in #577 (comment)

[rjrjr]

The transform is used to apply WrappedWithRootIfNecessary to ComposeViewFactory instances, so if we wrapped one of those in AndroidScreen or something, and it really was the topmost entry into Compose, things will break. Landmine.

I think the real fix will be in ViewRegistry itself. We keep being bit by its inability to support this kind of mapping. The current overhaul is our last chance to address that.

Yikes.

[rjrjr]

It did, but that's fixed by ScreenViewFactoryFinder.