You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is occurring for some of our users since I updated the Firebase packages some weeks ago. Unfortunately I can not reproduce it at will. What I see is that special characters like German umlauts (ä, ö, ü, ß) sometimes do not end up in the database properly but get turned into ��. For most users everything is fine, but for some it fails. Some users contact our support, other just leave our site disappointed. The issue seems to not depend on any particular browser or operating system.
I added some code to explicitly test and detect the issue:
If the issue strikes, I end up with this in the database:
specialCharacterTest: "abc-�öüß�-��-��-��-��-abc"
It is notable that several umlauts in a row cause the � to appear only at the beginning and the end and only the first umlaut is not displayed.
I know that an issue without steps to reproduce is very hard to solve, but I'd still like to bring this to your attention. Maybe someone has an idea why this happens.
The text was updated successfully, but these errors were encountered:
I finally found the root cause: It is not Firebase's fault, but UglifyJS' which reverses code order. It only affects the code of the long polling fallback, which is why it only happened sometimes. Here is the bug for reference: mishoo/UglifyJS#3278
Describe the problem
The issue is occurring for some of our users since I updated the Firebase packages some weeks ago. Unfortunately I can not reproduce it at will. What I see is that special characters like German umlauts (ä, ö, ü, ß) sometimes do not end up in the database properly but get turned into ��. For most users everything is fine, but for some it fails. Some users contact our support, other just leave our site disappointed. The issue seems to not depend on any particular browser or operating system.
I added some code to explicitly test and detect the issue:
If the issue strikes, I end up with this in the database:
It is notable that several umlauts in a row cause the � to appear only at the beginning and the end and only the first umlaut is not displayed.
I know that an issue without steps to reproduce is very hard to solve, but I'd still like to bring this to your attention. Maybe someone has an idea why this happens.
The text was updated successfully, but these errors were encountered: