Mesmer does a number of checks automatically to inform you if there are any potential issues when uploading a binary. Checks are performed to ensure that Mesmer automatically functions as expected after you've uploaded a build.
Mesmer supports two types of builds: Standard and Advanced.
A standard build is similar to what you'd upload to the Google Play or Apple App Store. This is all that's required to use most AX Testing features.
An advanced build requires additional configuration to allow:
Keychain Access (iOS)
In both cases, Mesmer will resign the application with its certificate.
Depending on the devices provisioned into your Mesmer Device Cloud, you should prepare the builds as follows)
Zipped .app File
Developer or Enterprise .ipa binary
Enable x86 Flag for .apk Binary
Standard .apk Binary
For Android builds, there are a number of limitations that are encountered in resigning the binary.
Each build should adhere to the following recommended configuration:
Disable Anti-Tampering Tools - Application binaries that are shipped to the public app stores should check for file integrity and certificates. For Mesmer to test an application fully, these types of tools should be disabled.
Enable 3rd Party Certificate - Many applications use third-party APIs such as Google Maps. Mesmer's Android signing certificate should be whitelisted on these services for proper use. Contact email@example.com for the SHA1 signing certificate.
For iOS Builds on physical devices, either an Enterprise or Developer build can be used. Enterprise builds do not require resigning, while developer builds need to be resigned using the Mesmer profile.
Due to resigning, certain applications may experience limited functionality for:
Push Notifications - Notifications will not function properly if a Developer build is uploaded.
Apple Pay - Apple pay will not function properly if a Developer build is uploaded.
Keychain - Certain Apple Key Chain functionality may be limited on a Developer build.