Open PraviBorko opened 2 years ago
Anything new regarding this issue?
Looking into it. Sorry for the delay. This is an old Android WebView issue.
Hi, I am experiencing the same issue with screen sets on core-v6.1.0 version. Is there any update?
Hi any updates on this issue?
Unable to find a viable solution for this yet. Coming back to it soon.
Can you advise on a workaround for this issue? Is there a list of characters that we should avoid using with gigya?
I currently have no workaround for it. The Android WebView component has had this issue for some time now even if we are specifying the default text encoding. Currently, the screensets webview is not accessible so there is no way to change the default settings encoding.
Are you using a specific lang for the screen set?
We are using spanish language on our screensets
But this issue is reproducible only on recent versions of SDK. On older versions (3.3.28 for example) special characters are shown correctly
3.3.28 is ancient, not old. I am currently running on latest SDK with my test env on "es" lang
Some special characters are not displayed correctly on screen sets.
For example:
Expected string: "Nächster Schritt 2/3"
We are using core sdk version 6.0.0. The same screenset is displayed correctly on iOS.