function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
fiona gentryfiona gentry 

Why LWC component not showing in App Builder when exposed = True and Target tags defined

Hi Folks,
Have a LWC component which is pushed successffully to scratch org using
sfdx force:source:deploy --sourcepath force-app\main\default\lwc\eRTCaseTypeLevelInfo

PS C:\sf\LWCSpecialist> sfdx force:source:deploy --sourcepath force-app\main\default\lwc\eRTCaseTypeLevelInfo
 »   Warning: sfdx-cli update available from 7.121.8 to 7.123.1.
Deploy ID: 0Af7c00000tcgy9BBV
SOURCE PROGRESS | ████████████████████████████████████████ | 1/1 Components

=== Deployed Source
FULL NAME             TYPE                      PROJECT PATH
────────────────────  ────────────────────────  ────────────────────────────────────────────────────────────────────────────────
eRTCaseTypeLevelInfo  LightningComponentBundle  force-app\main\default\lwc\eRTCaseTypeLevelInfo\eRTCaseTypeLevelInfo.html
eRTCaseTypeLevelInfo  LightningComponentBundle  force-app\main\default\lwc\eRTCaseTypeLevelInfo\eRTCaseTypeLevelInfo.js
eRTCaseTypeLevelInfo  LightningComponentBundle  force-app\main\default\lwc\eRTCaseTypeLevelInfo\eRTCaseTypeLevelInfo.js-meta.xml


Though i see the LWC app in Org but unable to find the LWC in Custom component section of Lightning App Builder Page or HomePage

Please note 
not showing in App Builder when exposed = True and Target tags defined as below
<?xml version="1.0" encoding="UTF-8"?>
<LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata">
  <apiVersion>52.0</apiVersion>
  <isExposed>true</isExposed>
  <masterLabel> CaseType Levels Info Component</masterLabel>
  <description>ERT CaseType Levels Info Component.</description>
  <targets>
      <target>lightning__RecordPage</target>
      <target>lightning__AppPage</target>
      <target>lightning__HomePage</target>
  </targets>
</LightningComponentBundle>

Your help is highly appreciated

Regards,
Fiona
 
Rina Nachbas 4Rina Nachbas 4
I had the same issue, removing the masterLabel element tag from the meta xml file resolved the issue