Hi, KMP community, during the development of the KMP + Compose UI application, I encountered an iOS-only UI issue.
The problem looks like, when using the application in some random moment of the time, screens stay black, and when I click to another tab in half a second, I see the past screen and then the black screen, it’s also strange moment because during the click to a new tab I should see on the second current screen not a past screen.
Also, one of my screens has a player with auto start. This screen was created natively on iOS, and when this bug appeared, the player did not start.
Only screens that are inside the tab bar have this issue. The TabBar component is still visible and clickable, and the user can interact with the navigation component, but not with any screen inside.
For navigation(NavHost) and screen UI using a native Android/KMP components, nothing native for IOS, at least on Swift code from our side.
Solving the problem is possible if I relaunch the app.
The algorithm to reproduce this bug is as follows:
The app should not be running. I need to open the app, click on a tab (in my case, the last one), then immediately switch to the next tab and back, all within around 10 seconds. If the issue was not caught, I need to kill the application and start again. During the 10 rounds of this algorithm, I can reproduce this issue.
It’s not a universal algorithm, but it works. My result after testing:
Using these physical devices, I can reproduce this issue.
iPhone 13 Pro Max, iOS 17.6.1
iPad Pro 12.9, iOS 18.5
iPad Pro 12.9, iOS 18.6.2
Devices where I can’t reproduce this issue.
iPhone SE 2022, iOS 18.5
Unfortunately, I am limited in the number of Physical Devices, but it looks like this problem may also depend on screen size. On iPad, this problem is possible to catch super fast, following the algorithm above
Project details:
Minimal version of iOS project is iOS 16.
Kotlin version 2.2.0
Compose Multiplatform 1.8.2
AGP 8.8.2
AndroidX Navigation 2.9.0-beta03
AndroidX Lifecycle 2.9.1
Do you know where the issue is, or perhaps someone has already encountered this problem and solved it?