Salesforce ".trigger" extension is not registered correctly

[Yahia]

I just installed the Illuminated Cloud plugin and I get this warning every time I started my IDE. Does anyone know how to solve this problem ?

I tried to follow the instructions below but when I restart my IDE, the message is still there.

‌

[Scott Wells]

Hi. That’s very strange and looks like a false positive given that expected and actual are both Apex. Can you please open Settings / Preferences > Editor > File Types, click on the Apex class file entry, and see if *.trigger is listed under File name patterns? If it’s not, please add it. If it is (grasping at straws a bit here since I’ve never seen this behavior before), please remove it, click OK, reopen that dialog, and add it explicitly.

If that doesn’t resolve the issue--and I’m not 100% certain it will because based on the dialog message I wouldn’t expect it to be happening at all--can you please provide your idea.log from right after this happens using File > Show Log in Explorer?

[Scott Wells]

One other question: Do you happen to have any other plugins installed that might be contending for these file types, e.g., JetForcer? If so, only one can be enabled at a time as they attempt to provide the same functionality and will conflict.

[Yahia]

Hi, I attached my idea.log file right after it happened, and to answer your previous question, I don't have another extension like Jetforcer.
Also, when it happens and I don't add the ".trigger" extension in the Apex file type, the .trigger files are not interpreted by the editor.

[Scott Wells]

Hi. Thanks for the log. Yes, I apologize if what I said wasn’t clear. I wasn’t recommending that you remove the file type registration for *.trigger permanently. I wanted to see if the behavior changes if you remove the existing association, commit those config changes, and then add an explicit association for *.trigger with the Apex class file file type. Have you tried that and found that it produces the same behavior?

If that’s the case, the next step will be to ensure that there’s not some kind of conflict with another installed custom plugin. Right now you have the following custom plugins installed:

• Angular Templates (1.1.3)
• Illuminated Cloud 2 (2.2.3.9)
• Material Theme UI Lite (18.1.0)
• .ignore (4.4.2)
• .env files support (2022.2)
• Comments Highlighter (2.4.1)
• GitToolBox (212.9.9)
• Ideolog (203.0.30.0)
• GitHub Copilot (1.1.33.1980)
• Randomness (2.7.5)

None of those look like they should produce conflicts, but just to be 100% sure, please disable (but don’t uninstall) all but the Illuminated Cloud 2 plugin, restart the IDE, and see whether the issue persists. Please let me know either way.

[Yahia]

Yes it reproduces the same behaviour.
I disabled all the installed plugins and I still get the same message on IDE startup.
I attached a second log file iead2.log

[Scott Wells]

Okay, thank you for doing that. I’ll ask two more things at this point:

1. Can you please provide a screenshot of that configuration screen from your machine, effectively your version of this:

   

2. Can you please fully uninstall the Illuminated Cloud 2 plugin, restart the IDE, install it from the plugin repository again, restart, and see if the same thing happens? I expect that it will because, again, this is not something I’ve ever seen before and I imagine I’m not seeing the root cause. Still, what that will do is fully unregister the IC2-specific file types from the IDE and then allow them to re-register upon fresh installation.

If it’s still happening at that point, there are two primary options:

1. Assuming that triggers are working properly in the editor for you in spite of this warning, you can just disable this via the Don’t ask again checkbox in that dialog (though I don’t see it in your screenshot which is quite curious as well):

   

2. I can instrument this area with some additional debug logging, provide you a build here with that additional debug logging, and see if I can figure out why it’s deciding that the found file type isn’t the expected file type even though it appears to be. That would be my preference as it would allow me to diagnose and fix this not just for you but for anyone else who might experience this issue in the future, but I also want to be respectful of your time of course.

Please let me know whether the steps above help, and if not, how you’d like to proceed with this issue. And thanks for all the diagnostic information you’ve provided so far!

[Yahia]

After doing all of your steps, I finally fixed it ! :)

This is how I did it :

• I exported the configuration of my IDE and I did'nt select File type and File type (schemes).
• Then I restored my IDE with the default settings.
• After that I reimported the configuration I had previously exported and it works well now !

Thank you for your reactivity and your help !

[Scott Wells]

Hmmmmm…I’m certainly glad to hear that it’s resolved for you, but that’s really odd. Something must have gotten into a bad state in your IDE’s stored configuration that was put back into a good state by those steps. If you see any other strange behavior like that, please let me know.

[Yahia]

Resolved