Page Comparison

...

1. CI/CD should be enabled for your Android pre-prod build.

2. As part of the upload step, a mapping file should be included while uploading the app binary. This mapping file should be the same mapping file that was generated while building the apk binary in Android Studio. The location of the generated mapping file depends on your proguard settings in your Android project. The mapping file should be included as a sourcemap option in your CI/CD upload step as follows:

   Code Block
   $ curl -F file=@androidapp.apk -F sourcemap=@mapping.txt https://prod-dopinder-v2.securetheorem.com/_ah/upload/Aewsadw[...]/

3. Once a mapping file has been uploaded for a specific pre-prod app, all subsequent uploads will require a corresponding mapping file for scans to be completed. The mapping file requirement can be disabled by making a PATCH request with the requested setting as the body of the request to the Mobile Apps endpoint in the Results API v2 to disable it as follows:

   Code Block
   curl --request PATCH https://api.securetheorem.com/apis/mobile_security/results/v2/mobile_apps/:mobile_app_id --data '{"scans_require_mapping_file": false}' -H "Authorization: APIKey ..."

   If you are running the above curl request on a Windows machine CLI, you would need to escape the quotes for the request body in order for the api call to succeed. For example:

   Code Block
   ... --data \"{\"scans_require_mapping_file\": false}\" ...

4. If there are no issues with the validation of the uploaded build and mapping file, the de-obfuscated scan results will show up in the portal. If there are any issues with the de-obfuscation, please reach out to support@datatheorem.com.

...