We ran across this issue, as shown in the attached image.
While I was able to figure out how to have the user get around this issue, we would like to be able to avoid anything similar in the future.
We were not able to replicate this issue, be it in test environments or on the deployed production server. When having the user log into an incognito window to force a new session to be created, she no longer had the issue.
Our hypothesis is for one reason or another there was an error while loading libraries, and the JavaScript on the client side was in some way malformed or incomplete.
If this is true, is it possible to put the instantiation of the client-side application in something like a try catch block so if something was loaded incorrectly, so we can at least notify the user that they should refresh their session to avoid unexpected behavior?
If you have any other thoughts or suggestions on the cause of the issue or how to resolve it, I’m interested to hear what you think.
Greg
