Hi Kamil Chlodek , sorry to hear you are running in to these problems.

Correct, it will not load the unsigned plugin.

One important change since Trados Studio 2021 is the requirement to sign the plugin before it can be executed in an automation environment.
Note: This process of signing plugins will be automated in the next months, but for now you should upload yr plugin to a location where it can be downloaded (e.g. dropbox, onedrive et.c..) and send a request to sign it here: app-signing@rws.com

How I'm suppose to test all those things together? This is how development gonna looks like: 

1. Send sign request. Wait 3 days (I'm already waiting 3 days for this).
2. Do the test. Find out there is null reference exception somewhere or something else. Fix this.
3. Go to point 1.

This is ridiculus. Fixing 3 simple bugs in code could take 9 days or even more. In case of critical error that need to be fixed immediately we are screwed. 

How I'm suppose to test all those things together? This is how development gonna looks like: 

1. Send sign request. Wait 3 days (I'm already waiting 3 days for this).
2. Do the test. Find out there is null reference exception somewhere or something else. Fix this.
3. Go to point 1.

This is ridiculus. Fixing 3 simple bugs in code could take 9 days or even more. In case of critical error that need to be fixed immediately we are screwed. 

Kamil Chlodek 

I just looked to see where your request was and can see why it's taken so long.  We get quite a lot of requests, often requests that are nonsensical, so when someone sends us our own plugin and offers no explanation at all for why they want an already signed plugin signed then the team will put it to the back the queue to address when they have more time.

Now that I see this thread and can link these things together (I don't normally sign plugins myself) I can make sure they get signed and sent back.

Going forward we have rebuilt the appstore front and back ends and added a lot of functionality, including the automated signing of plugins for developers.  So once this goes live... which isn't too far away, you won't have your ridiculous situation.

In the meantime help yourself a little and don't just send in plugins, especially ones that we actually developed, with no explanation.

Hi Paul 

The plugins are not meant to be published in app store. That's why there is not explanation what they are and what they do. I thought it's unnecessary. I'm quite sure I did not send signed plugin. Yep, there is DeepL MT plugin, but this is just modified version based on source code from sdl-community github repo). Ok, I got it. That might confuse.

I would not waste your and my time If I could found info about how to.

 06 Submitting apps for signing and/or publication - tba
https://gateway.sdl.com/apex/communityknowledge?articleName=000001600 - nothing about procedure of signing app.

Good thing I'll be able to sign the plugin myself. I hope it will cut development time from days to minutes :) But I don't understand why it happen in first place. Why it has been blocked. In Trados Studio I have option to allow load unsigned plugin at least. Under automation API no. Now, 18 months since Trados Studio 2022 release there will be an option to sign plugins myself. Am I the only one who thinks something is wrong here?

Regards

Kamil Chlodek 

Kamil Chlodek said:

But I don't understand why it happen in first place. Why it has been blocked.

I really doubt it's been blocked.  That would mean we did it on purpose and I really doubt this was ever the case.  I think this is just the result of the core product team not being fully aware of what developers using the APIs and using Studio plugins in their automation needed, and as a result the scenario was never tested.  I think it's easy to blame developers without any concept of how many priorities they have and what their strategic goals are, so things can be missed.  But making things harder for 3rd party developers is definitely not anything we want... quite the opposite in fact!

Yep, that makes sens. I don't blame developers. I'm one of them. I (think I) know how things works, especially in such a large project, where knowledge is spread over many people. The thing is can we fix it? Can you report it as an issue and hopefully this will be fixed in future? 

Thanks for your time.

Kamil Chlodek 

Kamil Chlodek said:

Can you report it as an issue and hopefully this will be fixed in future? 

It's already reported. Mentioned somewhere else in these forums by Patrick Andrew Hartnett