The problem is that I have no access and insight anymore in order to know which activities were in the erroneous xaml-files / workflows. It is difficult to re-work the logic steps totally new…
Does anyone have an idea what can I do so that these errors are solved and the activities are available/visible again?
Is there a backup of your old project? On Git/Bit Bucket or on orchestrator?
If you had published project to orchestrator before, you would be able to extract its older version from there.
And then you should be able to do a cross check on which were those activities that went missing. That way you should be create that activity in your current project and resolve the error.
As per errors looks like either the xamls have corrupted data or references are missing.there can be many causes takign a close look at xaml can help…if you cannot share open the xaml in notepad and check the positions mentioned in errors for any special invalid characters or so
It looks like your xaml files are corrupted If you have any backup file, try to use them, or if both machines are different, try to install the package & version that were used when developing this
And yes, there is a backup of my old project in Git (Bitbucket). I already opened an older project version but there are the same errors… Errors / unresolved activities are also present in project versions with older dependency versions…
I cannot share the project but I already had a look into notepad and the error is, for example, in the place of the “Guid” as the error message mentions, see here:
Also in any backup file there occur errors… What do you mean with “if both machines are different”?
I also set back the package versions back to the versions that were used when developing this, but the errors are still there.
And by the way, in the beginning of December, the used package versions worked. And without doing any changes, now by opening the project there are a lot of errors… I’m at a loss…
Hi,
I found the solution: I updated UiPath Studio Enterprise Edition to a newer version (from 2023.4.4 to 2024.10.7) and by opening the xamls no errors occur anymore.