Why is DeepL Translation Provider plug-in suddenly not accepting my correct API key after the recent update?

Question

Hello. 
 I recently updated the DeepL Translation Provider plug-in and now it no longer accepts my API key, even though it is valid (I've checked several times!) - can anyone shed some light? 
 
 Many thanks 
 Susan

Andrea-Melinda Ghisa · Answer

Hi Marcel Allera 
 We found the problem and we'll release a new version in a couple of hours. Sorry for the inconvenience. 
 Have a nice day, 
 Andrea Ghisa.

Andrea-Melinda Ghisa · Answer

In maximum 10 minutes is should be available in the AppStore Integration plugin. Or if you are in a hurry you can download from the Appstore web page there is available at this moment.

Andrea-Melinda Ghisa · Answer

We just released the new version on AppStore. Can you please update the plugin to see if the problem persists?

Andrea-Melinda Ghisa · Answer

Hi Susan McDonald , 
 Thank you for providing the log file. 
 It seems the errors logged there are old and it has nothing to do with the Authorization message which you are seeing. I assume somehow in Studio are save some incorrect credentials because that message which appears we are receiving it from DeepL when we are trying to validate the key. 
 Can you please go to the following path and delete the TranslationProviderCredentialStore files? 
 
 C:\Users\[your user]\AppData\Roaming\SDL\SDL Trados Studio\Studio16 
 Once you delete these files you'll have to add the DeepL key again in the translation provider. 
 Kind regards, 
 Andrea Ghisa

Andrea-Melinda Ghisa · Answer

Hi Rodrigo Mencía , 
 We found the problem and we'll release a new version in a couple of hours. Sorry for the inconvenience. 
 Have a nice day, 
 Andrea Ghisa.

Andrea-Melinda Ghisa · Answer

Hi Donna Elliott 
 We found the problem and we'll release a new version in a couple of hours. Sorry for the inconvenience. 
 Have a nice day, 
 Andrea Ghisa.

RWS AppStore > 2. RWS AppStore Applications

Why is DeepL Translation Provider plug-in suddenly not accepting my correct API key after the recent update?

Top Replies