Project settings
Studio's settings forms read and write the open project's waid.config.json.
They are a front end for that file, not a separate store: anything you set here
is a key you could have typed yourself, and anything you typed yourself shows up
here.
See App configuration for what each key means to the build.
Identity#
Three fields, all written to the top level of the config:
| Field | Config key | What it is |
|---|---|---|
| Display name | name | The name shown in generated apps. |
| Universal name | appUniversalName | A stable lowercase namespace for the app. |
| Native URL scheme | nativeUrlScheme | Reverse-DNS scheme for native callbacks, e.g. com.yourcompany.demo. |
Changing the app's identity after it has shipped is not free. Stored data and
granted permissions are scoped to the app's name, so renaming orphans them.
Renaming is data-safe, except for name
covers the rules.
Icon#
Pick an SVG and a background colour. The preview shows the icon as the packager will render it, not as your artwork looks in a browser: it is flattened to a silhouette in your chosen colour, which is what the Android adaptive icon pipeline produces. If your artwork depends on its own colours, the preview is where you find that out rather than after a build.
iOS profile#
Only relevant if you build for a physical iOS device.
| Field | What it is |
|---|---|
| Bundle ID | Required for physical-device builds. |
| Development team | Picked from the signing teams found on this machine. |
| Provisioning profile | The name of an installed profile. Leave empty for automatic selection. |
If the config names a team that is not currently available on this machine, Studio still shows it, marked as unavailable, rather than silently dropping it. A team you cannot see is a build that will fail with a confusing error later.