When saving Apps from App Studio, the following error message can occur:
"Connection to Apps service is lost."
- You've lost internet connection. Apps requires an active internet connection to save changes you make to your app.
- The reason for this error can be the fact that the App service uses WebSocket to save the App definition.
First, ensure that you have an active internet connection. If you are still facing issues then:
apps-socket.uipath.comto have long live connections by making sure you have the
connection: Upgradeparameter in the header. This must be done with the help of your IT team.
- Work with your IT or network team to understand how WebSocket traffic policies are being handled and alter them as needed.
- Allow WebSocket connections by making sure that
apps-socket.uipath.comis not added to your proxy policy. This must be done with the help of your IT team.
There are two known issues when this message can be displayed. Depending on the situation described below, follow the appropriate Possible cause and Solution.
When previewing an app, the following error can occur, even if there are no errors:
"Errors in App"
This issue can occur when an app is imported in the Automation Suite environment from the cloud environment. The following error can occur when previewing or publishing an app, even if there are no errors in the tree view:
"Errors in App"
One or more browser extensions can cause this error to occur.
Apps built in the Apps cloud environment which have entities referenced in them, will not work when imported in the Automation Suite environment.
Try previewing the app in a different browser OR Deactivate all extensions from your current browser.
Remove all entity references and entities before importing the app in the Automation Suite environment.
An error stating a process is not found can occur in runtime, even if the process is available in Orchestrator.
Check the name of the process and make sure that it does not contain an underscore (
Rename the process and remove all underscore (
Setting the control value using the Set Values rule in the Page load event results in not setting the control value properly.
Instead of setting the control value in the Page load event, use the app variable in the Set Values rule and bind the app variables to the control. By doing so, the control value is being set correctly.
When custom list, table, list, and dropdown controls have a thousand or more records to display, the performance may get slower.
Make sure to provide a height in the control size property and not leave it set to Auto. Once the height is specified, performance optimization kicks in, records being loaded progressively as the user scrolls.
When in Apps design time, the default selected value is correctly displayed for the dropdown control, but when switching to runtime it is no longer displayed
For this example we will use
10 as the value. To correctly display the value in runtime, insert the value in the following format:
=10, instead of simply
When adding custom arguments in the process details page, the newly added arguments are not displayed in the resource panel for binding.
Make sure to first refresh the browser and then add the arguments by pressing the sign. If you do not refresh the browser first, the newly added arguments will not be displayed in the resource panel for binding.
In some situations, app preview might not work in the first attempt.
Make sure that any pop-up blockers are disabled in your browser. Once pop-ups are allowed, app preview works as expected.
When previewing or running an app from home page, the app does not load and can result in a blank page.
The start page of the app is not set. Since there is no start page set, the app cannot decide which page to run or preview.
Set the start page explicitly from the tree view.
An app exported from the cloud environment and imported into the Automation Suite one can have some missing bindings.
Make sure that you check the bindings, preview, and test the app before publishing it in the Automation Suite environment.
When you assign an app variable in the Assign file to app variable property in the Get File from Storage bucket rule, the app variable is not saved.
When you open the app designer, you have to add the app variable again. You can publish the app after adding the app variable and the published version will have the app variable. However, in design time, the app variable has to be added again each time you open the app in App Studio.
When using the dark theme for Apps, the user experience can be sub-optimal.
The dark theme is still a work in progress can it can cause user experience issues.
You can use Apps with the light theme for the best user experience.
In some cases, when adding a new process the following error can occur:
"Process not found - click to replace"
You can only reference up to 20 processes in an app. If there are more than 20 processes, an error can occur on all processes.
Make sure that you do not have more than 20 processes in your app. After doing so, re-open the app.
When previewing an app, the displayed start page is not the correct one.
Two pages have the same order, leading to an incorrect start page in runtime.
To display the correct page in runtime, follow these steps:
- Clone the page that needs to be set as the start page.
- Set the newly-cloned page as the start page.
- Delete the original page.
You can now preview your app and the correct start page should be displayed.
Updated about a year ago