Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
3.9.2
-
-
MOODLE_39_STABLE
-
MOODLE_39_STABLE
-
Moodle App 3.9.3
Description
C:\Users\diou_\Desktop\moodle\original\moodleapp\platforms\android\app\src\main\AndroidManifest.xml:6: Error: Avoid hardcoding the debug mode; leaving it out allows debug and release builds to automatically assign one [HardcodedDebugMode]
<activity android:configChanges="orientation|keyboardHidden|keyboard|screenSize|locale|screenLayout|smallestScreenSize" android:debuggable="true" android:label="@string/activity_name" android:launchMode="singleTop" android:name="MainActivity" android:theme="@android:style/Theme.DeviceDefault.NoActionBar" android:windowSoftInputMode="adjustResize">
~~~~~~~~~~~~~~~~~~~~~~~~~
Explanation for issues of type "HardcodedDebugMode":
It's best to leave out the android:debuggable attribute from the manifest.
If you do, then the tools will automatically insert android:debuggable=true
when building an APK to debug on an emulator or device. And when you
perform a release build, such as Exporting APK, it will automatically set
it to false.
If on the other hand you specify a specific value in the manifest file,
then the tools will always use it. This can lead to accidentally publishing
your app with debug information.
To resolve this just remove android:debuggable="true" from config.xml