Services Plugins FAQs

Agora video conferencing - close page detection

Plugins
#1

Hello Zeroqode team. I love this plugin and it’s an integral part of our video conferencing app, so thank you!

However, I have a major issue with the new RTC element. It seems like you guys have embedded a ‘close page detection’ to the plugin, with a popup (are you sure you want to leave this page? yes/no) , which is switched on when someone first joins a room and it’s impossible to disable, even after the room is closed! Also, this doesn’t work properly, as you can see in your demo page (The ‘user left’ event isn’t triggered, thus ‘viewers’ are not deleted).

I have been using a separate close page detection plugin, which I would enable/disable as needed, to overcome some issues with your plugin. This plugin is now overriden by this new embedded feature, and I’m back to facing these bugs, making our app unusable.

Namely:

  1. When someone leaves a three person chat, the window gets squashed (you can replicate this in your demo page) and the two remaining people can’t see each other properly. I used to use the close page detection to refresh the page - I can’t do this now.
  2. When someone leaves a two person chat, the other person is left alone. I used to use close page detection to automatically remove the other person from the room. I can’t do this now (I tried using your AgoraRTC A user left, but it doesn’t work)

Do you have plans to remove this close page detection and let us use a separate plugin, or allow us to disable it? Is there a workaround? We’re really stuck at the moment!

#2

Hi @josh6 ! I have a similar problem: when user leaving room (workflow Leave Agora RTC - go to the page home) broswer shows notification “Are you sure you want to leave this page?”.
At the same time I see an issue with Agora RTC: State uid is not defined in the plugin

Screenshot_4
Screenshot_41906×921 140 KB

Screenshot_6
Screenshot_61903×834 78.8 KB

This negatively affects the user experience, I hope zerocode team will solve this problem

#3

Hi @josh6 & @schipanova.me, thanks for reporting this issue.
I’ve passed it to the developer team for investigation.

Once any news will become available, I will let you know.
Thank you for understanding :pray:

Regards,

#4

Thank you @Serg !! If they could help us bypass this issue it would make this plugin awesome again :slight_smile:

1 Like
#5

Hi @josh6 & @schipanova.me,

We will make a plugin improvement, that will add a checkbox, that will allow enabling/disabling the notification feature. Once any update in this regard will become available, I will let you know asap.

Would it be convenient also to show a screenshot with the browser console tab when this error appears (for Chrome browser is CTRL + Shift + I).

Looking forward to your reply.
Regards,

#6

Hi @Serg Thank you for your reply! Here is a screenshot :

image
image1908×938 213 KB

#7

@schipanova.me thanks for the provided screenshot.
We will add related bugfix to the next plugin update, mentioned above (addition of a checkbox for enabling\disabling notification feature).
Once it will come to live, I will let you know asap.

Regards,

#8

Hi @josh6 & @schipanova.me, thanks for your patience.
We have pushed a plugin update, that has added a checkbox on plugin element for enabling/disabling the notification feature and fixed the state uid error.

To check changes, please upgrade your plugin to the latest version (Version 1.31.0: Added checkbox to enable window closing detection) and give it a try.

We checked this moment too, this issue can be solved through a check condition - when in the room there is 1 participant, leave the room. Within an woukflow you can track the number of users and with DB checking support, trigger the “Leave Room A Agora Connector” action.

Hope the provided update will help in your cases. Please let me know if there is anything else that I can help with about our plugin.

Have a nice weekend ahead!
Regards,

#9

Hi @Serg ! Thank you for updates! I checked it and everything works as it should :ok_hand:

1 Like
#10

Hi @schipanova.me, thanks for letting me know that the issue is solved now :hugs:

Have a good day!
Regards,