Apps

Why an app shows as a canister id instead of a name

All help topics

The console names and groups apps from variables their canisters carry; a canister deployed without them is listed as an app of its own, named by its canister id.

  1. Set these canister environment variables on the app's canisters, for example in your project's icp.yaml:
  • __META_PROJECT: the app's name. Give every canister of the app the same value; canisters that share it are listed as one app.
  • __META_NAME: each canister's own label, like Frontend or Backend.
  • __META_MAIN_CANISTER: true on the one canister the app opens at, usually the frontend.
  • Optional, on that main canister: __META_BASE_URL (an https address the Open button uses) and __META_ICON_PATH (the icon's path under it, like /favicon.svg).
  1. Deploy the canisters again.
  2. Reload Your apps and services: the canisters show as one app, under its name.
Good to know
  • Easiest: ask your coding agent. The deploy-to-cloud-engine skill that the Build with agents prompt installs knows these variables.
  • To see what a canister carries, open its page and look under Environment, App metadata.
  • A canister with a __META_NAME but no __META_PROJECT is listed alone, under that name.
  • One app split over several rows usually means its canisters carry different __META_PROJECT values.
  • Apps installed with Upload a bundle are named after the bundle, and Caffeine and OpenSaaS apps name themselves.
  • The variables only change how the console lists the app; your app's code doesn't read them.

More about the same page

Still stuck? Contact support