In this version, we have:
- exchanged the
fetchmechanism to a new library to ensure cross browser compatibility - Introduced explicit usage of
UTF-8to ensure compatibility with all kinds of characters allowed in RTC (e.g. Japanese language)
For that reason, you must also upgrade the service to Version 1.5.3.
Thank you to @rsjazz for pointing me to the question on Jazz.net, to Ian who reported the issue there and a special thanks to @SBI- for adding encoding support to the core, so that I had to perform only minimal changes. You guys rock!