I ran into the same issue you did. I believed that I had found the solution to it, but it looks like this is a bug on UiPath’s part that needs to be addressed. Let me start with some steps of how I got this message, how I thought to resolve it, and the error that remains:
- Before publishing a package, I had designated a specific .xaml file as “Main” by right clicking and selecting “Set as main”
I then published the package to orchestrator, created a process, and tried to run it. I was met with the same error as you – “Starting jobs for processes which use multiple entry points packages is not supported (#1697)”
I went back to my project, and disabled the entry point for the “main.xaml” and then published the package again.
When I updated the process and tried to run it, I still received the same error message.
I even published the project under a different project after ensuring that there existed only one entry point and I still received the multiple-entry points error message.
My plan is to submit this as a bug to UiPath