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 subscription filters debug supports only messages containing Latin-1 characters. It does not support all unicode chars. For example, by verifying message for Czech lang we get the error:
Sometimes the error is a little bit different and comes from the hermes-management backend
The text was updated successfully, but these errors were encountered:
The subscription filters debug supports only messages containing Latin-1 characters. It does not support all unicode chars. For example, by verifying message for Czech lang we get the error:
![Screenshot 2024-03-19 at 16 35 29](https://private-user-images.githubusercontent.com/11329819/314127346-e23f4dcc-5ba1-4773-92a7-9b034505d35c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE4NjQwMDEsIm5iZiI6MTcyMTg2MzcwMSwicGF0aCI6Ii8xMTMyOTgxOS8zMTQxMjczNDYtZTIzZjRkY2MtNWJhMS00NzczLTkyYTctOWIwMzQ1MDVkMzVjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI0VDIzMjgyMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTZjZTc0ZGRiZGYxMGZmYzJiY2JiZGUyYmFiNzkwNGZkY2Y2NTAyYWM5NjE0NjE0YjI0ZjgwMmQxZWM3MTQ0NDAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.DxaxvNq2dzlS2Wotmfp3RBQF5VWCbIilIM08EM06uMk)
![Screenshot 2024-03-19 at 16 41 26](https://private-user-images.githubusercontent.com/11329819/314129135-3a3a64ca-5927-4af1-841e-da75f98009f4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE4NjQwMDEsIm5iZiI6MTcyMTg2MzcwMSwicGF0aCI6Ii8xMTMyOTgxOS8zMTQxMjkxMzUtM2EzYTY0Y2EtNTkyNy00YWYxLTg0MWUtZGE3NWY5ODAwOWY0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI0VDIzMjgyMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTAzMDcxOTAyZTVmZmRmZmRjZTU4MjYyMWZlYzc2MDA4Nzc4MmFiYjJjMDI5ODIxMjUzNDFiNTAyMzUwZmNiZmUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.G2J9aeIZ2sHY31fwSiFrK60nxNhuD_jmBHcXc4xrw24)
Sometimes the error is a little bit different and comes from the hermes-management backend
The text was updated successfully, but these errors were encountered: