Invalid entry in relation to failed string translations

I’ve reported this before, it seemed to stop after a change was made, but the errors have come back:

Failed to translate string with key: InGame.ConnectionError.DisconnectClientRequest

Previous report Invalid entry in relation to failed string translations

2 Likes

Thanks for reporting, team is looking into it

3 Likes

Hi, thanks again for the report!

I’d first like to clarify that Failed to translate string with key: InGame.ConnectionError.DisconnectClientRequest is unrelated to the Invalid entry error you mentioned in the previous thread.

Are you still encountering the Invalid entry error? We believe we’ve made changes that should fix this long-term for new localization table entries, but please provide additional details if you’re still seeing this.

1 Like

Yes, I’m not getting the Invalid entry.

But the previous thread did also report the Failed to translate string with key: InGame.ConnectionError.DisconnectClientRequest, which disappeared after the last fix, but has returned (and confirm still appears in the last day).

1 Like

I am getting spammed with this

How do i disable the warning it’s very annoying!

Hey @pjhinthehouse - this issue should be fixed now. Please let us know if you’re still seeing these messages.

Hey @RuizuKun_Dev - this seems like a separate issue from what was reported in the initial post. If you’re still encountering this problem, please file a separate bug report so we can track appropriately. Thank you!

I 100% thought it is related because of the failed translation error

How do I fix the failed translation string

1 Like