-
Technical task
-
Resolution: Done
-
P2: Important
-
None
-
None
-
None
Verify the Qt content can handle normal Activity lifecycle events, such as going into background and returning to the front.
Prerequisites: Have an Android app with a QtQuickView in it.
Things to verify:
- onPause/onResume:
- open the app
- verify the QtQuickView is rendering its contents correctly, able to interact
- switch to another app/go back to home screen without using the back button
- navigate back to the test app
- verify the QtQuickView is still rendering its contents correctly and can be interacted with
- second instance of the hosting Activity started
- launch the app's Activity where QtQuickView is embedded in
- verify the QtQuickView is rendering its contents correctly, able to interact
- launch another instance of the same Activity (you can e.g. have a button in the UI which launches an Intent to launch the same Activity, or use adb)
- is the QtQuickView behaving as expected?
- return back to the first instance - is the QtQuickView behaving as expected? (you can use the back button to navigate back to the previous instance)
- onCreate/onDestroy
- repeat the steps from 2., but after step 2.5, continue with...
- launch a second instance again. is everything still initialized correctly, Qt does not crash or get stuck, QtQuickView behaving as expected?
- Note, this assuming back button destroys the Activity, this is not always the case, depends on Android version, device, etc. Make sure with e.g. logging that the Activity's onDestroy() gets called
- resulted in
-
QTBUG-125199 Pausing and resuming Q4A apps can start the virtual keyboard
-
- Reported
-
-
QTBUG-125145 Starting a new Activity with embedded QML crashes when one already exists
-
- Closed
-