New answers tagged deployment
0
The problem was the labelling. I already had a Custom Metadata Type with the same label and namespace prefix. Changing the label of one of the Types resolved the issue.
0
It turns out that the issue was related to platform encryption. If the new fields are Encrypted with Case Insensitive Deterministic encryption, Salesforce stores a lowercase duplicate of the field behind the scenes.
0
I found the issue. In the workspaces option on the All Sites screen. Click on administration there are options to manage the login screen for the sites.
0
In my case, the name of directory in packageDirectories and actual directory on the disk was slighty different, when I fixed the typo, the error has gone
1
The first lwc that is encountered in a directory is considered the containing directory for all LWC components. Since you named it /lwc/internal/lwc/callbackIdRetriever, the system thinks you're trying to declare a component called internal. All of the source in those directories will be collapsed into a single folder for deployment, which means that any &...
1
LWC, in particular, are quite restrictive in their structure. Salesforce DX Project Structure and Source Format
Lightning web components must reside in a directory named lwc under
the directory.
Even with the above restriction, you could define multiple package directories to have different lwc folders, but you can't have subfolders within lwc.
{
&...
0
The problem is that you have both an Aura and LWC component with the same name. This is not allowed. You will want to delete or rename one of those components from the metadata files, presumably the Aura version. This may require some other refactoring of the code.
Top 50 recent answers are included