Versions Compared

Old Version 1

changes.mady.by.user Alban (Unlicensed)

Saved on

compared with

New Version 2

changes.mady.by.user Roy Racho (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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 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://prod-dopinder-v2.securetheorem.com/_ah/api/resultsapi/v2/mobile_apps/1234567890? --data '{"scans_require_mapping_file=False": true}' -H "Authorization: APIKey ..."

  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.

...