Using androiddeployqt from Qt 6.9.2 or 6.9.3 copies the wrong ABI version of some of our shared libraries into android-build/libs/<abi>. Using androiddeployqt from Qt 6.9.1 works correctly.

For some reason this only affects some of the .so files in our app, and seems to stem from the libraries read via dependency analysis, as changing QT_ANDROID_EXTRA_LIBS to only list the libraries for $ANDROID_ABI has no effect.

It also only happens on our CI build agent, I cannot reproduce it on my own machine using the same Qt versions, app repository state, and build steps. I completely deleted and reinstalled the exact same Qt versions (+ CMake and Ninja from Qt Maintenance Tool) on both the CI agent and my machine without a change in behavior. My guess is that there must be some other tool used by androiddeployqt that is influencing this.

As a reproducer I did the following using androiddeployqt from Qt 6.9.1, 6.9.2, and 6.9.3:

1. Deleted one of the affected libraries from android-build/libs/*.
2. Ran androiddeployqt verbose in aux-mode with the same state of the build dir.
3. Checked the ABIs of the libraries copied into android-build/libs/*.

Attached are the outputs from these 3 runs as well as the deployment settings JSON. When you search for the regex "Copied .*libcrypto_3" you will see that there are 4 results with the correct ABI versions for Qt 6.9.1, but 5 results with incorrect ABIs for x86 and x86_64 with Qt 6.9.2 and 6.9.3.

I made several attempts to analyze the issue including the androiddeployqt source using Codex on the CI agent, unfortunately without a definite result. I’m hoping that the above is sufficient to analyze this for someone with deeper knowledge of androiddeployqt.

Looking at the changes in androiddeployqt I believe the issue must stem from the change for QTBUG-136493 that shipped with Qt 6.9.2.