Here you Adobe IMS user profile has been stored in the browser session, which enables you to make request to the get-profiles action using your user token. When opened, the UI is almost similar to that when you access it on localhost, except the ExC Shell on top. You might be asked to log in using your Adobe ID. Previously, you can see from the Terminal output that it is also possible to access the app from ExC Shell. Because there is no user token embedded in the request header, you will see a 401 Unauthorized error in the browser console. Select it from the dropdown list, and press the Invoke button. Let's try invoking the get-profiles action. Navigating to Your App Actions, there is a form that allows you to try invoking the existing actions in the app. You should be able to see the UI of the app. That's fine for this app, hence you can accept and continue to the page.

When the app is up and running, it can be seen at Please note that, as you are visiting the localhost site via HTTPS, the browser may give a warning for the lack of certificate.

This command will deploy the get-profiles action onto I/O Runtime, and spins up a local instance for the UI.

Adobe app builder