How to Optimize File Size when Obfuscating Android & iOS apps
Learn to Prevent obfuscation of publicly available components in Mobile apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.
Why Prevent Obfuscation of Publicly Available Components?
Obfuscation reduces the efficiency of compression algorithms, so obfuscating all the code in the app may increase its file size significantly. Excluding publicly available elements for obfuscation decreases the size of the built app.
Which Libraries are Excluded from Obfuscation?
If you enable Favor App Size, the following libraries will remain unobfuscated:
Open Source Libraries:
|libopencv_imgproc.so, libopencv_core.so, libopencv_java3.so||https://opencv.org|
libmonodroid.so, libmono-btls-shared.so, libmonosgen-2.0.so, libe_sqlite3.so
libfb.so, libfolly_json.so, libglog.so, libglog_init.so, libgnustl_shared.so, libicu_common.so, libimagepipeline.so, libjsc.so, libprivatedata.so, libreactnativejni.so, libyoga.so. libc++_shared.so
libunity.so, libil2cpp.so, libcri_ware_unity.so, libgpg.so
libxwalkcore.so, libxwalkdummy.so, libsqlcipher.so
IMPORTANT: Some applications which come with anti-tampering might clash with Appdome’s binary code obfuscation. Read this article to learn about Appdome’s Anti-Tampering functionality.
Preventing obfuscation of publicly available components on Mobile apps by Using Appdome
On Appdome, follow these 3 simple steps to create self-defending Mobile Apps that Prevent obfuscation of publicly available components without an SDK or gateway:
Upload the Mobile App to Appdome.
Upload an app to Appdome’s Mobile App Security Build System
Upload Method: Appdome Console or DEV-API
Mobile App Formats: .ipa For iOS device or .apk or .aab
Build the feature: Binary Code Obfuscation > Favor App's Size.
Congratulations! The Binary Code Obfuscation > Favor App's Size protection is now added to the mobile app
Building Binary Code Obfuscation > Favor App's Size by using Appdome’s DEV-API:
Create and name the Fusion Set (security template) that will contain the Binary Code Obfuscation > Favor App's Size feature as shown below:
Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Binary Code Obfuscation > Favor App's Size feature via Appdome Console, to add the Binary Code Obfuscation > Favor App's Size feature to this Fusion Set.
Open the Fusion Set Detail Summary by clicking the “...” symbol on the far-right corner of the Fusion Set, as shown in Figure 1 above, and get the Fusion Set ID from the Fusion Set Detail Summary (as shown below):
Figure 2: Fusion Set Detail Summary
Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).
Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, App Center, Jenkins, Travis, Team City, Cirlce CI or other system:
Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
Look for sample APIs in Appdome’s GitHub Repository
Figure 1: Fusion Set that will contain the Binary Code Obfuscation > Favor App's Size feature
Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).
Building the Binary Code Obfuscation > Favor App's Size feature via Appdome Console
To build the Binary Code Obfuscation > Favor App's Size protection by using Appdome Console, follow the instructions below.
Where: Inside the Appdome Console, go to Build > Security Tab > TOTALCode™ Obfuscation section
How: Toggle (turn ON) Binary Code Obfuscation > Favor App's Size, as shown below.
Figure 3: Prevent obfuscation of publicly available components option
When you select the Binary Code Obfuscation > Favor App's Size you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Binary Code Obfuscation > Favor App's Size
Figure 4: Fusion Set that displays the newly added Binary Code Obfuscation > Favor App's Size protection
Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
Certify the Binary Code Obfuscation > Favor App's Size feature in Mobile Apps.
After building Binary Code Obfuscation > Favor App's Size, Appdome generates a Certified Secure™ certificate to guarantee that the Binary Code Obfuscation > Favor App's Size protection has been added and is protecting the app. To verify that the Binary Code Obfuscation > Favor App's Size protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below:
Figure 5: Certified Secure™ certificate
Each Certified Secure™ certificate provides DevOps and DevSecOps organizations the entire workflow summary, audit trail of each build, and proof of protection that Binary Code Obfuscation > Favor App's Size has been added to each Mobile app. Certified Secure provides instant and in-line DevSecOps compliance certification that Binary Code Obfuscation > Favor App's Size and other mobile app security features are in each build of the mobile app
Prerequisites to Using Binary Code Obfuscation > Favor App's Size:
To use Appdome’s mobile app security build system to Prevent obfuscation of publicly available components , you’ll need:
- Appdome account (create a free Appdome account here)
- A license for Binary Code Obfuscation > Favor App's Size
- Mobile App (.ipa For iOS device or .apk or .aab For Mobile)
- Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)
Using Appdome, there are no development or coding prerequisites to build secured Mobile Apps by using Binary Code Obfuscation > Favor App's Size. There is no SDK and no library to code or implement in the app and no gateway to deploy in your network. All protections are built into each app and the resulting app is self-defending and self-protecting.
Releasing and Publishing Mobile Apps with Binary Code Obfuscation > Favor App's Size
After successfully securing your app by using Appdome, there are several available options to complete your project, depending on your app lifecycle or workflow. These include:
- Customizing, Configuring & Branding Secure Mobile Apps
- Deploying/Publishing Secure mobile apps to Public or Private app stores
- Releasing Secured Android & iOS Apps built on Appdome.
All apps protected by Appdome are fully compatible with any public app store, including Apple App Store, Google Play, Huawei App Gallery and more.
Features Similar to Binary Code Obfuscation > Favor App's Size
Here are a few related resources:
- Binary Code Obfuscation, Anti-Reversing for Android & iOS Apps
- How to Encrypt Java Class Files (.dex) in Android Apps
- How to Optimise Load Time, Code Obfuscation Best Practices in Android & iOS Apps.
- Dex Control Flow Relocation, Anti-Reversing for Android Apps
- Non-Native Code Obfuscation, Anti-Reversing for Android & iOS Frameworks
If you have any questions, please send them our way at support.appdome.com or via the chat window on the Appdome platform.
Thanks for visiting Appdome! Our mission is to secure every app on the planet by making mobile app security easy. We hope we’re living up to the mission with your project.