Kinetic custom app "view could not be loaded" in client/MS Edge, but not Chrome

While investigating why one of my converted custom dashboards is not returning any data in the application (browser login) when it does in the BAQ designer, I came across a bewildering error.

I decided to open the particular dashboard I was troubleshooting in the client, I got an error stating “The view could not be loaded.” I wasn’t getting that error in Chrome. Was trying to debug with developer tools in Chrome comparing this dashboard to another that works correctly, but wasn’t seeing anything helpful. So I decided to use Edge and follow instructions I’ve found here on how to use browser developer tools to debug. I first opened my good dashboard, but it also gave me the same error in the Edge browser, but it did not in the Chrome browser. So I tried my troubled dashboard in Edge and also got the same error.

Thought maybe Chrome working was a cache issue, but after clearing that and logging back in the dashboard still works in Chrome. What gives??

image

2 Likes

I would say my only observation so far would be the method of creation.

I managed to reproduce the error by:
Using the wizard in Application Studio to generate the UI, then by modifying the base layer afterward.

if you then add a customer layer on top of the base layer and add to the menu item the error seems to disappear.

Anything generated by the manual method in Application Studio seems to be okay.

Just an observation…

Version: 2024.1.9

2 Likes

Appreciate the response. I’ll give this some attention to see if that clears it up for me. I did discover that on one of my app servers they open/function fine, it’s the other one that this happens on. So in my case, it might simply be a permissions issue that’s different between the two app servers.

These two particular app servers are our non-production servers, so crossing my fingers that our production servers both behave the same way and the dashboards work, so I don’t have to put much time now into solving the issue for the non-prod server that isn’t working.

Which versions are in play here? I had this issue today - 2023.2.10 worked fine, 2023.2.20 produced that error, 2023.2.26 works fine also. Something broken in 2023.2.20 from today’s experience for me!

2023.2.20 error repeatable across different environments, on different servers.

1 Like

2024.1.5 for me on my non-production and 2024.1.9 for my production (where I haven’t tested it out, yet).