LightningMessageChannel not supported
See original GitHub issueHey, I am just experiencing some errors in VSCode with ForceCode. I installed everything but always receive the following error when I want to retrieve classes:
"NamespacePrefix, Description FROM LightningMessageChannel WHERE NamespacePrefix ^ ERROR at Row:1:Column:61 sObject type 'LightningMessageChannel' 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."
Any ideas?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:9
Top Results From Across the Web
lightning web components - MessageChannel not working
I have a very simple code which is not working: ... <isExposed>true</isExposed> <description>This is a sample Lightning Message Channel.
Read more >LightningMessageChannel | Metadata API Developer Guide
A Lightning Message Channel represents a secure channel to communicate across UI technologies (Lightning Web Components, ... Unsupported Metadata Types.
Read more >salesforce - The LightningMessageChannel named ...
The Lightning Message Channel should be in the camel case is the best ... LightningMessageChannel named boatMessageChannel was not found in ...
Read more >Get error when lightning message channel is enabled in ...
... lightning Message Channel for genesys in salesforce, an error is popping up everytime we go on queue Error in $A.getCallback() [d is...
Read more >How to create a MessageChannel in Salesforce using VS ...
<description>This is a sample Lightning Message Channel.</description> <lightningMessageFields> ... i m trying same but it not working.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
For everyone facing this issue, change your api version to 46.0 in the org settings (Forcecode Menu => Org Settings). This is a per-org setting. I will release a fix soon.
Fixed in 3.19.2. If you are using LightningMessageChannel in a dev org, please read the changelog for instructions to re-enable opening LMCs