When building java packages assigned to the module we don't put jar target to any dependencies chain except the 'all' one. This causes an issue since androiddeployqt expects .jar files are built when scanning and processing '-android-dependencies.xml' files of the Qt modules.

'-android-dependencies.xml' is generated without any obligation that the files mentioned in it are created and ready to be deployed when deploying any target using androiddeployqt.

We can add the target level Qt modules dependency to the associated jar target and use the jar targets as the input source for the -android-dependencies.xml files.