Skip to content


Application Settings is a completely rewritten API from the legacy Secrets API. This is the evolution of the Secrets API and has an updated name to reflect the real intent as there are many time you are not actually protecting your codebase from actual application secrets as much as simply keeping configuration something that gets injected at build rather than being hard coded.


If you were using a 2.0 preview, the BuildTools will attempt to migrate your configuration over to using the Application Settings

What are AppSettings?

We all have settings that help make our app run whether in development, staging, or production. Some examples might be Client ID's, Backend Uri's, OAuth Scopes we need. When you have any of these sorts of things you can have the Mobile.BuildTools automatically generate one or more classes in your project.

Using the appsettings.json

The Mobile.BuildTools is smart, we look for the appsettings.json in the p

  "AppCenterAppId": "{your app id}",
  "BackendUri": ""


If upgrading to 2.0 and you are using a secrets.json, the secrets.json will continue to work with a build warning. You should convert the file over to appsettings.json as support for secrets.json will be deprecated in a future release.

Variable priority

The Mobile.BuildTools attempts to locate the values for your generated class through several sources. In the event that a variable key is duplicated, the Mobile.BuildTools has a precedence that the last one in wins. Variables are loaded from the following sources

  1. buildtools.json Environment Defaults
  2. buildtools.json Environment Configuration (i.e. Debug, Release)
  3. System Environment
  4. Recursively load legacy secrets.json from the Project directory to the Solution directory
  5. Recursively load appsettings.json from the Project directory to the Solution directory


This variable gathering is additionally used for replacing Manifest tokens