I tried updating Translation Manager to latest version v12.4.0 on Umbraco v12.2.0, we also have the usync complete v12.1.0 installed and got an error after the update (i rolled back to v12.3.3 and it works fine):
System.InvalidOperationException: 'The HttpClient factory already has a registered client with the name 'SubscriptionLicenceChecker', bound to the type 'uSync.Expansions.Core.Licencing.Checkers.SubscriptionLicenceChecker'. Client names are computed based on the type name without considering the namespace ('SubscriptionLicenceChecker'). Use an overload of AddHttpClient that accepts a string and provide a unique name to resolve the conflict.'
Could this be an issue with running this version of Translation Manager with this version of usync?
Sorry i missed this but yes - it turns out we didn't check them against each other (didn't realise it was ignoring namespaces) , there is a fix now for translation manager
Umbraco Translation Manager v12.4.0 update error
Hi Kevin,
I tried updating Translation Manager to latest version v12.4.0 on Umbraco v12.2.0, we also have the usync complete v12.1.0 installed and got an error after the update (i rolled back to v12.3.3 and it works fine):
System.InvalidOperationException: 'The HttpClient factory already has a registered client with the name 'SubscriptionLicenceChecker', bound to the type 'uSync.Expansions.Core.Licencing.Checkers.SubscriptionLicenceChecker'. Client names are computed based on the type name without considering the namespace ('SubscriptionLicenceChecker'). Use an overload of AddHttpClient that accepts a string and provide a unique name to resolve the conflict.'
Could this be an issue with running this version of Translation Manager with this version of usync?
Thanks,
Mike
Hi Mike,
Sorry i missed this but yes - it turns out we didn't check them against each other (didn't realise it was ignoring namespaces) , there is a fix now for translation manager
https://www.nuget.org/packages/Jumoo.TranslationManager/12.4.2
Nice one Kevin good work, thanks!
is working on a reply...