SFDX Package lost resolution of metadata type.

[Justin Julicher]

Have invalidated cache and restarted and also regenerated (full) the OST.

It doesn’t seem to be downloading the Custom Metadata type into the OST anymore.

[Justin Julicher]

Also, it seems to be anything package related.

I have a normal project and it’s having trouble resolving the hierarchy of Interfaces.

My package goes like this:

AnyFieldHasChangedFilter → cu.Filter → cu.Function

and I get the following:

where the above should not need any casting.

[Scott Wells]

These screenshots leave me with quite a few questions. First, the original screenshot looks...odd. The icons aren't what IC uses, and the scoping of meta.xml files beneath the .cls isn't something IC does. Are you using some other plugin to create a custom Project view or something?

Regarding the core issue, are the problematic types showing up in the generated OST? If so, can you create a simple standalone inheritance hierarchy that reproduces the issue?

[Justin Julicher]

I’m using the Material Theme plugin - which uses different Icons/style.

This one is still persisting after I resolved the issue in the other issue #1376

It doesn’t seem to be generating any symbols for the OST for Custom Metadata in a sfdx project. I can replicate this in a clean sfdx project.

‌

In regard to my first comment - I think it is because I had multiple projects open in the same window. Once I separated out the projects and regenerated the issue went away.

‌

So my project had the following open:

• Normal project
• sfdx module
• sfdx module

The Expected argument issue came about when I had that setup. I’m now running all 3 in separate windows and everything is resolving correctly again.

thanks

[Scott Wells]

Is there anything left to address here, at least distinct to this issue? There's another one already filed (I'd have to search for it) to support the new multi-project window stuff in 2019.2, but that will take a while because of some bugs I've already found in the base IDE in that feature.

[Justin Julicher]

To fix in another issue.

[Justin Julicher]

Sorry my bad. Issue still to fix:

SFDX project doesn't resolve custom metadata types.

[Scott Wells]

So even after a full OST regeneration you're still not seeing entries for the custom metadata types in the OST? If that's the case I'll need you to enable debug logging for OST generation (don't include the trace entry), regenerate the OST (SObjects portion should be sufficient), and email me all log files from that period of time for review.

[Justin Julicher]

Here ya go:

‌

2019-08-08 13:07:42,838 [ 141496] INFO - ct.OfflineSymbolTableGenerator - Starting activity Initializing local symbols with 1 steps.
2019-08-08 13:07:42,866 [ 141524] WARN - loud.symtab.OfflineSymbolTable - Failed to load custom object information for /home/justin/WebstormProjects/cortex-utils/force-app/main/default/objects/Dependency__mdt/Dependency__mdt.object-meta.xml.
javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,6]
Message: The processing instruction target matching "[xX][mM][lL]" is not allowed.
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:652)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XMLStreamReaderImpl.java:1346)
at com.illuminatedcloud.intellij.util.IlluminatedCloudXmlUtil.readXmlDocument(SourceFile:57)
at com.illuminatedcloud.intellij.util.IlluminatedCloudXmlUtil.readXmlDocument(SourceFile:84)
at com.illuminatedcloud.symtab.OfflineSymbolTable.getCustomObject(SourceFile:483)
at com.illuminatedcloud.symtab.OfflineSymbolTable.getObjectTypeNames(SourceFile:287)
at com.illuminatedcloud.symtab.OfflineSymbolTable.access$000(SourceFile:148)
at com.illuminatedcloud.symtab.OfflineSymbolTable$1$1.visitFile(SourceFile:438)
at com.intellij.openapi.vfs.VirtualFileVisitor.visitFileEx(VirtualFileVisitor.java:124)

‌

I checked all the XMl - it is all well-formed.

‌

thanks

[Scott Wells]

That's very helpful, Justin. Thanks! I'll take a look today and see if I can figure out what's going on, hopefully for a fix in the next build (currently shooting for tomorrow morning).

[Scott Wells]

Justin, do you mind emailing me objects/Dependency__mdt/Dependency__mdt.object-meta.xml so I can see what it looks like? There's something in there that's not parsing as XML properly which is what's causing the issue.

[Justin Julicher]

Hi Scott

I'll send it when I get to work but I've double checked the xml and it's well formed. I also have the same problem in my other sfdx package with a different type. It started happening when I moved to 2019.2.

[Justin Julicher]

Hi @scott wells

Here’s another message from the logs:

2019-08-09 10:00:57,009 [ 399242] WARN - loud.symtab.OfflineSymbolTable - Failed to load metadata for DEPENDENCY__MDT: org.apache.cxf.binding.soap.SoapFault: INVALID_TYPE: sObject type 'DEPENDENCY__MDT' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names.

[Justin Julicher]

Dependency files.

[Justin Julicher]

Remove the ‘1’ in the Dependency__mdt.object-meta.xml file - that’s a red herring accidentally added that in when I was zipping it up.

[Justin Julicher]

Ok figured it out.

It wasn’t the Dependency__mdt.object-meta.xml file.

It was one of the field files - it had an empty line as the first line which caused the issue.

Sorry about that.

thanks.

[Scott Wells]

I'll go ahead and resolve this as I've already added better error reporting when a file can't be parsed. Minimally you'll be told the file(s) that were skipped and why you won't have the resulting entries in the OST.