Build Configuration Controls
Build configuration controls change the protected artifact AppTego produces. Use them when QA, CI, simulator or emulator testing, or release packaging requirements need a different artifact shape than the default production build.
Keep these settings tied to the purpose of the build. A QA artifact may need simulator or emulator support; a production artifact should usually include only what your release channel and supported devices require.
Control Matrix
| Control | Platforms | Minimum plan | Execution | Use when |
|---|---|---|---|---|
| Include Simulator Architectures | iOS | Enterprise | Build-time | QA or CI needs simulator-compatible protected builds. |
| Include x86 Architectures | Android | Enterprise | Build-time | QA or CI needs emulator-compatible protected builds. |
These are build submission settings, not runtime detections. Changing either setting requires creating a new protected artifact.
Release Guidance
| Environment | Recommendation |
|---|---|
| Development | Include simulator or emulator architectures when they help local validation. |
| Staging | Match the intended QA device pool. Use physical-device builds when validating final security behavior. |
| Production | Ship only the architectures required by your distribution channel and device support policy. |
Testing Notes
Simulator and emulator support is useful for automation, but some controls depend on physical-device behavior. Attestation, device posture, screen capture, network, and runtime tamper checks should be validated on physical devices before Production release.
Decision Checklist
| Question | Recommendation |
|---|---|
| Is this build for local QA or CI? | Enable simulator or emulator support only when the test environment requires it. |
| Is this build for release? | Match app store, MDM, or enterprise distribution requirements and test on physical devices. |
| Did build settings change? | Create a new protected build and repeat the relevant installation and control checks. |
| Are automated tests passing but device tests failing? | Compare architecture settings, signing, OS version, and physical-device-only controls. |