Configure Build Output and Review Results

After you configure what PreEmptive Protection™ DashO™ protects, you decide where the protected build goes and what form it takes. The Output pages control the output format, reports, preverification, and signing. After the build, the Results page shows you what DashO renamed and removed, so you can confirm that your app is protected the way you expect. 

Output Pages

Configure the Output Format

1. In Dasho, navigate to Output.
   

2. Select the output type: Create Directory, Single Jar, APK, or WAR. For more information, see the <output> element.

   Warning: Changing the output type may reset other settings on this page to their defaults. Select the output type before you change other settings.

3. If you output to a directory, choose whether to select Merge Inputs. Merging combines the obfuscated results into a single directory. Leave it cleared to keep the original packaging of the input classes.
4. If you merge inputs, choose whether to select Auto Copy. See Auto Copy Behavior.

5. In the Name field, enter the name of the output directory or JAR file. DashO uses it as the root of the output and attempts to recreate the hierarchy of your original input JARs and directories.

   Note: When Merge Inputs is off, the output must be a directory.

6. (Optional) If DashO creates a single merged JAR, specify a manifest. The manifest can be a text file or a JAR file. DashO extracts the manifest from a JAR file.
7. (Optional) Set the JAR and WAR options. See Jar/War Options.
8. (Optional) Enter a Constant Pool Tag. For more information, see <constpooltag>.
9. (Optional) Enter a SourceFile Tag. For more information, see <sourcefile>.
10. Save your project and build it to apply the changes.

Auto Copy Behavior

Auto Copy controls how DashO handles non-class files when you merge inputs. It's only available when Merge Inputs is on.

Note: When DashO processes non-class files, it may update XML configuration files it finds so they reflect changed class and method names.

Jar/War Options

Configure APK Output

1. Navigate to Output > APK.
   
2. In Build Tools Directory, enter the location of the Android build tools. The directory must contain the zipalign command.

3. (Optional) Select Zipalign to align the output APK with zipalign.

   Note: Zipalign is only available when you sign the APK. 

4. In AAPT Version, choose whether to generate the output APK with AAPT or AAPT2.
5. Save your project and build it to apply the changes.

Generate Build Reports

1. Navigate to Output > Reports.
   

2. Enter the name and location for each report you want:

   Field	Report contents
   Report file	The class and member Removal and Renaming DashO performed. It includes a summary of the total methods, fields, and constant pool entries, and the final number and percentage of reduction. It also lists dynamically loaded classes, including reflection and Class.forName() calls.
   Renaming Report File	The old and new names of renamed classes and their renamed members.

3. Save your project and build it to generate the reports.

Run the Preverifier on CLDC Applications

1. Navigate to Output > Preverification.
   
2. Select Run Preverifier.
3. By default, DashO looks for preverify on the system path. To run a particular version of the preverifier, specify its path in the Preverifier field.

4. Select the restrictions to pass to the preverifier:

   Option	Passes	Restriction
   No Finalize	-nofinalize	No finalizers allowed in the input.
   No Floating Point	-nofp	No floating point operations allowed in the input.
   No Native Methods	-nonative	No native methods allowed.

5. Save your project and build it to apply the changes.

Sign Your Output

DashO signs the JAR, WAR, APK or AAB files it produces. By default, it uses jarsigner from your configured JDK location.

1. Navigate to Output > Signing.
   
2. Select Sign Jars/WAR/APK/AAB.
3. Specify the path to the signing tool if you don't include the JDK, need a particular version of jarsigner, or want to use apksigner. To use the jarsigner executable on the system path, enter jarsigner.
4. Under Key Store, enter the Password. It's the only required key store field.
   • Type defaults to the type the JVM running DashO specifies, such as JKS or PKCS12.
   • Location defaults to the .keystore file in your home directory.
5. Under Signing Key, enter the Alias of the private key. It's the only required signing key field. The Password defaults to the key store password.

6. Set the signing options:

   Option	jarsigner	apksigner
   Signature File	-sigFile	--v1-signer-name
   Internals .SF	-internalsf	Not applicable
   Sections Only	-sectionsonly	Not applicable
   Additional Arguments	-sigalg SHA1withRSA -digestalg SHA1	--v1-signing-enabled [true|false] --v2-signing-enabled [true|false] or --min-sdk-version nn --max-sdk-version nn (where nn is an sdk version)

7. Save your project and build it to apply the changes.

Note: DashO stores passwords that don't contain property references in encrypted form in the project file.

Review Your Build Results

1. Build your project.
2. Navigate to Results.
   
3. Review the class hierarchy of your input classes and the renaming results. The hierarchy doesn't list classes and members DashO removed.
4. Open the reports you configured on the Output - Reports page for a detailed record of Removal and Renaming. 

Limitations and Troubleshooting

Related Articles

• Use the DashO GUI
• Project File Reference
• Manage Inputs