Chat messages showing non-ascii characters

ativsoftware · January 18, 2021, 9:05pm

Chat messages received on web sdk (1.8.6) show garbage characters if sent from Mac client (5.4.7).
Also does not display proper characters if chat sent from iOS SDK (5.4.54…)

Messages sent from web sdk show up as “[This is an encrypted message]” on iOS SDK and Mac client.

MaxM · January 20, 2021, 1:39am

Hey @ativsoftware,

Thank you for reaching out to the Zoom Developer Forum. I tried reproducing this issue on my end but didn’t see the same issue. Does this happen only during meetings or webinars or are there other settings to reproduce the issue? Are you also able to provide a meeting ID where this happened?

Thanks,
Max

ativsoftware · January 20, 2021, 2:17pm

It was on a webinar: 83458851102

MaxM · January 20, 2021, 10:41pm

Hey @ativsoftware,

Thank you for providing additional information. I tested this again using our Sample Angular App when in a Webinar and still wasn’t able to see the issue. I tested when sending to and from the following:

Web SDK 1.8.6
MacOS Client 5.4.7 and 5.4.9
iOS Client 5.4.10
Android Client 5.4.7

Are you seeing the same issue when using the Sample Angular app or our Sample Web App? This will help me to narrow down the cause.

Thanks,
Max

ativsoftware · January 21, 2021, 6:20pm

Is there a standalone working implementation where I can just test by entering a meeting ID, key, secret, etc?

MaxM · January 21, 2021, 10:39pm

Hey @ativsoftware,

That is essentially what the Sample Web App is, but it does require some configuration the first time you run it. You can change the API Key and Secret at the following lines:

github.com

zoom/sample-app-web/blob/5bdebf62bb35a495dad6e30877317964a3601f30/Local/js/index.js#L13-L19


const API_KEY = "YOUR_API_KEY";
/**
 * NEVER PUT YOUR ACTUAL API SECRET IN CLIENT SIDE CODE, THIS IS JUST FOR QUICK PROTOTYPING
 * The below generateSignature should be done server side as not to expose your api secret in public
 * You can find an eaxmple in here: https://marketplace.zoom.us/docs/sdk/native-sdks/Web-Client-SDK/tutorial/generate-signature
 */
const API_SECRET = "YOUR_API_SECRET";

Then you would run npm install and npm start in the terminal to get it running. From there, you can serve it locally over HTTPS using ngrok using the command ngrok http 9999. This is the process I use for testing the Web SDK. Testing with the Sample Angular App is similar but does have some differences.

I hope that helps! Let me know if you have any questions.

Thanks,
Max

ativsoftware · February 17, 2021, 8:55pm

I tried again with web sdk 1.9.0 and the latest Mac client and got the same results.

Could it matter how we set things up for the web sdk?
Here’s our code:

<link type="text/css" rel="stylesheet" href="https://source.zoom.us/1.9.0/css/bootstrap.css" />
<link type="text/css" rel="stylesheet" href="https://source.zoom.us/1.9.0/css/react-select.css" />

<script src="https://source.zoom.us/1.9.0/lib/vendor/react.min.js"></script>
<script src="https://source.zoom.us/1.9.0/lib/vendor/react-dom.min.js"></script>
<script src="https://source.zoom.us/1.9.0/lib/vendor/redux.min.js"></script>
<script src="https://source.zoom.us/1.9.0/lib/vendor/redux-thunk.min.js"></script>
<script src="https://source.zoom.us/1.9.0/lib/vendor/jquery.min.js"></script>
<script src="https://source.zoom.us/1.9.0/lib/vendor/lodash.min.js"></script>

<!-- import ZoomMtg -->
<script src="https://source.zoom.us/zoom-meeting-1.9.0.min.js"></script>

<script>
    var initialized = false;
    $(document).ready(function(){
        if (initialized == false) {
            initialized = true;
            let curUrl = "<?php echo $this->return_url; ?>";

            ZoomMtg.setZoomJSLib('https://source.zoom.us/1.9.0/lib', '/av'); 
            ZoomMtg.preLoadWasm();
            ZoomMtg.prepareJssdk();
            console.log(JSON.stringify(ZoomMtg.getWebSDKVersion()));

            ZoomMtg.init({
                debug: false,
                leaveUrl: curUrl,
                isSupportAV: true,
                isSupportChat: true,
                disableInvite: true,
                meetingInfo: [
                  'topic',
                  'mn',
                  'participant',
                  'enctype',
                ],
                success: function() {
                    ZoomMtg.join({
                        signature: "<?php echo $signature; ?>",
                        apiKey: "<?php echo $this->api_key; ?>",
                        meetingNumber: <?php echo $this->meetingid; ?>,
                        userName: "<?php echo $userName; ?>",
                        passWord: "<?php echo $this->password; ?>",
                        userEmail: "<?php echo $this->email; ?>", 
                        success(res) {
                        },
                        error(res) { 
                            console.log(res);
                        }
                    })
                },
                error: function() {
                    console.log("init failed");
                }
            });
        }
    });
</script>

MaxM · February 17, 2021, 11:19pm

Hey @ativsoftware,

Thank you for the update. This could be related to the browser that you’re using to run the Web SDK. Have you tried using a different browser, updating your existing browser or clearing your cache?

If that doesn’t help, please send an email to developersupport@zoom.us with a link to this thread. We can set up a meeting from there and troubleshoot the issue live to make sure that I’m not missing any steps to reproduce the issue.

Thanks,
Max