Skip to content
All changes

Console tabs follow your environment, and environment fixes

A console tab now follows a switch made in another tab, and a closed environment answers 401. The environment menu shows how many your plan allows.

Improved
2
  • EnvironmentsThe console's environment menu now shows how many environments your plan allows besides production. It reads, for example, 1 of 2 environments besides production. At the limit, it offers Upgrade for more environments. Before, a number showed only once an add was refused.
  • ConsoleA downgrade can leave you over your plan's limit on team members, open invitations or environments. Adding one more then says how many to remove. For example, with 4 environments on a plan that includes 2, it says to remove 3.
Fixed
6
  • ConsoleA console tab now follows an organization or environment switch made in another tab of the same browser. Before, it kept showing where it was while its requests went where the other tab went. It now moves there without reloading the page, and a message says where it is.
  • EnvironmentsA request signed in to an archived environment now answers 401 with ENVIRONMENT_NOT_FOUND, instead of a 500 server error. A console tab inside that environment moves to the organization's production by itself, and says That environment no longer exists.
  • ConsoleIn a development or staging environment, the dialog showing a new client secret now gives the organization ID your app needs. An Environment row sits beside it. Copy all four puts both in your env variables, as NEXT_PUBLIC_BUILDBASE_ORG_ID and NEXT_PUBLIC_BUILDBASE_ENVIRONMENT. Before, the ID it gave was refused by the SDK at start-up.
  • ConsoleIn a development or staging environment, Test OAuth2 flow now uses that environment. So do the Connect your app steps under Settings > Tracking & tags. Before, they pointed at production, which refused them.
  • ConsoleA setup welcome you dismiss, and the plan usage meters, now keep to the organization and environment you are in. Before, a dismissed welcome stayed hidden in every other environment, and a meter could briefly show the previous environment's count.
  • SecurityA read-only support session that BuildBase staff open for a development or staging environment now stays there. Before, the console opened it in production instead.

Use what shipped this week

Everything in this release is already in the console and the SDK.

Free plan7-day free trial on paid plansNo credit card required