Now Experience UI properties are not resolved for viewport sub-pages - Known Error

Now Experience UI properties are not resolved for viewport sub-pages Description If you create a page for a workspace in UIB that has a viewport whose contents contain a binding to some app (experience) properties, should you navigate to that page directly from the workspaces tab in the navigation bar, that binding will not resolve correctly unless you refresh the page. If you open the page in question in a new tab, or it is not the initial page you navigate to from the workspaces tab, the context.app bindings resolve correctly.

Steps to Reproduce

Create any UIB page. Add a viewport sub-page. Open the main UIB page. Notice the context.app is working fine. Open the sub-page context.app. This does not work until the page is reloaded. Workaround Configure your page as follows:

1. Create a page in UIB, then add a viewport subpage (i.e. contextual sidebar).

2. In the main (parent) page, create a state variable and bind it to the context.app.* value in question.

3. In the viewport (sub-page), create a new property (click on the Body in the component pane, then in the config panel on the right at the top, select edit next to Properties). Add a new property.

4. Bind that new property you just created in the sub-page to the state variable you created in your parent page.

5. In your viewport (sub-page), wherever you would have bound to context.app.*, bind instead to that new property you have created in the viewport (sub-page) and the binding will resolve as intended. If you keep the binding in the viewport sub-page as context.app.*, the only resolution after navigating to the page from the workspaces menu is to refresh the page in question.