A modern programming language that makes developers happier.

kotlinlang

Screenshot_1617971738.png

Screenshot_1617971765.png

Screenshot_1617971759.png

Screenshot_1617971754.png

Screenshot_1617971733.png

Hello, everyone! :wave:

I’m facing some issues with Compose and SplitScreen support. When my application first loads in Split Screen, it works fine. But if I try to resize it, the UI no longer loads.
If I resize for a second time, it loads again. Basically, the first resize does work, the second does not, the third does works and goes on.

Is it a Compose issue? Am I doing something wrong?
Could someone help me, please?

Thanks a lot in advance. :heart:

Split screen *can* trigger a configuration change. It should do so as you enter and exit the split-screen mode. It might also do so on a resize operation, depending on circumstances.

So, you might want to play around with configuration changes and see if there is a connection. For example, if you added `android:configChanges` to the manifest for your activity, perhaps you missed a change type that occurs as part of split-screen resizes, and the destroy-and-recreate cycle is breaking things. Or, conversely, perhaps configuration changes are working fine, but resizes that do not trigger a configuration change are the ones that are failing.

Thanks, I will try to take a look! :blush:
At a first glance I’m not adding anything that would break this behavior. Also, landscape is working fine… The only issue seems related to Split Screen.

KI. There's a bug where compose is making an assumption about window decor views across activity recreation for config changes that doesn't hold for certain cases of resizing.

There's a workaround you can do involving creating your own Recomposer; I can post it when I'm at my desk later today

As always, thanks a lot <@UJBKXD0HH>. :blush:

Should I open a IssueTracker or is it already tracked?

(Specifically, Android can reuse the same View instances across activity recreation and Compose ends up using a stale Recomposer stored there that was shut down/inactive when the old activity was destroyed. We'll have a proper fix out soon but it might not make the next beta.)

I think there's one open already, let me check some slack history

<https://issuetracker.google.com/issues/184456605>

<https://issuetracker.google.com/issues/184293033|https://issuetracker.google.com/issues/184293033>

Looks like there's a few :slightly_smiling_face:

is this why the keyboard doesn't trigger recomposition either? <https://issuetracker.google.com/175864912>

Can't see that one from my phone but I can check later. I wouldn't think so unless an activity destroy/recreate is involved

That's a specific requirement for this bug in particular

Copy the contents of this private function to your project <https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/ui/ui/src/androidMain/kotlin/androidx/compose/ui/platform/WindowRecomposer.android.kt;l=206?q=windowRecomposer|https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/[…]platform/WindowRecomposer.android.kt;l=206?q=windowRecomposer>

Call `setParentCompositionContext(recomposer)` with a recomposer you create as outlined there

the one compose is setting is kept in a view tag on the root view of the window and it's getting reused; if you specify your own on a `ComposeView` instance and `setContentView(myComposeView)` instead, you won't see the reuse.

Awesome! Thanks a lot! :heart:
Have a great weekend!