These are some common issues that you may encounter when configuring the DashO™ Gradle Plugin for Android. PreEmptive Protection™ DashO has its own troubleshooting section here.
Verifying the plugin is available
You can verify the plugin is installed correctly by running gradlew tasks. If you properly applied the com.preemptive.dasho.android plugin, you should see a dashOPluginVersion task listed under the Help tasks section.
DashO Home Issues
DashO x.y or later not found. Please set the DASHO_HOME property, or set 'home' or 'searchVersion' in the 'dasho' closure in your buildscript.
DashO Home was not specified using any of the ways described in Configuring DashO Home. You may see this message if the installed versions of DashO that were found are incompatible with this version of the plugin.
Specified DashO Home '[file path]' is not valid
Make sure that the directory that you specified contains the DashOPro.jar file. If using DashO Gradle Plugin for Android v1.1.x, the specified directory should also contain the Encrypter.jar file.
DashO version 'x.y' was not found. Could not find {some jar}. Please use a different version or set DashO Home.
When the plugin searches for the specified version of DashO, it may fail if it finds an installation of DashO, but the installation does not contain the expected jar. This may happen if specifying a specific version, e.g. 10.1, which does not contain the required Encrypter.jar. Verify the specified searchVersion contains a supported version of DashO. You may also directly configure the location.
Option --pathMap not understood
You are using a version of DashO that is not compatible with the DashO Gradle Plugin for Android. The plugin is compatible with DashO 10.x and later.
Other Configuration Issues
Could not get unknown property {some property} for object of type com.preemptive.dasho.gradle.DashOExtension.
Verify you have correctly spelled the property. This can also occur if you try to set javaOptions, libraryAssetDirs or libraryResourceDirs using an equals sign (e.g. javaOptions = "-Xmx512m"). Do not use the = (e.g. javaOptions "-Xmx512m").
Error: Could not find method libraryAssetDirs() (or libraryResourceDirs()) for arguments...
This can occur if you try to configure libraryAssetDirs or libraryResourceDirs with v1.1 or earlier. These options were added in v1.2.
Error: You must use an Android Mode configuration file with the DashO Gradle Plugin for Android.
The DashO configuration (.dox) file that you are using with DashO is not configured for Android Mode and needs to be migrated.
Changes were not applied. {Some Reason}
You may see this issue, with a reason like JVMTI error: JVMTI_ERROR_UNMODIFIABLE_CLASS or Adding classes requires an app restart, if attempting to use Apply Changes when you have enabled DashO on debug builds. Apply Changes is not compatible with the changes performed by DashO.
Exclude pattern '{pattern}' did not match any inputs: {list of names}
The pattern provided did not match any of the inputs provided to the DashO transform. Double-check the pattern against the list of names below the error message. As mentioned in Excluding from Protection, if other transforms run before the DashO transform the names may be corrupted.
Warning: ProGuard appears to be enabled instead of R8.
You will receive this warning if ProGuard appears to be enabled instead of R8. ProGuard may not correctly handle classes processed by DashO, and could issue fatal errors when attempting to process them. We strongly recommend using R8 rather than ProGuard with the DashO Gradle Plugin for Android.
ProGuard will run instead of R8 if you are using a version of the Android Gradle Plugin prior to 3.4.0 without manually enabling R8. ProGuard will also run if you have disabled R8 by setting android.enableR8=false in your gradle.properties file.
You can enable R8 by setting android.enableR8=true in your gradle.properties file. See Enabling R8 for details.
Warning: minifyEnabled is false for build type "[current build type]".
You will receive this warning if minifyEnabled is not set to true for the build type of a variant on which DashO is running. This means that R8 will not process the classes protected by DashO. Running R8 alongside DashO is essential for full protection of your application or library when using the DashO Gradle Plugin for Android.
See Enabling R8 for details.
A problem occurred configuring project {some name}. {Maybe some additional information}
If you attempt to use DashO Gradle Plugin for Android v1.1.x (or later) with Android Gradle v3.2.x, you may see ASCII as the additional information. Make sure you have configured a supported version of the Android Gradle Plugin.
Build Task Failures
Execution failed for task ':transformClassesWithInstantRunForDebug'
You will get this error when you build in Android Studio and have enabled DashO for debug builds but have not disabled Instant Run. Either change the variants for which DashO is enabled, or disable Instant Run.
Execution failed for task ':minifyReleaseWithR8'
R8 had an issue processing the classes. Run the Gradle build with a --debug or --stacktrace option to get more details.
One known issue involves R8 throwing a NullPointerException while processing kotlinx.coroutines.internal.MainDispatcherLoader.loadMainDispatcher(). If you see this issue, you can exclude that method from Control Flow processing or exclude kotlinx-coroutines from DashO entirely.
Runtime Failures
Kotlin Coroutines
When R8 is not properly configured, you may get an exception like java.lang.NoSuchFieldException: No field inFlightTasks or java.lang.IllegalStateException: Module with the Main dispatcher is missing.. Please make sure you configure R8 appropriately.
java.lang.RuntimeException: Internal error in Cloud Firestore {version}
One known cause for this relates to String Encryption and Reflection. If you encounter this error, you can exclude the problem code from String Encryption. Here is a list of methods known to cause this error in Firebase version 22.1.1:
io.grpc.LoadBalancerRegistry:getHardCodedClasses()io.grpc.ManagedChannelProvider$HardcodedClasses:iterator()io.grpc.NameResolverRegistry:getHardCodedClasses()
Temporarily Disabling DashO Integration
If you would like to run a build without DashO processing the files, use the DISABLE_DASHO property when you run gradlew.
Troubleshooting Parameters
If you would like to see all the parameters passed to DashO, use the SHOW_DASHO_CMD property when you run gradlew. You can also configure the debug option.
Reviewing DashO's Logs
The output from DashO will go to the console automatically. It is also captured in a log file located at build/outputs/logs/dasho-{variantName}-log.txt.