Errors and Workarounds for UiBundle Deployment Flow in Salesforce CLI

Error 1 Invalid Target value 'AppLauncher'

262.8 core app + b2e access feature enabled + outdated sfdx plugins

If customer see the following error:

Invalid Target value 'AppLauncher'. Valid values are: [CustomApplication, Experience]. Note: 'AppLauncher' has been deprecated in favor of 'CustomApplication'.

This means the customer’s org has the b2e access feature enabled, and they are trying to deploy the old metadata shape of UiBundle, the UiBundle could be something customer already has in their vs code, or it could be generated by the old version of skills/templates/reference apps.

To workaround this, customer should follow the following steps:

1. In <project root folder>/force-app/main/default/uiBundles/<UiBundle devname>/<UiBundle devName>.uibundle-meta.xml, update AppLauncher target to be CustomApplication

2. In <project root folder>/force-app/main/default/applications folder, create an xml file for CustomApplication

   1. Sample file name: TestApp.app-meta.xml

<?xml version="1.0" encoding="UTF-8"?>

<CustomApplication xmlns="http://soap.sforce.com/2006/04/metadata">

   <brand>

       <headerColor>#0070D2</headerColor>

       <shouldOverrideOrgTheme>false</shouldOverrideOrgTheme>

   </brand>

   <formFactors>Small</formFactors>

   <formFactors>Large</formFactors>

   <isNavAutoTempTabsDisabled>false</isNavAutoTempTabsDisabled>

   <isNavPersonalizationDisabled>false</isNavPersonalizationDisabled>

   <isNavTabPersistenceDisabled>false</isNavTabPersistenceDisabled>

   <isOmniPinnedViewEnabled>false</isOmniPinnedViewEnabled>

   <label>TestApp</label>

   <navType>Standard</navType>

   <uiBundle>c__propertymanagementapp</uiBundle>

   <uiType>Lightning</uiType>

</CustomApplication>

The uiBundle field should be in the format of <namespace>__<devName of the uiBundle>, for an org without namespace, <namespace> should be c.

Error 2 Invalid Target value 'CustomApplication'

262.8 core app + b2e access feature disabled + latest sfdx plugins

If customer see the following error:

The specified field isn't valid: uiBundle. And Invalid Target value 'CustomApplication'. Valid values are: [AppLauncher, Experience].

This means the customer’s org has been upgraded to 262.8 but the b2e feature is disabled, and they are trying to deploy the latest metadata shape which is only applicable when b2e feature is enabled, most likely generated through the latest version of skill/template/reference apps.

To workaround this, customer should follow the following steps:

1. Update CustomApplication target to AppLauncher

2. In <project root folder>/force-app/main/default/applications folder, delete the xml file that has the <uiBundle> field.

   1. Refer to the xml sample in Error 1.

Error 3 Invalid Version and Invalid Target value 'CustomApplication'

260 core app + latest sfdx plugin (no b2e access feature on 260)

Customer will hit several errors:
1. Invalid version specified:67.0

1. 1. This means the customer’s org is still on 260 (v66), and the project they are trying to deploy is created with v67. 

   2. To workaround this, customer need to update <project root folder>/sfdx-project.json file and set sourceApiVersion as "66.0"

2. Error parsing file: Element {http://soap.sforce.com/2006/04/metadata}uiBundle invalid at this location in type CustomApplication (15:15) and Invalid Target value 'CustomApplication'. Valid values are: [Experience, AppLauncher]

   

   1. To workaround these errors, follow workaround for Error 2