Details
-
Bug
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
Qt Creator 4.4.1
-
None
-
Qt 5.9.2 android armv7
QtCreator 4.4.1
MS Windows 7 SP1
Description
When using gradle to build android app, if user explicit assign different applicationId in the gradle script, then the debugger will fail to start (and the run command too)
In gradle build environment, the real applicationId can be manually assigned, e.g.:
android.defaultConfig {
applicationId "com.yy.xx"
minSdkVersion 16
targetSdkVersion 23
}
The AndroidManifest.xml may have different package name, e.g.
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.yy.aa"> ... </manifest >
In this case, the package of AndroidManifest.xml only affect the package name of R.java, and not the real applicationId.
For the merged (real) AndroidManifest.xml, you can refer:
<shadow-build>/android-build/build/intermediates/manifests/full/debug/AndroidManifest.xml
It looks like QtCreator debugger only look at the user's AndroidManifest.xml, but not the real merged AndroidManifest.xml in android-build folder.