Skip to content

Latest commit

 

History

History
27 lines (17 loc) · 2.03 KB

ConfigureAppSecrets.md

File metadata and controls

27 lines (17 loc) · 2.03 KB

Configure App Secrets

As a best-practice principle, our project conceals app secrets from source code by generating and compiling an AppSecrets.swift source code file at build time using a custom build rule. The same pattern can be applied to your app development as well.

This build rule looks for a secrets file stored in the project's root directory, $(SRCROOT)/.secrets.

Note: License strings are not required for development. Without licensing or licensing with invalid keys do not throw an exception, but simply fail to license the app, falling back to Developer Mode (which will display a watermark on the map and scene views). Apply the license strings when your app is ready for deployment.

  1. Create a hidden secrets file in your project's root directory.
touch .secrets
  1. Add your License String to the secrets file. Licensing the app will remove the 'Licensed for Developer Use Only' watermark. Licensing the app is optional in development but required for production. Add your Extension License String and API Key access token to the secrets file if needed. If the license string is set, an Advanced Editing extension will be required to access all the samples, such as those with utility network capabilities. Learn more about how to Get a license.
echo ARCGIS_LICENSE_KEY=your-license-key >> .secrets
echo ARCGIS_EXTENSION_LICENSE_KEY=your-extension-license-key >> .secrets
echo ARCGIS_API_KEY_IOS=your-api-key >> .secrets

Replace 'your-license-key', 'your-extension-license-key' and 'your-api-key' with your keys.

Visit the developer's website to learn more about Deployment and Security and authentication.

To learn more about masquerade, consult the documentation of Esri's Data Collection app.