Frequently Asked Questions

What upload types does Emerge support?

See our Supported Artifacts documentation for supported artifacts.

Is Emerge SOC 2 certified?

Yes, Emerge Tools is SOC 2 Type I certified and conducts annual penetration testing.

Does Emerge support SSO (single sign-on)?

Yes, Emerge supports SSO (single sign-on) for Enterprise accounts.

We currently support these SSO providers: AuthO, Okta, OneLogin, and Google Workspace.

Please contact us if you need help setting up SSO for your team.

How do I add a new product to my Emerge dashboard?

No need to manually add any information, simply upload a build from the new app or framework you're trying to include, and Emerge will automatically create the new product on your Dashboard.

What access does the Emerge integration require?

Currently, there are no Emerge products that require access to source code. The Emerge integration works by analyzing final binary products in the development process.

Do I need to specify the archive zip path for our Fastlane Emerge lane?

Yes! Here is an example of Emerge upload lane that specifies the file path:


platform {:ios/:android} do
  lane :app_size do
    emerge(file_path: "path to .xcarchive or .aab")

After each upload, how long does Emerge retain the artifact?

Currently, we retain the artifacts permanently until deletion is requested.

A core feature of our tool is the ability to see how the size trend changes over time, deleting the artifacts would cause that data to no longer be available.

Please contact us if you would like to request that an artifact be deleted.

Does Emerge support Dexguard or other proprietary obfuscation solutions?

Yes! Emerge supports deobfuscation for any Dexguarded build. Emerge requires uploading any mapping files generated by Dexguard as a part of your upload.

Contact your Emerge representative for details on what mapping files to provide and how to provide them.