Skip to content
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.

Latest commit

 

History

History
27 lines (17 loc) · 1.78 KB

ConfigureAppSecrets.md

File metadata and controls

27 lines (17 loc) · 1.78 KB
Raw

Configure App Secrets

As a best-practices principle, the 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.

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

Note: License keys 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 keys when the app is ready for deployment.

  1. Create a hidden secrets file in the project's root directory.
touch .secrets
  1. Add your License Key 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 Key and API Key to the secrets file if needed. Acquire license keys from your dashboard.
echo ARCGIS_LICENSE_KEY=your-license-key >> .secrets
echo ARCGIS_EXTENSION_LICENSE_KEY=your-extension-license-key >> .secrets
echo ARCGIS_API_KEY=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.