What:

When an app has QtQuickViews placed in Jetpack Composes navigation graphs non-start screens, the Views do not render. When checking the log, qtQuickView status also isn’t being set to READY as opposed to the startDestination screen where its status is. This leads to the Views not being rendered.

This happens when:

1. the Views are initialized in onCreate() and then applied at AndroidView() factory and,
2. when they are initialized on a composable function (see picture) and then applied at AndroidView() factory.

When qtQuickView from the code above is displayed in the startDestination, the qtQuickView gets displayed as expected. However, when this code is in a composable view that the navigation structure does not start from, the qtQuickView does not get displayed.

If an XML layout is placed in the AndroidView() were a qtQuickView is failing to render, the XML layout renders without problems

The example project and video showcase 3 instances to highlight problems and difference between expected and actual behaviour:

1. onCreate initialization
2. Compose function initialization
3. Display XML frame

Steps to reproduce:

(Fully restart app every time you reach step 4 and want to choose other options)

1. Open app
2. Click "Navigation Problems"
3. Do not interact with visible QtQuickView (QTBUG-138922)
4. Choose from one of the following:
   1. Click "Remember initialization example"
   2. Click "onCreate initialization example"
   3. Click "XML layout example"
5. Observe behaviour:
   1. EXPECTED / ACTUAL = Visible QtQuickView / No rendered QtQuickView
   2. EXPECTED / ACTUAL = Visible QtQuickView / No rendered QtQuickView
   3. EXPECTED / ACTUAL = Visible XML content / Visible XML content

Example video:

navigation-issue-video.mkv

Example project:
QTBUG-139081.7z
(Note: replace QtBuild file directories in build.gradle with your local installations)