It turns out when you register HTTPClients for services the Namespace of the service is not taken into account so we had a SubscriptionLicenceChecker class in both uSync and Translation manager (in diffrent namespaces) - and this causes an error on startup.
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.'
It turns out when you register HTTPClients for services the Namespace of the service is not taken into account so we had a SubscriptionLicenceChecker class in both uSync and Translation manager (in diffrent namespaces) - and this causes an error on startup.
As reported : https://our.umbraco.com/forum/using-umbraco-and-getting-started/112775-umbraco-translation-manager-v1240-update-error