Duplicate translations for message '9182224963637946835' when merging after update to Angular 13.1

[hheexx]

Which @angular/* package(s) are the source of the bug?

localize

Is this a regression?

Yes

Description

After updating to Angular 13.1 i have ton of warnings in console that look like this:

WARNING [locales/messages.sr.xlf]: Duplicate translations for message '9088279543992873374' when merging

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

No response

Please provide the environment you discovered this bug in (run ng version)

Angular 13.1.1
Node 16.13.1
npm 8.1.2

Anything else?

No response

[alan-agius4]

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?

You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

[hheexx]

Ill try that in few weeks if it's not fixed by then.
Let's wait for now to see if I'm only one with this or there are more people....

Our usage of localization is pretty basic so I assume there will be more people.

[alan-agius4]

Does this happen during serve or build?

[hheexx]

Only serve.
I think I receive warning for every treanslation there is in a file.

[JoniJnm]

I have the same problem after upgrading to v13

The warnings appears after the first rebuild (I mean, the first "build" while serving is ok, but if I modify a file I see this warnings)

I will try to create a new project to reproduce the problem

[hheexx]

I confirm same behavior.
@JoniJnm, have in mind that problem is just in 13.1. 13.0 is ok.

[JoniJnm]

The repository: https://github.com/JoniJnm/bug-22398

Use "npm start", modify a file and see the i18n warnings

[destus90]

We are facing the same issue after upgrading to the newest version. Glad to see we are not the only ones.

[bbarry]

I believe it was caused by #16341

More specifically the reload here: 9300545#diff-50f53ef4e38233adf87a2a3af8e79f59cb5befbeb7d053d52a84b76e04d52b18R367-R378 doesn't re-initialize localeDescription.translation between reloads so every reload, every translation is seen as a duplicate.

If only one translation file is permitted during ng serve then it should be easy to fix this with simply adding localeDescription.translation = {}; before reloading. But if translations can cascade across multiple locales (not sure offhand if something like this is supported by Angular) then it is much more complex.

[hheexx]

@alan-agius4 we have repo. Update label please.

[dydek]

we've got the same issue after upgrading to 13.1

[rlejeune]

Same problem here also, started after upgrading to 13.1

[msalzig]

Same issue after upgrading to 13.1