logEntryMetadataViewer only displays spinner

[Rumtum]

Package Edition of Nebula Logger

Managed Package

Package Version of Nebula Logger

4.17

New Bug Summary

After the installation of 4.17, from 4.16, log entries no longer display code in the origin or source components. Rather, we just see the spinner.

The access to the apex controller class hasn't changed and appears to be correct.

[jongpie]

@Rumtum are you able to tell if there's any kind of exception being thrown? You could check in either the Apex developer console, or check your browser's console to see if there are any errors.

[Rumtum]

This is the only indicator we can see. Safari and Chrome behave the same way. Nothing obvious in the Apex developer console.

[khouseknecht]

We are experiencing this same error with the same version. Uncaught promise in the loggerCodeViewer and we see the spinning indicator. Any thoughts on how to resolve?

[cbcruz74]

Same here with 4.17.3

[jongpie]

Hey everyone, thanks for the additional feedback / confirmation that this is impacting multiple people. I still have not been able to reproduce the issue myself, so I'll need some help determining exactly what's going on here.

For anyone that's impacted by this issue & has some time to check a few more things:

1. Can you try enabling Lightning Debug Mode for your users to see if it's possibly a caching issue? You can enable this under Setup → Lightning Components → Debug Mode → enable it for yourself.
   • Once you've done this, try reloading a page to see if the LWC still has issues
2. Can you confirm that you see the static resource LoggerResource in your org? It should be under Setup → Custom Code → Static Resources, with the name LoggerResource and namespace Nebula
3. Can you check your browser's "Network" tab to see if the static resource is being properly loaded? In Chrome, you'll want to open the browser console first, then open a LogEntry__c record page. Then in the browser console, go to Network and search for prism - you should see 2 results for prism.css and prism.js, like in the screenshot below:

[jongpie]

And @cbcruz74 just to confirm, you're using the unlocked package, right? If so, it sounds like this is impacting both the managed & unlocked package.

[khouseknecht]

1. Enabled Lightning debug mode - empty cache and hard reload - still see the issue.
2. Confirmed Static Resource exists in org
3. Confirmed in Network that resources are downloading

I also confirmed that this works in the current unlocked package. I observe the issue only in the managed package.

[cbcruz74]

Hi @jongpie . Yes, we are using the unlocked package. In Chrome, i'm getting this:

[joshiausdemwald]

Hi @jongpie, I can confirm that the issue also exists in our environment -- it appears to happen when using the Unlocked Package, too. prims.js/.css are loaded as expected though.

[joshiausdemwald]

I suppose I've found a solution @jongpie :

For me the issue disappeared after I enabled Lightning Web Security in Setup -> Session Settings. It seems that the lib used to display and format the source code is not working together with Locker Service which was in my understanding superseded by Lightning Web Security.

[cbcruz74]

I could not replicate that behavior in a sandbox with 4.17 and SLDS 2.0. The component did not render after enabling Lightning Web Security.

[khouseknecht]

Can confirm that enabling Lightning Web Security fixes the issue in the managed package.