Experience page not loading depending on default device context

Bug Report
, ,
1

There’s a bug that’s causing experience pages (a dashboard page) to not load correctly. I click on the link in the experience, this triggers an endpoint in a workflow. That workflow does a device get request, goes through a function to generate a particular url based on the type of device, then goes to an Endpoint reply node. This all triggers as it should. The url the experience user ends up at is correct and includes the device id of the device they should be seeing a dashboard for. The page should be there, but it’s not.

I’ve seen this bug twice now, and the fix seems to be to change the default device context in the affected dashboard (in dashboard settings). I don’t really understand why this works. The device context that is actually being used depends on which device the user is viewing when they click on the link, and it’s not necessarily going to be the same as the device that’s set as the default. Also, the default device that it was set to before (when it was failing to load) should be perfectly valid.

The first time this happened, trying to change the device context in the development environment (not the default, in the dashboard settings, just at the top left of the dashboard) was bringing up an error saying that the device wasn’t valid. Once the default was changed, it seemed to recognise the previously invalid device.

This might all have something to do with the way we’ve set up our experience workflows, or maybe it’s a genuine bug.

2

Without seeing actual error messages, screenshots, or application configuration, my first guess is that the device context variable that you are setting a value for has some sort of validation applied to it in the dashboard context configuration, and the device the user is trying to access does not pass that validation. Setting the default value also opts that value in to pass the validation.

If that’s not it, can you please provide some additional information? “The page should be there, but it’s not” can mean a lot of things. Are you getting a white screen? A layout with an empty area where the dashboard should be? Any kind of errors in your browser console or your experience view render log for the page?

3

Thanks Dylan. I’ll check whether I’ve set some kind of validation somewhere.

From memory, I believe it was loading the page layout elements but just had a blank, white area where the dashboard should have been.

If the problem comes up again, I’ll make some more detailed notes, take screenshots, and add them to this thread. Since the page in question is working now, I’m reluctant to deliberately break it again for testing purposes.