Skip to end of metadata
Go to start of metadata
Build Android Apps with the Required Xamarin Settings
To build an Android app with the required Xamarin settings
- In Xamarin Studio, right-click the Android project in the Solution Pad and then select Options.
- Under the Build section of the Project Options dialog, click Android Build.
- From the Configuration menu, select Release. By default, the Debug option is selected. You need to build the app in Release mode before you can distribute it to users. Release mode turns off the shared runtime and turns on linking so that the application only ships the pieces of Xamarin.Android required at runtime.
- On the Packaging tab:
- Clear the User shared Mono runtime and Fast assembly deployment check boxes.
- Select the Embed assemblies in native code check box.
- On the Linker tab: From the Linker behavior menu, select Link all assemblies.
- Click OK to save the Android Build settings.
- Right-click the Android project again and select Clean.
- From the menu next to the Run button at the top-left of the Xamarin Studio window, choose Release | x86 to specify the release build.
- From the Project top menu, click Create Android Package. You will see a status window, and then the Create Android Package dialog.
- On the Create Android Package dialog, leave the default settings or specify a different Target Directory and File name.
- Click OK to build the Android package.
- In a file browser, change to the target directory for the Android package. This is the directory specified in step 10. In this directory, you should have a bin folder that includes a Release folder. The Release folder includes a
Filename.apk (unsigned) and
Filename-Signed.apk (signed) version of the app. The unsigned version (
Filename.apk) is the app that you should add to Digital.ai App Management. Do not add the signed version. For instructions on adding apps to Digital.ai App Management, see Add an Application.
After you add the app to Digital.ai App Management you must sign it. If you want to apply policies, apply the policies before you sign it (since you are required to sign an app after you apply policies the first time). If you do not want to sign with Digital.ai App Management, you can manually sign it with the
jarsigner utility before you add it, or you can upload it, apply policies, and then download a signing package to sign the version with policies outside of Digital.ai App Management. For more information on signing apps, see About Signing.