Library compilation failed

[jsilvestre]

We recently upgraded to version 2020.10.11 and I’m trying to publish a library into orchestrator. I’m able to publish historical libraries but received the below error when creating a new library.

Unable to create activity builder for document. Reason was ‘Cannot create unknown type ‘{http://schemas.microsoft.com/winfx/2006/xaml/presentation}Point’.’.

Anyone come across this issue and how did you resolve it

[system]

Hello @jsilvestre!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

1. Always search first. It is the best way to quickly find your answer. Check out the icon for that.
   Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

2. Topic that contains most common solutions with example project files can be found here.

3. Read our official documentation where you can find a lot of information and instructions about each of our products:

4. Watch the videos on our official YouTube channel for more visual tutorials.

5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly
Forum_Staff

[Pablito (Pawel Wozniak)]

Hi!
What version of the Orchestrator do you have? Have you tried a manual import of the same library?

[jsilvestre]

Have version 2020.10. I opened a service ticket with UiPath. The workaeound was to edit the xaml file and remove/comment out the references to the pointer. In my case “point”. It’s aesthetic according to the help desk. This solved my issue and apparently is resolved in the latest version of UiPath.