Skip to main content





Experience Builder blockers and warnings

Experience Builder validates your app before publishing it to the environment.

If the validation fails, Experience Builder lists the issues it found in your app or environment. Issues belong to one of the following types:

  • Blockers are issues that you need to solve before publishing the app.

  • Warnings are issues that may affect the experience of your app, but you don't need to solve them to publish the app.

An issue may include a Fix it now link that helps you solve you the issue. Selecting this link takes you to the location in Experience Builder where you can fix it.

Blockers reference

A blocker is an issue with your environment or with your app that blocks the publishing of the app.

Experience Builder lists blockers in the publish dialog after Before publishing the app, please review the following:.

We can't publish your application, because the dependency "<dependency-name>" has version <outdated-version> and the required version is <current-version>

Your environment doesn't have the correct version of a dependency of the app.

Update the dependency.

We can’t publish your app. There’s a missing required dependency in your environment: "<dependency-name>"

Your environment doesn't have a required dependency installed.

Install the dependency.

You haven’t added any screens.

Your app must have screens, otherwise you can't test it.

Add flows to your app.

Not enough flows. Add flows to your app.

Ensure that your app has at least two flows.

Missing menu items. Add menu items to your app.

In the Menu canvas, add a menu icon and connect it to a flow.

In the Menu canvas, link at least one menu item to a flow.

Missing flows. Add a Login or Onboarding flow.

Your app needs a default screen to act as the entry point. Experience Builder uses either a login or onboarding flow as the default screen of your app.

In the Flow canvas, select Add flow, search for Loginor Onboarding, and add a login or onboarding flow to the app.

Too many login flows. Add only 1 login flow per app.

Your app can only have one login flow.

In the Flow canvas, delete the login flows until your app only has one login flow.

Warnings reference

A warning lets you know about issues that can compromise the experience of testing the app.

Experience Builder lists warnings in the publish dialog after It looks like your app isn't ready to be published... You might want to:.

There’s a missing dependency in your environment: "<dependency-name>"

Your environment doesn't have an optional dependency installed.

Install the missing dependency in one of the following ways:

Unlinked menu items. Connect menu items to destination flows.

When using the app, selecting the unlinked menu entries won't take you anywhere in the app.

Connect menu items to flows.

Can't access the "<flow-name>" flow.

When using the app, you won't be able to access the screens in the <flow-name> flow since no flow or menu item connect to the <flow-name> flow.

Connect the end point of another flow or a menu item to <flow-name> flow.

That doesn't look right. Your login flows isn't connected to another flow. Connect the flow so user can log in and use your app.

You must connect the exit point of the login flow to another flow, otherwise end users can't test the rest of the app.

Adding flows would improve navigation.

You only added onboarding and login flows to your app and you won't be able to test your app.

Add flows of other types, and make sure the login or oboarding flows connect to the flows you added.

You've added flows that required registered users. Add a login flow.

Some flows in the app are only accessible to registered uses, which means the app must be able to authenticate users using a login flow.

You've added a passcode login flow. Add a signup flow.

Passcode information isn't available by default in end-users created using Users. All the singup flows in Experience Builder let the end-user set a passcode.

  • Was this article helpful?